As per Relevance of the word terminal, we have this rfc below:
Network Working Group Marvin
Request for Comments: 884 Edward
University of Wisconsin -
December 1983
TELNET TERMINAL TYPE
This RFC specifies a standard for the ARPA Internet community. Hosts
the ARPA Internet that exchange terminal type information within
Telnet protocol are expected to adopt and implement this standard
1. Command Name and
TERMINAL-TYPE 24
2. Command
IAC WILL TERMINAL-
Sender is willing to send terminal type information in
subsequent sub-
IAC DO TERMINAL-
Sender is willing to receive terminal type information in
subsequent sub-
IAC DON'T TERMINAL-
Sender refuses to accept terminal type
IAC WON'T TERMINAL-
Sender refuses to send terminal type
IAC SB TERMINAL-TYPE SEND IAC
Sender requests receiver to transmit his (the receiver's)
type. The code for SEND is 1. (See below.)
IAC SB TERMINAL-TYPE IS ... IAC
Sender is stating the name of his terminal type. The code for
is 0. (See below.)
Solomon & Wimmers [Page 1]
RFC 884 December 1983
3.
DON'T TERMINAL-
WON'T TERMINAL-
Terminal type information will not be exchanged
4. Motivation for the
This option allows a telnet server to determine the type of
connected to a user telnet program. The transmission of
information does not immediately imply any change of processing
However, the information may be passed to a process, which may
the data it sends to suit the particular characteristics of
terminal. For example, some operating systems have a terminal
that accepts a code indicating the type of terminal being driven
Using the TERMINAL TYPE and BINARY options, a telnet server
on such a system could arrange to have terminals driven as if
were directly connected, including such special functions as
addressing, multiple colors, etc., not included in the
Virtual Terminal specification. This option fits into the
structure of TELNET options by deferring the actual transfer
status information to the SB command
5. Description of the
WILL and DO are used only to obtain and grant permission for
discussion. The actual exchange of status information occurs
option subcommands (IAC SB TERMINAL-TYPE...).
Once the two hosts have exchanged a WILL and a DO, the sender of
WILL TERMINAL-TYPE is free to transmit type information, spontan
eously or in response to a request from the sender of the DO.
worst, this may lead to transmitting the information twice. Only
sender of the DO may send requests (IAC SB TERMINAL-TYPE SEND IAC SE
and only the sender of the WILL may transmit actual type
(within an IAC SB TERMINAL-TYPE IS ... IAC SE command).
The terminal type information is an NVT ASCII string. Within
string, upper and lower case are considered equivalent. A
terminal type names useful in the context of IBM systems are
below. It is anticipated that additional names will be added in
future. The complete list of valid terminal types will be found
the latest "Assigned Numbers" RFC
Solomon & Wimmers [Page 2]
RFC 884 December 1983
The following is an example of use of the option
Host1: IAC DO TERMINAL-
Host2: IAC WILL TERMINAL-
(Host2 is now free to send status information at any time
Solicitations from Host1 are NOT necessary. This should
produce any dangerous race conditions. At worst, two IS's
be sent.)
Host1 (perhaps): IAC SB TERMINAL-TYPE SEND IAC
Host2:
IAC SB TERMINAL-TYPE IS IBM-3278-2 IAC
6. Implementation
The "terminal type" information may be any NVT ASCII string meaning
ful to both ends of the negotiation. The list of suggestions
is intended to minimize confusion caused by alternative "spellings
of the terminal type. For example, confusion would arise if
party were to call a terminal "IBM3278-2" while the other called
"IBM-3278/2". There is no negative acknowledgement for a
type that is not understood, but certain other options (such
switching to BINARY mode) may be refused if a valid terminal
name has not been specified. In some cases, a particular
may be known by more than one name, for example a specific type and
more generic type. In such cases, the sender of the TERMINAL-TYPE
command should reply to successive TERMINAL-TYPE SEND commands
the various names, from most to least specific. In this way,
telnet server that does not understand the first response can
for alternatives. However, it should cease sending TERMINAL-
SEND commands after receiving the same response two
times. Similarly, a sender should indicate it has sent all
names by repeating the last one sent
Here are a few terminal types useful in the IBM environment
IBM-3275-2
IBM-3276-2
IBM-3276-3
IBM-3276-4
IBM-3277-2
IBM-3278-2
IBM-3278-3
IBM-3278-4
Solomon & Wimmers [Page 3]
RFC 884 December 1983
IBM-3278-5
IBM-3279-2
IBM-3279-3
Here are a few terminal types useful in the TOPS20 environment
ANN-ARBOR-
CONCEPT-100
DATAMEDIA-2500
DEC-LA30
DEC-VT100
DEC-VT52
EXECUPORT-4000
HAZELTINE-1500
HP-2621
HP-2640
HP-2645
HP-2649
NETWORK-VIRTUAL-
TEKTRONIX-4025
TELERAY-1061
TELETYPE-33
TELETYPE-37
TELEVIDEO-950
TERMINET-300
TI-700
ZENITH-H19
Here are a few terminal types used in the Unix environment
ADDS-CONSUL-980
ADDS-REGENT-200
ANDERSON-JACOBSON-832
ANN-ARBOR-
CDI-1203
COMPUCOLOR-
CONCEPT-100
DATA-GENERAL-6053
DATAGRAPHIX-132
DATAMEDIA-3045
DATAPOINT-3360
DEC-DECWRITER-
DEC-GT40
DEC-VT52
DELTA-DATA-5000
DIABLO-1620
EXECUPORT-4000
Solomon & Wimmers [Page 4]
RFC 884 December 1983
GENERAL-TERMINAL-100
HAZELTINE-1500
HAZELTINE-2000
HP-2621
HP-2640
HP-2645
HP-2649
IBM-3101
INFOTON-100
LSI-ADM-3
MICROTERM-ACT-
MICROTERM-MIME-2
NETWORK-VIRTUAL-
PERKIN-ELMER-1100
PLASMA-
SUPERBEE-III-
TEKTRONIX-4014
TELERAY-3700
TELETYPE-33
TELETYPE-37
TELEVIDEO-912
TERMINET-300
TI-700
TI-733
TI-745
VISUAL-200
XEROX-1720
ZENITH-H19
ZENTEC-30
The type "UNKNOWN" should be used if the type of the terminal
unknown or unlikely to be recognized by the other party
The complete and up-to-date list will be maintained in the "
Numbers".
Solomon & Wimmers [Page 5]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
