RFC 580

Note to Protocol Designers and Implementers

📅 published October 1973, from ietf

NWG/RFC# 580 💌 note to protocol designers and implementers

Okay bestie, the header says this is NWG/RFC# 580, a note to protocol designers and implementers, written by Jon Postel (JBP) on 25-OCT-73 06:00, with the number 19849 🦋. It doesn't list a category, status, or anything it obsoletes or updates, so it's just a quick note 🎀.

Submit your protocols online 💻

Okay so, from now on, new protocol proposals should be submitted as online documents, ideally as NLS files at the Network Information Center 🌸. Why? Because it makes the review process way smoother and lets editors make both editorial and substantive changes quickly ✨. It also means protocol docs can get updated in time when future decisions make that necessary 🔥. Online docs are also super easy to pass around to the whole network community, which is iconic 💜. If you're having a really hard time with this, just reach out to me 🫶.

Telnet subnegotiation, read this one 🚨

Telnet protocol readers, and especially implementers, need to know this: all the existing Telnet Options that use subnegotiation have been modified [see RFC 562] so that the subnegotiation strings end with IAC SE 💀.

The value of SE is 240 🧚. Also, inside subnegotiations, any byte with the value 255 (IAC) has to be doubled when it's sent 🙈. Don't skip this part or your implementation will be lowkey broken 😭.

New address, who dis 📬

My address has changed, so update your contacts 🍓:

Jon Postel
The MITRE Corporation
Mail Stop W185
Westgate Research Park
McLean, Virginia 22101

Phone: (703) 893-3500 x2350

Online messages will still reach me at POSTEL@ISI or at JBP in the NIC Journal 💅✨.

📦 where this page comes from