RFC 361

Deamon Processes on Host 106

📅 published July 1972, from ietf

RFC 361 🎀 Bob's Daemon Update

okay bestie, the title block tea ☕: this is a Network Working Group doc by Bob Bressler from MIT-DMCG, with NIC number 10603, dated 5 July 1972 📅. It doesn't list a category or status, and it doesn't obsolete or update any other RFC. ✨

In response to RFCs 347 and 348, which are ECHO and DISCARD, MIT-DMCG (Host 106) now has daemon processes that answer RFCs on sockets 7 and 9 🧚. Literally so iconic. 💅

Bob also wanted to hear what people think about a few admin-type decisions 🫶.

First, if the machine is too full to run another daemon process, the proposed connection gets refused. That means a CLS is sent back in response to the RFC on socket 7 or 9 🙈.

Second, if nothing happens for two consecutive minutes (no characters coming in on input, or output stuck waiting for allocation), the connection gets aborted 💀. Not me timing out on the vibes. ⏰

Then comes the question for the group chat: does anyone see a need or a use for a third service, a random character generator? 🌈 Lowkey, a lot of systems already have programs like "TTYTST" that you can reach over the standard login connection. But it would be totally doable to make a server connection (like ECHO) that only offers this one limited service 🍓. Bob's pretty sure it'd be super useful for new NCPs and for gathering statistics 📊. Ngl, that's a strong case. 🔥

This RFC was turned into machine-readable form for the online RFC archives by BBN Corp. under the direction of Alex McKenzie, in January 1997 💜.
📦 where this page comes from