RFC 562

Modifications to the TELNET Specification 💖

okay bestie, the title block 🎀 says this is RFC 562 (NIC 18638) by A. McKenzie of BBN-TENEX 🧚, dated 28 August 1973 📅. It updates RFC 495 ✨ and references RFCs 513 and 529 💅.

okay so it's been almost four months since the new TELNET Protocol spec dropped 😭. In that time only two RFCs have suggested changes, and the newest one came out two months ago 🙈. Also the switch from old TELNET to new TELNET (1 January 1974) is only four months away ⏰. So it's giving time to officially update the spec with the suggested changes, and to declare a moratorium (a pause on adding more suggestions) until after the switchover 🛑. (Of course, no moratorium on specifying additional options, obviously 🫶.)

The two attached documents are the revised TELNET Protocol specs. They replace NIC #15372, TELNET Protocol Specification, and NIC #15373, TELNET Option Specifications 📚. The rest of this RFC sums up the changes. Page numbers refer to the earlier docs 📄.

Changes to TELNET Protocol Specification 🌸

• Page 8: the phrase "blocked on input" is removed (see RFC #513).
• Page 9, 10: an additional use of IP is mentioned (see RFC #529).
• Page 10: the explanation of AO is expanded (see RFC #513).
• Page 11: the definition of "'print position' (e.g., an overstrike)" is clarified (see RFC #513).
• Page 11, 12: the description of the TELNET Synch Signal is reworked to be in conformance with the ideas of RFC #529 (also see RFC #513).
• Page 14: the explanation of the CR-NUL convention is expanded (see RFC #513).
• Page 16: an additional command, End of Subnegotiation Parameters (SE) is defined (see RFCs 513, 529).

Changes to TELNET Option Specifications ✨

• Pages 2, 3: use of the command SE is explained (see RFCs 513, 529).
• Page 3: doubling of IAC in subnegotiation parameters is required (see RFC #513).

[This RFC was put into machine readable form for entry] [into the online RFC archives by Helene Morin, Via Genie 12/99]