Debian Codegraph @

rfc1763.html

raw
1 <pre>Network Working Group S. Senum
2 Request for Comments: 1763 DigiBoard
3 Category: Standards Track March 1995
4
5
6 <span class="h1">The PPP Banyan Vines Control Protocol (BVCP)</span>
7
8 Status of this Memo
9
10 This document specifies an Internet standards track protocol for the
11 Internet community, and requests discussion and suggestions for
12 improvements. Please refer to the current edition of the "Internet
13 Official Protocol Standards" (STD 1) for the standardization state
14 and status of this protocol. 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 for
19 transporting multi-protocol datagrams over point-to-point links. PPP
20 defines an extensible Link Control Protocol, and proposes a family of
21 Network Control Protocols for establishing and configuring different
22 network-layer protocols.
23
24 This document defines the Network Control Protocol for establishing
25 and configuring the Banyan VINES protocol over PPP.
26
27 Table of Contents
28
29 <a href="#section-1">1</a>. Introduction .......................................... <a href="#page-2">2</a>
30 <a href="#section-1.1">1.1</a> Specification of Requirements ................... <a href="#page-2">2</a>
31 <a href="#section-1.2">1.2</a> Terminology ..................................... <a href="#page-3">3</a>
32 <a href="#section-2">2</a>. A PPP Network Control Protocol for VINES .............. <a href="#page-3">3</a>
33 <a href="#section-2.1">2.1</a> Sending VINES Datagrams ......................... <a href="#page-4">4</a>
34 <a href="#section-2.2">2.2</a> General Considerations .......................... <a href="#page-4">4</a>
35 <a href="#section-3">3</a>. BVCP Configuration Options ............................ <a href="#page-5">5</a>
36 <a href="#section-3.1">3.1</a> BV-NS-RTP-Link-Type ............................. <a href="#page-5">5</a>
37 <a href="#section-3.2">3.2</a> BV-FRP .......................................... <a href="#page-6">6</a>
38 <a href="#section-3.3">3.3</a> BV-RTP .......................................... <a href="#page-7">7</a>
39 <a href="#section-3.4">3.4</a> BV-Suppress-Broadcast ........................... <a href="#page-8">8</a>
40 SECURITY CONSIDERATIONS ...................................... <a href="#page-9">9</a>
41 REFERENCES ................................................... <a href="#page-9">9</a>
42 ACKNOWLEDGEMENTS .......................................... <a href="#page-9">9</a>
43 CHAIR'S ADDRESS .............................................. <a href="#page-10">10</a>
44 AUTHOR'S ADDRESS ............................................. <a href="#page-10">10</a>
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="./rfc1763">RFC 1763</a> PPP BVCP March 1995</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
58
59 PPP has three main components:
60
61 1. A method for encapsulating multi-protocol datagrams.
62
63 2. A Link Control Protocol (LCP) for establishing, configuring,
64 and testing the data-link connection.
65
66 3. A family of Network Control Protocols for establishing and
67 configuring different network-layer protocols.
68
69 In order to establish communications over a point-to-point link, each
70 end of the PPP link must first send LCP packets to configure and test
71 the data link. After the link has been established and optional
72 facilities have been negotiated as needed by the LCP, PPP must send
73 BVCP packets to choose and configure the VINES network-layer
74 protocol. Once BVCP has reached the Opened state, VINES datagrams
75 can be sent over the link.
76
77 The link will remain configured for communications until explicit LCP
78 or BVCP packets close the link down, or until some external event
79 occurs (an inactivity timer expires or network administrator
80 intervention).
81
82 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Specification of Requirements</span>
83
84 In this document, several words are used to signify the requirements
85 of the specification. These words are often capitalized.
86
87 MUST This word, or the adjective "required", means that the
88 definition is an absolute requirement of the specification.
89
90 MUST NOT This phrase means that the definition is an absolute
91 prohibition of the specification.
92
93 SHOULD This word, or the adjective "recommended", means that there
94 may exist valid reasons in particular circumstances to
95 ignore this item, but the full implications must be
96 understood and carefully weighed before choosing a
97 different course.
98
99 MAY This word, or the adjective "optional", means that this
100 item is one of an allowed set of alternatives. An
101 implementation which does not include this option MUST be
102 prepared to interoperate with another implementation which
103 does include the option.
104
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="./rfc1763">RFC 1763</a> PPP BVCP March 1995</span>
111
112
113 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Terminology</span>
114
115 This document frequently uses the following terms:
116
117 datagram The unit of transmission in the network layer (such as IP).
118 A datagram may be encapsulated in one or more packets
119 passed to the data link layer.
120
121 frame The unit of transmission at the data link layer. A frame
122 may include a header and/or a trailer, along with some
123 number of units of data.
124
125 packet The basic unit of encapsulation, which is passed across the
126 interface between the network layer and the data link
127 layer. A packet is usually mapped to a frame; the
128 exceptions are when data link layer fragmentation is being
129 performed, or when multiple packets are incorporated into a
130 single frame.
131
132 peer The other end of the point-to-point link.
133
134 silently discard
135 This means the implementation discards the packet without
136 further processing. The implementation SHOULD provide the
137 capability of logging the error, including the contents of
138 the silently discarded packet, and SHOULD record the event
139 in a statistics counter.
140
141 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. A PPP Network Control Protocol for VINES</span>
142
143 The Banyan VINES Control Protocol (BVCP) is responsible for
144 configuring, enabling, and disabling the VINES protocol modules on
145 both ends of the point-to-point link. BVCP uses the same packet
146 exchange mechanism as the Link Control Protocol. BVCP packets may
147 not be exchanged until PPP has reached the Network-Layer Protocol
148 phase. BVCP packets received before this phase is reached should be
149 silently discarded.
150
151 The Baynan VINES Control Protocol is exactly the same as the Link
152 Control Protocol [<a href="#ref-1" title="&quot;The Point-to-Point Protocol (PPP)&quot;">1</a>] with the following exceptions:
153
154 Frame Modifications
155
156 The packet may utilize any modifications to the basic frame format
157 which have been negotiated during the Link Establishment phase.
158
159
160
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="./rfc1763">RFC 1763</a> PPP BVCP March 1995</span>
167
168
169 Data Link Layer Protocol Field
170
171 Exactly one BVCP packet is encapsulated in the Information field
172 of a PPP Data Link Layer frame where the Protocol field indicates
173 type hex 8035 (Banyan VINES Control Protocol).
174
175 Code field
176
177 Only Codes 1 through 7 (Configure-Request, Configure-Ack,
178 Configure-Nak, Configure-Reject, Terminate-Request, Terminate-Ack
179 and Code-Reject) are used. Other Codes should be treated as
180 unrecognized and should result in Code-Rejects.
181
182 Timeouts
183
184 BVCP packets may not be exchanged until PPP has reached the
185 Network-Layer Protocol phase. An implementation should be
186 prepared to wait for Authentication and Link Quality Determination
187 to finish before timing out waiting for a Configure-Ack or other
188 response. It is suggested that an implementation give up only
189 after user intervention or a configurable amount of time.
190
191 Configuration Option Types
192
193 BVCP has a distinct set of Configuration Options.
194
195 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Sending VINES Datagrams</span>
196
197 Before any VINES datagrams may be communicated, PPP must reach the
198 Network-Layer Protocol phase, and the Banyan VINES Control Protocol
199 must reach the Opened state.
200
201 Exactly one VINES packet is encapsulated in the Information field of
202 a PPP Data Link Layer frame where the Protocol field indicates type
203 hex 0035 (Banyan VINES datagram). The maximum length of a VINES
204 datagram transmitted over a PPP link is the same as the maximum
205 length of the Information field of a PPP data link layer frame.
206
207 The format of the Information field itself is the same as that
208 defined in [<a href="#ref-2" title="&quot;VINES Protocol Definition&quot;">2</a>].
209
210 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. General Considerations</span>
211
212 VINES supports an Address Resolution Protocol, VINES ARP, primarily
213 used for address assignment. Since this protocol is part of VINES
214 IP, it is fully supported over BVCP. VINES also supports a data-link
215 Echo Protocol (VINES Echo), used to test connectivity to a VINES
216 Server in a LAN environment, which is not supported over BVCP.
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="./rfc1763">RFC 1763</a> PPP BVCP March 1995</span>
223
224
225 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. BVCP Configuration Options</span>
226
227 BVCP Configuration Options allow modifications to the standard
228 characteristics of the network-layer protocol to be negotiated. If a
229 Configuration Option is not included in a Configure-Request packet,
230 the default value for that Configuration Option is assumed.
231
232 BVCP uses the same Configuration Option format defined for LCP [<a href="#ref-1" title="&quot;The Point-to-Point Protocol (PPP)&quot;">1</a>],
233 with a separate set of Options.
234
235 Up-to-date values of the BVCP Option Type field are specified in the
236 most recent "Assigned Numbers" RFC [<a href="#ref-3" title="&quot;Assigned Numbers&quot;">3</a>]. Current values are assigned
237 as follows:
238
239 Value Option
240
241 1 BV-NS-RTP-Link-Type
242 2 BV-FRP
243 3 BV-RTP
244 4 BV-Suppress-Broadcast
245
246 Note: A suggestion was made to combine the BV-NS-RTP-Link-Type option
247 and the BV-RTP option into a single option that could negotiate one
248 of four settings (S-RTP, NS-RTP-LAN, NS-RTP-WAN, NO-RTP). This
249 suggestion has been rejected because VINES must already deal with a
250 mix of S-RTP and NS-RTP, and that pushing this information down to
251 the PPP layer is not desirable.
252
253 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. BV-NS-RTP-Link-Type</span>
254
255 Description
256
257 This Configuration Option provides a way to negotiate the way the
258 Non-Sequenced Routing Update Protocol (NS-RTP) (pre-VINES 5.5,
259 i.e., 4.11 and 5.0) will run on the link. NS-RTP handles updates
260 differently depending on whether the interface is a LAN type or a
261 WAN type. For a LAN type, the full routing table is rebroadcast
262 every update interval (90 seconds). For a WAN type, the full
263 routing table is only transmitted for the first 3 update intervals
264 after the link comes up. After that only changes are transmitted
265 (for 5 update intervals). Note that this has no effect if
266 Sequenced RTP (VINES 5.5) is being used. More information on this
267 can be found in [<a href="#ref-2" title="&quot;VINES Protocol Definition&quot;">2</a>].
268
269 This option negotiates what an implementation is willing to
270 receive, and is negotiated separately per side of the PPP
271 connection. The acceptance of this option (by the peer) indicates
272 that the peer will send NS-RTP updates as if the link was a LAN
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="./rfc1763">RFC 1763</a> PPP BVCP March 1995</span>
279
280
281 type. The rejection (or absence) of this option indicates that
282 the peer will send NS-RTP updates as if the link was a WAN type.
283
284 By default, NS-RTP updates are sent as if the link was a WAN type.
285
286 A summary of the BV-NS-RTP-Link-Type Configuration Option format is
287 shown below. The fields are transmitted from left to right.
288
289 0 1
290 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
291 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
292 | Type | Length |
293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
294
295
296 Type
297
298 1
299
300 Length
301
302 2
303
304 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. BV-FRP</span>
305
306 Description
307
308 This Configuration Option provides a way to negotiate the use of
309 VINES Fragmentation Protocol (FRP). This protocol is used to
310 allow fragmentation and reassembly of a VINES packet over the
311 link. FRP prepends a two octet field to every packet going over
312 the link that contains a begin and end fragment information and a
313 sequence number. With PPP's default MRU of 1500, FRP is not
314 normally needed, and no FRP header would be sent with the VINES
315 packet. If a MRU of less than 1484 is negotiated, FRP will be
316 needed to send a full size VINES packet over the link. More
317 information on this can be found in [<a href="#ref-2" title="&quot;VINES Protocol Definition&quot;">2</a>].
318
319 This option negotiates what an implementation is willing to
320 receive, and is negotiated separately per side of the PPP
321 connection. The acceptance of this option (by the peer) indicates
322 that the peer will send VINES packets with a FRP header. The
323 rejection (or absence) of this option indicates that the peer will
324 send VINES packets without a FRP header.
325
326 By default, VINES packets are sent without a FRP header.
327
328
329
330
331
332 <span class="grey">Senum [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1763">RFC 1763</a> PPP BVCP March 1995</span>
335
336
337 A summary of the BV-FRP Configuration Option format is shown below.
338 The fields are transmitted from left to right.
339
340 0 1
341 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
342 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
343 | Type | Length |
344 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
345
346
347 Type
348
349 2
350
351 Length
352
353 2
354
355 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. BV-RTP</span>
356
357 Description
358
359 This Configuration Option provides a way to negotiate whether RTP
360 is used over the link. If dial-up lines with static routes are
361 being used, the use of RTP may be totally suppressed to conserve
362 bandwidth on the link.
363
364 This option negotiates what an implementation is willing to
365 receive, and is negotiated separately per side of the PPP
366 connection. The acceptance of this option (by the peer) indicates
367 that the peer will not send RTP packets. The rejection (or
368 absence) of this option indicates that the peer will send any RTP
369 packets.
370
371 By default, RTP packets are sent over the link.
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Senum [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1763">RFC 1763</a> PPP BVCP March 1995</span>
391
392
393 A summary of the BV-RTP Configuration Option format is shown below.
394 The fields are transmitted from left to right.
395
396 0 1
397 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
398 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
399 | Type | Length |
400 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
401
402
403 Type
404
405 3
406
407 Length
408
409 2
410
411 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. BV-Suppress-Broadcast</span>
412
413 Description
414
415 This Configuration Option provides a way to negotiate the sending
416 of VINES broadcast packets, i.e., packets with a destination VINES
417 network address of all ones. This option only affects VINES
418 packets that are not of type VINES ARP or VINES RTP. This option
419 can be used by a VINES Client to request that most of the
420 broadcast packets that would normally be sent to it by a VINES
421 Server be discarded, in order to conserve link bandwidth. Most of
422 the broadcast packets sent by a VINES Server are not useful to a
423 VINES Client.
424
425 This option negotiates what an implementation is willing to
426 receive, and is negotiated separately per side of the PPP
427 connection. The acceptance of this option (by the peer) indicates
428 that the peer MUST NOT send any VINES broadcast packets, other
429 than packets of type VINES ARP or VINES RTP. The rejection (or
430 absence) of this option indicates that the peer will send all
431 VINES broadcast packets.
432
433 By default, all VINES broadcast packets are sent.
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Senum [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1763">RFC 1763</a> PPP BVCP March 1995</span>
447
448
449 A summary of the BV-Suppress-Broadcast Configuration Option format is
450 shown below. The fields are transmitted from left to right.
451
452 0 1
453 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
454 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
455 | Type | Length |
456 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
457
458
459 Type
460
461 4
462
463 Length
464
465 2
466
467 Security Considerations
468
469 Security issues are not discussed in this memo.
470
471 References
472
473 [<a id="ref-1">1</a>] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51, <a href="./rfc1661">RFC</a>
474 <a href="./rfc1661">1661</a>, Daydreamer, July 1994.
475
476 [<a id="ref-2">2</a>] Banyan, "VINES Protocol Definition", June 1993, Order No.
477 003673.
478
479 [<a id="ref-3">3</a>] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, <a href="./rfc1700">RFC 1700</a>,
480 USC/Information Sciences Institute, October 1994.
481
482 Acknowledgements
483
484 Some of the text in this document is taken from previous documents
485 produced by the Point-to-Point Protocol Working Group of the Internet
486 Engineering Task Force (IETF).
487
488 In particular, Bill Simpson provided the boiler-plate used to create
489 this document.
490
491
492
493
494
495
496
497
498
499
500 <span class="grey">Senum [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1763">RFC 1763</a> PPP BVCP March 1995</span>
503
504
505 Chair's Address
506
507 The working group can be contacted via the current chair:
508
509 Fred Baker
510 Cisco Systems
511 519 Lado Drive
512 Santa Barbara, California 93111
513
514 Phone: (805) 681-0115
515 EMail: [email protected]
516
517 Author's Address
518
519 Questions about this memo can also be directed to:
520
521 Steven J. Senum
522 DigiBoard
523 6400 Flying Cloud Drive
524 Eden Prairie, Minnesota 55344
525
526 Phone: (612) 943-9020
527 EMail: [email protected]
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556 Senum [Page 10]
557 </pre>