Tech-invite3GPPspaceIETFspace
959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 0127

Comments on RFC 123

Pages: 2
Obsoleted by:  0145
Updates:  0123
Updated by:  0151

ToP   noToC   RFC0127 - Page 1
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
ToP   noToC   RFC0127 - Page 2
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 ]