As per Relevance of the word terminal, we have this rfc below:





NWG/RFC# 736 MRC 31-OCT-77 23:28 42213
Telnet SUPDUP



Network Working Group Mark
Request for Comments 736 SU-
NIC 42213 31 October 1977

TELNET SUPDUP

1. Command name and code

SUPDUP 21

2. Command meanings

IAC WILL

The sender of this command REQUESTS permission to, or
that it will, use the SUPDUP display

IAC WON'T

The sender of this command REFUSES to use the SUPDUP protocol

IAC DO

The sender of this command REQUESTS that the receiver use,
grants the receiver permission to use, the SUPDUP protocol

IAC DON'

The sender of this command DEMANDS that the receiver not use
SUPDUP protocol

3. Default

WON'T

DON'T

i.e., the SUPDUP display protocol is not in use














Mark Crispin [page 1]


NWG/RFC# 736 MRC 31-OCT-77 23:28 42213
Telnet SUPDUP


4. Motivation for the option

Since the publication of RFC 734, I have been requested to
an option to the TELNET protocol to provide for SUPDUP service
This option allows a host to provide SUPDUP service on the
TELNET socket (27 octal) instead of 137 (octal) which is the
SUPDUP ICP socket

5. Description of the option

A user TELNET program which wishes to use the SUPDUP
protocol instead of the NVT terminal service should send an IAC
SUPDUP. If the server is willing to use the SUPDUP
protocol, it should respond with IAC WILL SUPDUP; otherwise
should refuse with IAC WONT SUPDUP

For hosts which normally provide SUPDUP terminal services,
server can send IAC WILL SUPDUP upon ICP which the user may
accept or refuse

If the SUPDUP option is in effect, no further TELNET
are allowed. They are meaningless, since SUPDUP has its
facilities to perform the functions that are needed. Hence,
377 will become an ordinary transmitted character (in this case
invalid %TD code) instead of an IAC

Following the mutual acceptance of the SUPDUP option, the
negotiation proceeds as described in RFC 734.

























Mark Crispin [page 2]



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






Spectrum