Browse Prior Art Database

Comments on RFC 123 (RFC0127)

IP.com Disclosure Number: IPCOM000002088D
Original Publication Date: 1971-Apr-01
Included in the Prior Art Database: 2019-Feb-10
Document File: 2 page(s) / 2K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Postel: AUTHOR

Related Documents

10.17487/RFC0127: DOI

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

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]

Processing...
Loading...