1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
<pre>Network Working Group J. Postel
Request for Comments # 127 20 April 71
NIC #5843 UCLA
[Category D.1 Computer Science
Updates 123]
Comments on <a href="./rfc123">RFC 123</a>
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
<span class="grey"> [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey">l , l , and l are links, m and m are message allocations, b</span>
A B c B c B
and b are bit allocations, and all other symbols are as defined in
c
<a href="./rfc123">RFC 123</a>.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Gert Doering 4/97 ]
[Page 2]
</pre>
|
