Organization: China Interactive Publishing Network (http://www.china-pub.com/)
RFC Document Chinese Translation Program (http://www.china-pub.com/compters/emook/aboutemook.htm)
E-mail: Ouyang@china-pub.com
Translator: Wang Liang (Redar1 WL_PRJ_01@263.net)
Translation time:
Copyright: This Chinese translation copyright belongs to China Interactive Publishing Network. Can be used for non-commercial use free reprint, but the translation and copyright information of this document must be retained.
Network Working Group Marvin Solomon
Request for Comments: 930 Edward Wimmers
Supersedes: RFC 884 University of Wisconsin - Madison
January 1985
Telnet Terminal Type Options
(RFC930 - TELNET TERMINAL TYPE OPTION)
The state of this memo
This RFC specifies the standards on ARPA Internet Community. All hosts on the ARPA Internet should adopt and implement this standard. The release of this article is not restricted.
This standard is an update to RFC884. The only change is to define the Terminal-Type IS 只 只 送 送 送 出.. 作... Take the detailed explanation.
1. Command and code
Terminal 24
2. Command meaning
IAC Will Terminal-Type
The sender can send terminal information in a subsequent sub-negotiation.
Iac Won't Terminal-Type
The sender refuses to send terminal information.
Iac Do Terminal -Type
The sender can receive terminal information in a subsequent sub-negotiation.
Iac Don't Terminal-Type
The sender refuses to receive terminal type information.
Iac Sb Teminal-Type Send Iac SE
The sender request accepting end passes its terminal type to yourself. The command code of Send is 1. (See below)
Iac Sb Terminal-Type IAC SE
The sender is declaring its terminal type. The code of this command is 0. (See below)
3. Defaults
WON 'T Terminal-Type
Terminal type information is unchanged.
Don't Terminal-Type
Terminal type information is inconvenient.
4. Reasons for options
This option allows Telnet servers to confirm terminal types that have been connected to the user Telnet program. The transmission of type information does not mean that the processing will change immediately. These information may be passed to a process, which is given to the data issued by the specific terminal type to warn. For example, some operating systems have a terminal driver, so they can be accepted to indicate a code that drives the terminal type. With the Termanal Type and Binary options, the Telnet server program on these operating systems can drive the client terminal, and the effects of the direct connection, including the position, rich color, etc. of the mouse, and these are not included in the virtual network terminal. In the definition. This option can be consistent with the structure of the ordinary Telnet option by postponcing the status information to the SB command.
5. Option description
Will and do can only be used to get and ensure the permission discussed in the future. The actual status information exchange is simultaneously occurring at the same time. (IAC SB Terminal-Type). Once the two hosts begin to exchange for WILL and DO, it is idle for request type information in the Do Terminal-TypeDe sender. Only the DO type transmitting end can send a request (IAC SB Terminal-Type Send IAC SE), only the sender of the WILL type can transmit the actual type information (with the IAC SB RMINAL-TYPE IS ... IAC SE command). Terminal type information cannot be transmitted in an automatic manner, but can only be in a request-response.
Terminal type information is NVT ASCII String string type. This encoding does not consider the difference in case. A complete list of effective terminal types can be found in the nearest RFC "Assigned NumBers".
Next is an example of an option application:
Host 1: Iac Do Terminal-Type
Host 2: IAC Will Terminal-Type
(Host 1 can request status information at any time)
Host 1: IAC SB Terminal-Type Send Iac SE
Host 2: IAC SB Terminal-Type IBM-3728-2 IAC SE
6. achieve
"Terminal Type" information can be any NVT ASCII string that is meaningful to negotiation. The terminal type table named in "Assigned Number" is used to reduce the chaos caused by the name of the terminal type name. For example, if a terminal is called "IBM3278-2" type, another part is called "IBM3278 / 2", which has created chaos at this time. For the case where the terminal type is unknown, no negation recognition is not confirmed, but some other options (such as converted to BINARY mode) may be rejected. In some cases, a particular terminal may have more than one name, that is, a particular type may correspond to multiple common types. In these cases, the Terminal-Type IS command may use a lot of different names to respond to the continuous terminal-type send command. In this way, do not understand that the first Telnet server will require the terminal to retransmit. However, if the server has received the same response twice, it stops sending the terminal-type send command. Similarly, the sender should use the method of repeating the previous type name indicate that it has been sent all effective type names. Note: The Terminal-Type Send command is a response request because the host that sends Terminal-Type Send and receives Terminal-Type Send can't determine whether other hosts are requesting the second option, or Terminal-Type Send Two commands with Terminal-Type IS are confused in the middle.
The "unknown" type can be used to be used when the terminal type is uncertain or impossible to be recognized by others.
Maintain complete and the latest terminal type name in "Assigned NumBers". The maximum length of the terminal type name is 40 characters.
