RFC 580 UNKNOWN PROCESS · TELNET

Note to Protocol Designers and Implementers

Jon Postel asks protocol authors to submit proposals online and notes a Telnet change.

On rfc-editor.org ↗
PUBLISHED
October 1973
AUTHORS
J. Postel
STREAM
Legacy
UPDATED BY
RFC 582 — Comments on RFC 580: Machine readable protocols
SE VALUE
240
IAC VALUE
255
PREFERRED DOCUMENT FORMAT
NLS files at the Network Information Center
DOI
10.17487/RFC0580

RFC text

Original text · RFC Editor View on rfc-editor.org ↗
NWG/RFC# 580                                  JBP 25-OCT-73 06:00  19849
note to protocol designers and implementers



 Hereafter proposed protocols shall be submitted in the form of
on-line documents, preferably as nls files at the Network
Information Center. This will greatly facilitate the review
process and enable editorial and substantive changes to proceed
quickly. This also will permit timely updating of protocol
documents as may be neccessitated by future decisions. On-line
documents are also easily distributed to the network community.
If you find great difficulty in complying with this request
please contact me.


It should be noted by all Telnet protocol readers and especially
implementers that all the existing Telnet Options that involve
subnegotiation are modified [see RFC 562] to terminate the
subnegotiation strings with IAC SE. The value of SE is 240. Also
note that within subnegotiations the occurance of a byte with the
value 255 [IAC] requires doubling that byte on transmission.


Please note that my address has changed to:
     Jon Postel
     The MITRE Corporation
     Mail Stop W185
     Westgate Research Park
     McLean, Virginia 22101

     Phone: (703) 893-3500 x2350

On-line messages will reach me addressed to either
     POSTEL@ISI
or
     JBP in the NIC Journal.

ISO Plain Language

On this page
PROBLEMThe RFC says reviewing, editing and updating proposed protocols can be facilitated by keeping the documents online.
MECHANISMIt asks that proposed protocols be submitted as online documents, preferably NLS files at the Network Information Center, and notes new Telnet subnegotiation delimiters.
WHAT IT CHANGESThe note explains the expected review and distribution benefits and specifies IAC SE termination. The unit metadata says RFC 582 updates this note.

§1Submit Proposed Protocols Online

Jon Postel asks that proposed protocols be submitted as online documents, preferably as NLS files at the Network Information Center. He says online documents make review easier, allow editorial and substantive changes to proceed quickly, support timely updates, and are easy to distribute to the network community.

He asks anyone who has great difficulty complying to contact him.

Protocol proposals should be shared as online files. This makes them easier to review, change, update and distribute.

§2Telnet Subnegotiation Ending

The note says all existing Telnet options that use subnegotiation are modified as described in RFC 562. A subnegotiation string ends with IAC SE, where the value of SE is 240.

If a subnegotiation contains a byte with value 255 (IAC), the sender must transmit that byte twice.

A Telnet subnegotiation ends with the two-byte marker IAC SE. If the data itself contains IAC, send that byte twice.

§3Updated Contact Information

The note gives Jon Postel's new mailing address at The MITRE Corporation in McLean, Virginia. Online messages can be addressed to POSTEL@ISI or to JBP in the NIC Journal.

The note also gives a new mailing address and two ways to send the author an online message.

§4References