Debian Codegraph @

rfc1376.html

raw
1 <pre>Network Working Group S. Senum
2 Request for Comments: 1376 Network Systems Corporation
3 November 1992
4
5
6 <span class="h1">The PPP DECnet Phase IV Control Protocol (DNCP)</span>
7
8 Status of this Memo
9
10 This RFC specifies an IAB standards track protocol for the Internet
11 community, and requests discussion and suggestions for improvements.
12 Please refer to the current edition of the "IAB Official Protocol
13 Standards" for the standardization state and status of this protocol.
14 Distribution of this memo is unlimited.
15
16 Abstract
17
18 The Point-to-Point Protocol (PPP) [<a href="#ref-1" title="&quot;The Point-to-Point Protocol (PPP)&quot;">1</a>] provides a standard method of
19 encapsulating Network Layer protocol information over point-to-point
20 links. PPP also defines an extensible Link Control Protocol, and
21 proposes a family of Network Control Protocols (NCPs) for
22 establishing and configuring different network-layer protocols.
23
24 This document defines the NCP for establishing and configuring
25 Digital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP.
26 This document applies only to DNA Phase IV Routing messages (both
27 data and control), and not to other DNA Phase IV protocols (MOP, LAT,
28 etc.).
29
30 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
31
32 There are two basic approaches to running the DNA Phase IV Routing
33 protocol over a serial line:
34
35 1. The approached that several router vendors have taken which is to
36 treat the serial link as an Ethernet, using the same data and
37 control messages an Ethernet would use.
38
39 2. The approach defined by Digital, which uses DDCMP and slightly
40 different control messages.
41
42 This document will define a method that uses the first approach.
43
44
45
46
47
48
49
50
51
52 <span class="grey">Senum [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1376">RFC 1376</a> PPP DNCP November 1992</span>
55
56
57 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Overview Of Phase IV DNA Protocols</span>
58
59 The Phase IV DNA protocols which act as data link clients are:
60
61 o DNA Phase IV Routing
62 The Phase IV Digital Network Architecture (DNA) Routing
63 protocol is a network layer protocol providing services similar
64 to that of DoD IP. It routes messages in Phase IV DECnet
65 networks and manages the packet flow. The complete definition
66 of the DNA Phase IV Routing protocol can be found in [<a href="#ref-2" title="&quot;DNA Routing Layer Functional Specification&quot;">2</a>].
67
68 o DNA System Console
69 The Digital Network Architecture (DNA) System Console protocol
70 is a maintenance protocol providing low level access to a
71 system for the functions of:
72
73 . Identify processor
74 . Read data link counters
75 . Boot system
76 . Console carrier (a general purpose i/o channel)
77
78 The complete definition of the DNA System Console protocol can
79 be found in [<a href="#ref-3" title="&quot;DNA Maintenance Operations Functional Specification&quot;">3</a>].
80
81 o Digital Customer Use
82 The Digital Customer Use protocol type is a value reserved for
83 use by Digital customers. It allocates a type for private use
84 which will not conflict with Digital or other vendor protocols.
85
86 o DNA Diagnostics
87 The Digital Network Architecture (DNA) Diagnostics protocol
88 type is reserved to allow diagnostic software communications in
89 parallel with other data link clients.
90
91 o DNA Naming Service (DNS)
92 The Digital Network Architecture Naming Service (DNS) provides
93 a distributed naming service. It allows clients to register
94 named objects and to bind a set of attributes to the objects in
95 a distributed database.
96
97 o DNA Time Service (DTS)
98 The Digital Network Architecture Time Service (DTS) is a
99 protocol providing global clock synchronization in a
100 distributed environment.
101
102 o DNA Load/Dump
103 The Digital Network Architecture (DNA) Load/Dump protocol is a
104 maintenance protocol for copying the contents of processor
105
106
107
108 <span class="grey">Senum [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1376">RFC 1376</a> PPP DNCP November 1992</span>
111
112
113 memory to or from a remote system. For example, a system
114 manager can load an operating system into an unattended, remote
115 system. The complete definition of the Phase IV DNA Load/Dump
116 protocol can be found in [<a href="#ref-3" title="&quot;DNA Maintenance Operations Functional Specification&quot;">3</a>].
117
118 o DNA Experimental Use
119 The Digital Network Architecture (DNA) Experimental Use
120 protocol type allows Digital experimental protocols to share a
121 data link with other data link clients. It is for use by
122 Digital Equipment Corporation only.
123
124 o DNA Communications Test
125 The Digital Network Architecture (DNA) Communications Test
126 protocol is a maintenance protocol for testing the data link
127 communications path. The complete definition of the DNA
128 Communications Test protocol can be found in [<a href="#ref-3" title="&quot;DNA Maintenance Operations Functional Specification&quot;">3</a>].
129
130 o Digital Protocol X1
131 The Digital X1 protocol is a network layer protocol currently
132 private to Digital.
133
134 This document defines the NCP for establishing and configuring
135 Digital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP.
136 This document applies only to DNA Phase IV Routing messages (both
137 data and control), and not to other DNA Phase IV protocols (MOP, LAT,
138 etc.).
139
140 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. A PPP Network Control Protocol for DNA Phase IV Routing</span>
141
142 The DNA Phase IV Routing Control Protocol (DNCP) is responsible for
143 configuring, enabling, and disabling the DNA Phase IV Routing
144 protocol modules on both ends of the point-to-point link. DNCP uses
145 the same packet exchange mechanism as the Link Control Protocol
146 (LCP). DNCP packets may not be exchanged until PPP has reached the
147 Network-Layer Protocol phase. DNCP packets received before this
148 phase is reached should be silently discarded.
149
150 The DNA Phase IV Routing Control Protocol is exactly the same as the
151 Link Control Protocol [<a href="#ref-1" title="&quot;The Point-to-Point Protocol (PPP)&quot;">1</a>] with the following exceptions:
152
153 Frame Modifications
154
155 The packet may utilize any modifications to the basic frame format
156 which have been negotiated during the Link Establishment phase.
157
158 Data Link Layer Protocol Field
159
160 Exactly one DNCP packet is encapsulated in the Information field
161
162
163
164 <span class="grey">Senum [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1376">RFC 1376</a> PPP DNCP November 1992</span>
167
168
169 of a PPP Data Link Layer frame where the Protocol field indicates
170 type hex 8027 (DNA Phase IV Control Protocol).
171
172 Code field
173
174 Only Codes 1 through 7 (Configure-Request, Configure-Ack,
175 Configure-Nak, Configure-Reject, Terminate-Request, Terminate-Ack
176 and Code-Reject) are used. Other Codes should be treated as
177 unrecognized and should result in Code-Rejects.
178
179 Timeouts
180
181 DNCP packets may not be exchanged until PPP has reached the
182 Network-Layer Protocol phase. An implementation should be
183 prepared to wait for Authentication and Link Quality Determination
184 to finish before timing out waiting for a Configure-Ack or other
185 response. It is suggested that an implementation give up only
186 after user intervention or a configurable amount of time.
187
188 Configuration Option Types
189
190 DNCP has no Configuration Options.
191
192 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Sending DNA Phase IV Routing Packets</span>
193
194 Before any DNA Phase IV Routing packets may be communicated, PPP must
195 reach the Network-Layer Protocol phase, and the DNA Phase IV Routing
196 Control Protocol must reach the Opened state.
197
198 Exactly one octet-count field and one DNA Phase IV Routing packet are
199 encapsulated in the information field of a PPP Data Link Layer frame
200 where the Protocol field indicates type hex 0027 (DNA Phase IV
201 Routing). The octet-count contains a count of the number of octets
202 in the DNA Phase IV Routing packet. It is two octets in length
203 itself, and is stored in VAX byte ordering, to be more consistent
204 with DNA Phase IV Routing over Ethernet (i.e. least significant byte
205 first). It is needed to disambiguate optional padding octets from
206 real information.
207
208 The maximum length of an DNA Phase IV Routing packet transmitted over
209 a PPP link is the same as the maximum length of the Information field
210 of a PPP data link layer frame minus 2 octets (for the Length field).
211
212 The format of the packets themselves is the same as the format used
213 over Ethernet, without the Ethernet header, Pad, and FCS fields.
214
215 A summary of the information field is shown below. The fields are
216 transmitted from left to right.
217
218
219
220 <span class="grey">Senum [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1376">RFC 1376</a> PPP DNCP November 1992</span>
223
224
225 0 1 2 3
226 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
227 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
228 | Length LSB | Length MSB | DATA | ... |
229 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
230 | ... |
231 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
232
233 Length LSB
234
235 Least significant byte of length field
236
237 Length MSG
238
239 Most significant byte of length field
240
241 DATA
242
243 DNA Phase IV Routing data, as specified in [<a href="#ref-2" title="&quot;DNA Routing Layer Functional Specification&quot;">2</a>]
244
245 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. General Considerations</span>
246
247 When a topology change in the network occurs, DNA Phase IV Routing
248 nodes immediately propagate changes via Level 1 and Level 2 Routing
249 messages, with a 1 second minimum delay between updates. DNA Phase
250 IV Routing nodes also periodically retransmit the complete Level 1
251 and Level 2 distance vectors to guard against data corruption in host
252 memory, and (in the case of Ethernet) loss of packets due to media
253 errors. Because Digital's serial links run a protocol that
254 guarantees delivery of packets (DDCMP), the recommended default
255 retransmit time is long (600 seconds), whereas for Ethernet, where
256 packet delivery is not guaranteed, the recommended default is short
257 (10 seconds), as documented in [<a href="#ref-2" title="&quot;DNA Routing Layer Functional Specification&quot;">2</a>]. To achieve convergence of routes
258 within a satisfactory time, the interval between updates should be
259 based upon the error rate of underlying data link. As such, it is
260 recommended that the time between routing updates be user
261 configurable per PPP interface.
262
263 The Hello timer and Listen timer should be set according to the
264 recommendations for broadcast links (15 and 45 seconds,
265 respectively).
266
267 Routers are not required to send routing updates if the remote node
268 connected via the PPP link is an endnode. Endnodes are required to
269 discard all routing updates received over a PPP link. The type of a
270 node (endnode versus routing) can be determined from the hello
271 messages received from it.
272
273
274
275
276 <span class="grey">Senum [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1376">RFC 1376</a> PPP DNCP November 1992</span>
279
280
281 References
282
283 [<a id="ref-1">1</a>] Simpson, W., "The Point-to-Point Protocol (PPP)", <a href="./rfc1331">RFC 1331</a>,
284 Daydreamer, May 1992.
285
286 [<a id="ref-2">2</a>] Digital Equipment Corporation, "DNA Routing Layer Functional
287 Specification", Version 2.0.0, Order No. AA-X435A-TK.
288
289 [<a id="ref-3">3</a>] Digital Equipment Corporation, "DNA Maintenance Operations
290 Functional Specification", Version 3.0.0, Order No. AA-X436A-TK.
291
292 Acknowledgments
293
294 Some of the text in this document is taken from previous documents
295 produced by the Point-to-Point Protocol Working Group of the Internet
296 Engineering Task Force (IETF).
297
298 The author wishes to thank Jim Muchow (Network Systems Corporation),
299 and Arthur Harvey (Digital Equipment Corporation) for their input to
300 this memo.
301
302 Security Considerations
303
304 Security issues are not discussed in this memo.
305
306 Chair's Address
307
308 The working group can be contacted via the current chair:
309
310 Brian Lloyd
311 Lloyd &amp; Associates
312 3420 Sudbury Road
313 Cameron Park, California 95682
314
315 Phone: (916) 676-1147
316 EMail: [email protected]
317
318 Author's Address
319
320 Questions about this memo can also be directed to the author:
321
322 Steven J. Senum
323 Network Systems Corporation
324 7600 Boone Avenue North
325 Minneapolis, Minnesota 55428
326
327 Phone: (612) 424-4888
328 EMail: [email protected]
329
330
331
332 Senum [Page 6]
333 </pre>