RFC 127

Network Working Group, Request for Comments # 127 🎀

J. Postel 💖 UCLA, Computer Science, NIC #5843, dated 20 April 71 📅

Category D.1 🌸 This one updates RFC 123 ✨, so it's basically a follow-up comment bestie needs to read alongside it.

Comments on RFC 123 💅

okay so this is Postel's take on the NCP-to-NCP exchange you'd need to actually run the Initial Connection Protocol from RFC 123 🦋 it's literally the whole conversation between the two sides, step by step, and it's giving very clean choreography 💃

     Server NCP                                User NCP
     ----------                                --------

     Listen for Connection on L                RTS, U, L, l
     STR, L, U, 32                                         A

     Send 32 bits of data
     in 1 message on link l
                           A
     (value is S)                              Receive 32 bits of data
                                               from link l (value is S)
                                                          A

     CLS, L, U                                 CLS, U, L

     STR, S+1, U, B                            STR, U+1, S, B
                   s                                         u

     RTS, S, U+1, l                            RTS, U, S+1, l
                   B                                         c

     wait for connection                       wait for connection

     ALL, l , m , b                            ALL, l , m , b
           B   B   B                                 c   c   c

     data sent on link l                       data sent on link l
                        c                                         B

     data received on link l                   data received on link l
                            B                                         c

the little key for all the symbols is kinda wild with the subscripts 🙈 but here's how it reads, verbatim:

l , l , and l  are links, m  and m  are message allocations, b
 A   B       c             B      c                           B
and b  are bit allocations, and all other symbols are as defined in
     c
RFC 123.

ngl the whole thing is basically "everything else means what RFC 123 says it means" 🧚 so if you're ever confused, go check RFC 123 first, periodt 💜

[ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Gert Doering 4/97 ] 🌈