Документ взят из кэша поисковой машины. Адрес оригинального документа : http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/pdfrfc/rfc736.txt.pdf Дата изменения: Wed Mar 27 23:49:28 2002 Дата индексирования: Tue Oct 2 16:33:50 2012 Кодировка:

NWG/RFC# 736 Telnet SUPDUP Option

MRC 31-OCT-77 23:28

42213

Network Working Group Request for Comments 736 NIC 42213 TELNET SUPDUP Option 1. Command name and code. SUPDUP 2. Command meanings. IAC WILL SUPDUP 21

Mark Crispin SU-AI 31 October 1977

The sender of this command REQUESTS permission to, or that it will, use the SUPDUP display protocol IAC WON'T SUPDUP

confirms

The sender of this command REFUSES to use the SUPDUP protocol. IAC DO SUPDUP The sender of this command REQUESTS that the receiver use, grants the receiver permission to use, the SUPDUP protocol. IAC DON'T The sender of this command DEMANDS that the receiver not use the SUPDUP protocol. 3. Default. WON'T SUPDUP DON'T SUPDUP i.e., the SUPDUP display protocol is not in use. or

Mark Crispin [page 1] \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000


NWG/RFC# 736 Telnet SUPDUP Option

MRC 31-OCT-77 23:28

42213

4.

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

5.

Description of the option. A user TELNET program which wishes to use the SUPDUP display protocol instead of the NVT terminal service should send an IAC DO SUPDUP. If the server is willing to use the SUPDUP display protocol, it should respond with IAC WILL SUPDUP; otherwise it should refuse with IAC WONT SUPDUP. For hosts which normally provide SUPDUP terminal services, the server can send IAC WILL SUPDUP upon ICP which the user may then accept or refuse. If the SUPDUP option is in effect, no further TELNET negotiations are allowed. They are meaningless, since SUPDUP has its own facilities to perform the functions that are needed. Hence, octal 377 will become an ordinary transmitted character (in this case an invalid %TD code) instead of an IAC. Following the mutual acceptance of the SUPDUP option, the negotiation proceeds as described in RFC 734. SUPDUP

Mark Crispin [page 2] \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000


\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000