RFC 461

Telnet Protocol meeting announcement

📅 published February 1973, from ietf

RFC 461: TELNET Protocol Meeting Announcement ✨

okay bestie, the title block first 💅 This is RFC 461 (NIC 14416), titled TELNET Protocol Meeting Announcement, written by A. McKenzie of BBN-NET and dated February 14, 1973 🎀 The original doesn't list a category, and it doesn't obsolete or update anything.

Why a meeting? 🦋

ngl, TELNET had been having a MOMENT. Since RFC 318 came out, people had sent in SO many proposals for changes and extensions to the protocol, and it was still unofficial 😭 So Alex is calling a meeting to finally get everyone on the same page and define an "official" protocol. Maybe with a little room for optional expansion too 🌸

The meeting itself 🗓️

It's happening at UCLA on Monday, March 5 🍓 This is going to be a working meeting, not a tutorial. The vibe is: come ready to talk, not to be caught up on the basics. So only people who can discuss at LEAST the issues that have already been raised should come 💖

Homework before you show up 📚

Before you walk in, you should be familiar with these RFCs. Like, at a minimum:

RFC 318
RFC 328
RFC 340
RFC 357
RFC 393
RFC 426
RFC 435

It also helps to know what the TELNET Committee was discussing before RFC 318. Bestie, I'm not gonna pretend that's required, but it would probably help 🧚

⚠️ Heads up: there are few (no?) Hosts that follow the echo-control conventions described in RFC 318. Iconic behaviour from the network, honestly 💀

How to RSVP 📞

If you want to come, contact Alex McKenzie at BBN (NIC ident aam):

50 Moulton Street, Cambridge, Mass. 02l38
(617) 491-1850 ext. 441

Once there's a rough idea of how many people are coming, Alex will pick a meeting room and announce a time, etc. 🫶

       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by Alex McKenzie with    ]
       [ support from GTE, formerly BBN Corp.             9/99 ]
📦 where this page comes from