RFC 6

Network Working Note 💖 Written by Steve Crocker of UCLA, dated 10 April 1969, and filed as RFC-6. It's a Network Working Note, so it isn't a standard, and it doesn't obsolete or update anything. ✨

CONVERSATION WITH BOB KAHN 🎀

okay so Steve talked with Bob Kahn at BB&N yesterday 🦋 they got into code conversion in the IMPs, IMP-HOST communication, and HOST software. obsessed with the lineup. 💅

BB&N is ready to convert 6, 7, 8, or 9 bit character codes into 8-bit ASCII for transmission, and then convert again when the message is assembled at the destination IMP. 🌸 Their plan is a one for one conversion scheme, with tables that are unique to the HOST. Steve suggested that sites with 6-bit codes might also want case shifting. Bob said that could cause overflow if too many case shifts are needed. ngl that's a real plot twist 😭 Steve's take was that this is rare, so they could probably live with an overflow indication instead of a guarantee. 🫶

For HOST-IMP communication, we now have a five bit link field and a bit to indicate conversion. 🧚 There's also a possible 2-bit conversion indicator: one value for converting before sending, and one for converting after. That would give another handle for checking or controlling the system. main character energy 👑

The HOST can send messages or portions of a message to its IMP, specifying:

1. Tracing
2. Conversion
3. Whether message is for destination IMP or HOST
4. Send RFNM
5. HOST up or down
6. Synchronization
7. Format Error Messages
8. Master Link Clear
9. Status Requested

The IMP can send its HOST information on:

1. Conversion
2. REFNM Arrived
3. IMP up or down
4. Synchornization
5. Called HOST not Responding
6. Format Error
7. Status in IMP

And Steve also gave Bob a summary of Network Notes 1, 2, and 3. 🌈 That's the whole tea ☕💜