As per Relevance of the word terminal, we have this rfc below:
NWG/RFC# 747 MRC 21-MAR-78 44015
Recent Extensions to the SUPDUP
Network Working Group Mark
Request for Comments 747 SU-
NIC 44015 21 March 1978
Updates: RFC 734. See also RFC 746.
Recent Extensions to the SUPDUP
Recently, some extensions have been made to the SUPDUP protocol.
746, by Richard Stallman, documented the SUPDUP graphics extension
In addition, a TTYOPT bit has been added and two more variables
been added to the initial negotiation. This RFC describes the
from RFC 734, but excludes the detailed information in RFC 746.
These extensions are upwards and downwards compatable, and
completely optional. For most SUPDUP user and server programs
RFC 734 remains an adequate description of the protocol
However, it is suggested that if the console's line speed
known, the user SUPDUP should be modified to send the new ISPEED
OSPEED variables (sending 0 for SMARTS if the graphics extension
not to be used) so the server can handle buffering for the
better
Since these changes are compatable and optional, and since the
protocol is being actively worked on at the present time, I have
to issue this update RFC rather than an updated version of
734. An updated 734 will be issued when the protocol stabilizes again
Three new variables have been added to the initial negotiation.
order, they are SMARTS, ISPEED, and OSPEED. Consequently, the
should now be -10,,0, or, in octal, 777770000000.
The SMARTS variable specifies what "smarts" (in general, what
capabilities) the terminal has. Like the TTYOPT variable, a bit
true implies that the terminal has this option. RFC 746 describes
variable and the SUPDUP graphics option in complete detail.
the graphics extension is not to be used, SMARTS should be set to 0.
The ISPEED and OSPEED variables are respectively the input and
baud rates of the terminal, if known. For example, a 150./1200.
baud terminal would have an ISPEED of 150. and an OSPEED of 1200.
speed of zero means the line speed is indeterminate
The %TPPRN TTYOPT bit (value 0,,200) has been added. This
specifies that the system should swap parenthesis with square
on input. This is often desirable for LISP users who are using
terminal which has parenthesis as a shift character but
square brackets. This bit is normally off and servers are not
to implement it
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
