Telnet terminal type options

Organization: China Interactive publishing network (http://www.china-pub.com /)
RFC document Chinese Translation Plan (http://www.china-pub.com/compters/emook/aboutemook.htm)
E-mail: ouyang@china-pub.com
Redar1 wl_prj_01@263.net)
Posting time:
Copyright: The copyright of this Chinese translation document belongs to China Interactive publishing network. This document can be freely reproduced for non-commercial purposes, but the translation and copyright information of this document must be kept.

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)

Status of this Memorandum

This RFC standardizes an ARPA Internet community standard. All hosts on the ARPA Internet should adopt and implement this standard. The release of this article is unrestricted.
This standard is an update of rfc884. The only change is that the terminal-type is subnegotiation can only be sent when a response is made to the terminal-type send subnegotiation. For more information, see.

1. commands 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 rejects the sending terminal information.
IAC do terminal-type
The sender can receive terminal information in a subsequent sub-negotiation.
IAC don't terminal-type
The sender rejects the type information of the Receiving Terminal.
IAC Sb TEMINAL-TYPE send IAC se
The sender sends the terminal type to the receiver of the request. The send command code is 1. (See below)
IAC Sb terminal-type is IAC se
The sender declares the terminal type. The code for this command is 0. (See below)

3. Default Value

Won't terminal-type
The terminal type information remains unchanged.
Don't terminal-type
The terminal type information is inconvenient.

4. Reasons for option generation

This option allows the telnet server to confirm that it is connected to the terminal type of the user's telnet program. The transmission of type information does not mean that the processing process will change immediately. This information may be transmitted to a process, which warns of the data to adapt to the specific terminal type. For example, someOperating SystemThere is a terminal driver, so you can accept the code used to indicate the driver terminal type. With termanal type and binary optionsOperating SystemThe telnet server program on can drive the client terminal, and the effect is the same as that of direct connection, including the mouse position, rich color, etc, these are not included in the definition of virtual network terminals. By postponing the transmission of status information to the SB command, this option can be consistent with the structure of the common telnet option.

5. Option description

Will and do can only be used to obtain and guarantee future discussions. The actual status information exchange occurs simultaneously with the option subcommand. (IAC Sb terminal-type ).
Once the two hosts begin to exchange will and do, the DO TERMINAL-TYPEDE sender is idle for request type information. Only do-type senders can send requests (IAC Sb terminal-type send IAC Se), only will-type senders can transmit actual type information (with IAC Sb RMINAL-TYPE is... IAC se command ). Terminal type information cannot be transmitted automatically, but only in request-response mode.
The terminal type information is nvt ASCII string type. This encoding is case-insensitive. The complete list of valid terminal types can be found in the latest RFC "assigned numbers.
The following 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 is IBM-3728-2 IAC se

6. Implementation

The "terminal type" information can be any nvt ASCII string that is meaningful to both parties. The terminal type table named in "assigned number" is used to reduce confusion caused by the diversity of terminal type names. For example, if a terminal is called the "IBM3278-2" type by some people and the other part is called the "ibm3278/2", then chaos occurs. If the terminal type is unknown, you cannot make a negative confirmation. However, if the valid Terminal type name is not confirmed, some other options (such as converting to binary mode) it may be rejected. In some cases, a specific terminal may have more than one name, that is, a specific type may correspond to multiple common types. In these cases, the terminal-type is command may use many different names to respond to the continuous terminal-type send command. In this way, the first time the corresponding telnet server is required to resend the terminal. However, if the server receives the same response twice, it stops sending the terminal-type send command. Similarly, the sender should use the method that repeats the previous type name to indicate that it has sent all valid type names. Note: The terminal-type send command is in the Response Request (terminal-type send ), this is because the host that sends the terminal-type send and receives the terminal-type send cannot determine that other hosts are requesting the second option, the terminal-type send and terminal-type is commands are confused in the middle.
The "unknown" type can be used when the terminal type is unknown or cannot be recognized by others.
The complete and up-to-date terminal type name is maintained in assigned numbers. The maximum length of a terminal type name is 40 characters.
// Http://www.leftworld.net [2006-08-15]