From 4bfd864f10b68b71482b35c818559068ef8d5797 Mon Sep 17 00:00:00 2001 From: Thomas Voss Date: Wed, 27 Nov 2024 20:54:24 +0100 Subject: doc: Add RFC documents --- doc/rfc/rfc127.txt | 112 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 112 insertions(+) create mode 100644 doc/rfc/rfc127.txt (limited to 'doc/rfc/rfc127.txt') diff --git a/doc/rfc/rfc127.txt b/doc/rfc/rfc127.txt new file mode 100644 index 0000000..c316d22 --- /dev/null +++ b/doc/rfc/rfc127.txt @@ -0,0 +1,112 @@ + + + + + + +Network Working Group J. Postel +Request for Comments # 127 20 April 71 +NIC #5843 UCLA +[Category D.1 Computer Science +Updates 123] + + Comments on RFC 123 + +The following is my interpretation of the exchange between NCP's which +would be necessary to carry out the Initial Connection Protocol of RFC +123. + + 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 + + + + + + + + + [Page 1] + +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. + + + [ This RFC was put into machine readable form for entry ] + [ into the online RFC archives by Gert Doering 4/97 ] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + [Page 2] + -- cgit v1.2.3