File: rfc145.txt

package info (click to toggle)
doc-rfc 20181229-2
  • links: PTS, VCS
  • area: non-free
  • in suites: buster
  • size: 570,944 kB
  • sloc: xml: 285,646; sh: 107; python: 90; perl: 42; makefile: 14
file content (115 lines) | stat: -rw-r--r-- 2,490 bytes parent folder | download | duplicates (5)
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
107
108
109
110
111
112
113
114
115






Network Working Group                                          J. Postel
Request for Comments: 145                                     UCLA - NMC
NIC: 6739                                                     4 May 1971
Updates: 123
Obsoletes: 127

              Initial Connection Protocol Control Commands

     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.  (This note corrects an error pointed out by Eric
   Harslem of RAND).

      Server NCP                      User NCP
      __________                      ________

      Listen for Connection L         RTS, U, L, l
                                                  A

      STR, L, U, 32                   ALL, l  , 1, 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+1, 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 to link l             data sent on link l
                         C                               B

      data received on link           data received on link l
                           B                                 C




Postel                                                          [Page 1]

RFC 145               Initial Connection Protocol             4 May 1971


      l , l , and l , are links, m  and m  are messages allocations, b
       A   B       C              B      C                            B
      and b  are bit allocations, and all other symbols are defined in
           C
      RFC #123.

      [This RFC is also available in .PS and. PDF format.]

          [ This RFC was put into machine readable form for entry ]
               [ into the online RFC archives by Lorrie Shiota]









































Postel                                                          [Page 2]