Debian Codegraph @

rfc1333.html

raw
1 <pre>Network Working Group W. Simpson
2 Request for Comments: 1333 Daydreamer
3 May 1992
4
5
6
7 <span class="h1">PPP Link Quality Monitoring</span>
8
9
10
11 Status of this Memo
12
13 This RFC specifies an IAB standards track protocol for the Internet
14 community, and requests discussion and suggestions for improvements.
15 Please refer to the current edition of the "IAB Official Protocol
16 Standards" for the standardization state and status of this protocol.
17 Distribution of this memo is unlimited.
18
19 Abstract
20
21 The Point-to-Point Protocol (PPP) [<a href="#ref-1" title="&quot;The Point-to-Point Protocol&quot;">1</a>] provides a standard method of
22 encapsulating Network Layer protocol information over point-to-point
23 links. PPP also defines an extensible Link Control Protocol, which
24 allows negotiation of a Quality Protocol for continuous monitoring of
25 the viability of the link.
26
27 This document defines a protocol for generating Link-Quality-Reports.
28
29 This RFC is a product of the Point-to-Point Protocol Working Group of
30 the Internet Engineering Task Force (IETF). Comments on this memo
31 should be submitted to the [email protected] mailing list.
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Simpson [Page i]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-ii" ></span>
54 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
55
56
57 Table of Contents
58
59
60 <a href="#section-1">1</a>. Introduction .......................................... <a href="#page-1">1</a>
61
62 <a href="#section-2">2</a>. Link Quality Monitoring ............................... <a href="#page-2">2</a>
63 <a href="#section-2.1">2.1</a> Design Motivation ............................... <a href="#page-2">2</a>
64 <a href="#section-2.2">2.2</a> Counters ........................................ <a href="#page-2">2</a>
65 <a href="#section-2.3">2.3</a> Counting Packets and Octets ..................... <a href="#page-4">4</a>
66 <a href="#section-2.4">2.4</a> Processes ....................................... <a href="#page-4">4</a>
67 <a href="#section-2.5">2.5</a> Configuration Option Format ..................... <a href="#page-6">6</a>
68 <a href="#section-2.6">2.6</a> Packet Format ................................... <a href="#page-8">8</a>
69 <a href="#section-2.7">2.7</a> Transmission of Reports ......................... <a href="#page-12">12</a>
70 <a href="#section-2.8">2.8</a> Calculations .................................... <a href="#page-12">12</a>
71 <a href="#section-2.9">2.9</a> Failure Detection ............................... <a href="#page-13">13</a>
72 <a href="#section-2.10">2.10</a> Policy Suggestions .............................. <a href="#page-14">14</a>
73
74 SECURITY CONSIDERATIONS ...................................... <a href="#page-14">14</a>
75
76 REFERENCES ................................................... <a href="#page-14">14</a>
77
78 ACKNOWLEDGEMENTS ............................................. <a href="#page-14">14</a>
79
80 CHAIR'S ADDRESS .............................................. <a href="#page-15">15</a>
81
82 AUTHOR'S ADDRESS ............................................. <a href="#page-15">15</a>
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 <span class="grey">Simpson [Page ii]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-1" ></span>
110 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 PPP has three main components:
116
117 1. A method for encapsulating datagrams over serial links.
118
119 2. A Link Control Protocol (LCP) for establishing, configuring,
120 and testing the data-link connection.
121
122 3. A family of Network Control Protocols (NCPs) for establishing
123 and configuring different network-layer protocols.
124
125 In order to establish communications over a point-to-point link, each
126 end of the PPP link must first send LCP packets to configure the data
127 link during the Establishment phase. During the Authentication and
128 Network-Layer Protocol phases, the link may be tested to determine if
129 quality is sufficient for operation. This testing is completely
130 optional.
131
132 If an implementation desires that the peer use some specific link
133 quality monitoring protocol, then it MUST negotiate the use of that
134 protocol using the Quality-Protocol Configuration Option during Link
135 Establishment phase.
136
137 The negotiation mechanism is independent in each direction. However,
138 if the peer agrees to send Quality-Protocol packets, it MUST
139 correctly process such packets on reception, even if it does not
140 request such packets or implement a monitoring policy.
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Simpson [Page 1]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
166 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
167
168
169 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Link Quality Monitoring</span>
170
171 Data communications links are rarely perfect. Packets can be dropped
172 or corrupted for various reasons (line noise, equipment failure,
173 buffer overruns, etc.). Sometimes, it is desirable to determine
174 when, and how often, the link is dropping data. Routers, for
175 example, may want to temporarily allow another route to take
176 precedence. An implementation may also have the option of
177 disconnecting and switching to an alternate link. The process of
178 determining data loss is called "Link Quality Monitoring".
179
180 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Design Motivation</span>
181
182 There are many different ways to measure link quality, and even more
183 ways to react to it. Rather than specifying a single scheme, Link
184 Quality Monitoring is divided into a "mechanism" and a "policy". PPP
185 fully specifies the "mechanism" for Link Quality Monitoring by
186 defining the Link-Quality-Report (LQR) packet and specifying a
187 procedure for its use. PPP does NOT specify a Link Quality
188 Monitoring "policy" -- how to judge link quality or what to do when
189 it is inadequate. That is left as an implementation decision, and
190 can be different at each end of the link. Implementations are
191 allowed, and even encouraged, to experiment with various link quality
192 policies. The Link Quality Monitoring mechanism specification
193 insures that two implementations with different policies may
194 communicate and interoperate.
195
196 To allow flexible policies to be implemented, the PPP Link Quality
197 Monitoring mechanism measures data loss in units of packets, octets,
198 and Link-Quality-Reports. Each measurement is made separately for
199 each half of the link, both inbound and outbound. All measurements
200 are communicated to both ends of the link so that each end of the
201 link can implement its own link quality policy for both its outbound
202 and inbound links.
203
204 Finally, the Link Quality Monitoring protocol is designed to be
205 implementable on many different kinds of systems. Although it may be
206 common to implement PPP (and especially Link Quality Monitoring) as a
207 single software process, multi-process implementations with hardware
208 support are also envisioned. The PPP Link Quality Monitoring
209 mechanism provides for this by careful definition of the Link-
210 Quality-Report packet format, and by specifying reference points for
211 all data transmission and reception measurements.
212
213 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Counters</span>
214
215 Each Link Quality Monitoring implementation maintains counts of the
216 number of packets and octets transmitted and successfully received,
217
218
219
220 <span class="grey">Simpson [Page 2]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
222 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
223
224
225 and periodically transmits this information to its peer in a Link-
226 Quality-Report packet.
227
228 These counters are similar to sequence numbers; they are constantly
229 increasing to give a "relative" indication of the number of packets
230 and octets communicated across the outbound link. By comparing the
231 values in successive Link-Quality-Reports, an LQR receiver can
232 compute the "delta" number of packets and octets successfully
233 communicated across the link. Comparing these absolute numbers then
234 gives an indication of a link's quality. Relative numbers, rather
235 than absolute, are transmitted because they greatly simplify link
236 synchronization.
237
238 The Link-Quality-Report uses the Interface counters defined by SNMP
239 MIB-II [<a href="#ref-2" title="&quot;Management Information Base for Network Management of TCP/IP-based internets: MIB-II&quot;">2</a>]. These counters are not initialized to any particular
240 value when the LCP enters the Establishment phase.
241
242 In addition, the Link-Quality-Report requires the implementation of
243 the following three unsigned, monotonically increasing counters which
244 conform to the type and size requirements for SNMP MIB Counters [<a href="#ref-3" title="&quot;Structure and Identification of Management Information for TCP/IP-based Internets&quot;">3</a>].
245
246 OutLQRs
247
248 OutLQRs is a 32-bit counter which increases by one for each
249 tranmitted Link-Quality-Report packet. This counter MUST be set
250 to zero when the LCP enters the Establishment phase, and MUST NOT
251 be reset until the LCP leaves the Termination phase. This counter
252 is incremented before it is inserted into the LQR packet.
253
254 InLQRs
255
256 InLQRs is a 32-bit counter which increases by one for each
257 received Link-Quality-Report packet. This counter MUST be set to
258 zero when the LCP enters the Establishment phase, and MUST NOT be
259 reset until the LCP leaves the Termination phase. This counter is
260 incremented before it is inserted (in an implementation dependent
261 fashion) into the LQR packet.
262
263 InGoodOctets
264
265 InGoodOctets is a 32-bit counter which increases by the number of
266 octets in each successfully received Data Link Layer packet.
267 Unlike the MIB ifInOctets, octets for frames which are counted in
268 ifInDiscards and ifInErrors MUST NOT be counted. This counter MAY
269 be set to any initial value when the LCP enters the Establishment
270 phase, but MUST NOT be reset until the LCP leaves the Termination
271 phase.
272
273
274
275
276 <span class="grey">Simpson [Page 3]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
278 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
279
280
281 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Counting Packets and Octets</span>
282
283 The intent of the counters is to provide an indication of the amount
284 of information passing over the link, rather than an actual
285 measurement of the total bandwidth used. This specification is
286 designed to yield the same count in various circumstances, such as
287 when a separate device provides the framing and escaping mechanisms
288 invisibly to the implementation, or a synchronous-to-asynchronous
289 converter in the link changes between mechanisms.
290
291 All octets which are included in the FCS calculation MUST be counted,
292 including the packet header, the information field, and any padding.
293 The FCS octets MUST also be counted, and one flag octet per frame
294 MUST be counted. All other octets (such as additional flag
295 sequences, and escape bits or octets) MUST NOT be counted.
296
297 When inserting the packet and octet counts in the LQR, the counts
298 MUST include the expected values for the LQR itself.
299
300 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Processes</span>
301
302 The PPP Link Quality Monitoring mechanism is described using a
303 "logical process" model. As shown below, there are five logical
304 processes duplicated at each end of the duplex link.
305
306 +---------+ +-------+ +----+ Outbound
307 | |--&gt;| Mux |--&gt;| Tx |=========&gt;
308 | Link- | +-------+ +----+
309 | Manager |
310 | | +-------+ +----+ Inbound
311 | |&lt;--| Demux |&lt;--| Rx |&lt;=========
312 +---------+ +-------+ +----+
313
314 Link-Manager
315
316 The Link-Manager process transmits and receives Link-Quality-
317 Reports, and implements the desired link quality policy. LQR
318 packets are transmitted at a constant rate, which is negotiated by
319 the LCP Quality-Protocol Configuration Option.
320
321 Mux
322
323 The Mux process multiplexes packets from the various protocols
324 (e.g., LCP, IP, XNS, etc.) into a single, sequential, and
325 prioritized stream of packets. Link-Quality-Report packets MUST
326 be given the highest possible priority to insure that link quality
327 information is communicated in a timely manner.
328
329
330
331
332 <span class="grey">Simpson [Page 4]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
334 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
335
336
337 Tx
338
339 The Tx process maintains the MIB counters ifOutUniPackets and
340 ifOutOctets, and the internal counter OutLQRs, which are used to
341 measure the amount of data which is transmitted on the outbound
342 link. When Tx processes a Link-Quality-Report packet, it inserts
343 the values of these counters into the corresponding PeerOut...
344 fields of the packet. The Tx process MUST follow the Mux process
345 so that packets are counted in the order transmitted to the link.
346
347 Rx
348
349 The Rx process maintains the MIB counters ifInUniPackets,
350 ifInDiscards, ifInErrors and IfInOctets, and the internal counters
351 InLQRs and InGoodOctets, which are used to measure the amount of
352 data which is received by the inbound link. When Rx processes a
353 Link-Quality-Report packet, it inserts the values of these
354 counters into the corresponding SaveIn... fields of the packet (in
355 an implementation dependent manner).
356
357 Demux
358
359 The Demux process demultiplexes packets for the various protocols.
360 The Demux process MUST follow the Rx process so that packets are
361 counted in the order received from the link.
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Simpson [Page 5]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
390 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
391
392
393 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Configuration Option Format</span>
394
395
396 Description
397
398 Implementations MUST be prepared to receive the Quality-Protocol
399 Configuration Option for the Link-Quality-Report. However,
400 negotiation is not required. Negotiation is only necessary when
401 the implementation wishes to ensure that the peer transmits Link-
402 Quality-Reports as opposed to some other Quality-Protocol, or else
403 to prevent the peer from maintaining its own timer, or else to
404 establish a maximum time between transmissions of Link-Quality-
405 Reports.
406
407 A summary of the Quality-Protocol Configuration Option format to
408 negotiate the Link-Quality-Report is shown below. The fields are
409 transmitted from left to right.
410
411 0 1 2 3
412 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
413 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
414 | Type | Length | Quality-Protocol |
415 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
416 | Reporting-Period |
417 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
418
419 Type
420
421 4
422
423 Length
424
425 8
426
427 Quality-Protocol
428
429 c025 (hex) for Link-Quality-Report
430
431 Reporting-Period
432
433 The Reporting-Period field is four octets and indicates the
434 maximum time in hundredths of seconds between transmission of
435 packets. The peer MAY transmit packets at a faster rate than that
436 which was negotiated.
437
438 A value of zero indicates that the peer does not need to maintain
439 a timer. Instead, the peer generates a LQR immediately upon
440 receiving a LQR. A value of zero MUST be Nak'd by the peer with
441
442
443
444 <span class="grey">Simpson [Page 6]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
446 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
447
448
449 an appropriate non-zero value when that peer has sent or will send
450 a Configure-Request packet containing the Quality-Protocol
451 Configuration Option for the Link-Quality-Report with a zero
452 Reporting-Period.
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500 <span class="grey">Simpson [Page 7]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
502 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
503
504
505 <span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Packet Format</span>
506
507 Exactly one Link-Quality-Report packet is encapsulated in the
508 Information field of PPP Data Link Layer frames where the protocol
509 field indicates type hex c025 (Link-Quality-Report). A summary of
510 the LQR packet format is shown below. The names of the fields are
511 relative to the packet receiver, since it is the receiver who
512 requested the packet in the Configuration Option. The fields are
513 transmitted from left to right.
514
515 0 1 2 3
516 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
517 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
518 | Magic-Number |
519 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
520 | LastOutLQRs |
521 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
522 | LastOutPackets |
523 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
524 | LastOutOctets |
525 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
526 | PeerInLQRs |
527 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
528 | PeerInPackets |
529 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
530 | PeerInDiscards |
531 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
532 | PeerInErrors |
533 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
534 | PeerInOctets |
535 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
536 | PeerOutLQRs |
537 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
538 | PeerOutPackets |
539 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
540 | PeerOutOctets |
541 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
542
543 The following fields are not actually transmitted over the inbound
544 link. Rather, they are logically appended (in an implementation
545 dependent manner) to the packet by the implementation's Rx process.
546
547 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
548 | SaveInLQRs |
549 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
550 | SaveInPackets |
551 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
552 | SaveInDiscards |
553
554
555
556 <span class="grey">Simpson [Page 8]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
558 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
559
560
561 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
562 | SaveInErrors |
563 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
564 | SaveInOctets |
565 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
566
567 Magic-Number
568
569 The Magic-Number field is four octets and aids in detecting links
570 which are in the looped-back condition. Unless modified by a
571 Configuration Option, the Magic-Number MUST be transmitted as zero
572 and MUST be ignored on reception. If Magic-Numbers have been
573 negotiated, incoming LQR packets SHOULD be checked to ensure that
574 the local end is not seeing its own Magic-Number and thus a
575 looped-back link. See the Magic-Number Configuration Option for
576 further explanation.
577
578 LastOutLQRs
579
580 The LastOutLQRs field is four octets, and is copied from the most
581 recently received PeerOutLQRs on transmission.
582
583 LastOutPackets
584
585 The LastOutPackets field is four octets, and is copied from the
586 most recently received PeerOutPackets on transmission.
587
588 LastOutOctets
589
590 The LastOutOctets field is four octets, and is copied from the
591 most recently received PeerOutOctets on transmission.
592
593 PeerInLQRs
594
595 The PeerInLQRs field is four octets, and is copied from the most
596 recently received SaveInLQRs on transmission.
597
598 Whenever the PeerInLQRs field is discovered to be zero, the
599 LastOut... fields are indeterminate, and the PeerIn... fields
600 contain the initial values for the peer.
601
602 PeerInPackets
603
604 The PeerInPackets field is four octets, and is copied from the
605 most recently received SaveInPackets on transmission.
606
607
608
609
610
611
612 <span class="grey">Simpson [Page 9]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
614 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
615
616
617 PeerInDiscards
618
619 The PeerInDiscards field is four octets, and is copied from the
620 most recently received SaveInDiscards on transmission.
621
622 PeerInErrors
623
624 The PeerInErrors field is four octets, and is copied from the most
625 recently received SaveInErrors on transmission.
626
627 PeerInOctets
628
629 The PeerInOctets field is four octets, and is copied from the most
630 recently received SaveInOctets on transmission.
631
632 PeerOutLQRs
633
634 The PeerOutLQRs field is four octets, and is copied from OutLQRs
635 on transmission. This number MUST include this LQR.
636
637 PeerOutPackets
638
639 The PeerOutPackets field is four octets, and is copied from the
640 current MIB ifOutUniPackets and ifOutNUniPackets on transmission.
641 This number MUST include this LQR.
642
643 PeerOutOctets
644
645 The PeerOutOctets field is four octets, and is copied from the
646 current MIB ifOutOctets on transmission. This number MUST include
647 this LQR.
648
649 SaveInLQRs
650
651 The SaveInLQRs field is four octets, and is copied from InLQRs on
652 reception. This number MUST include this LQR.
653
654 SaveInPackets
655
656 The SaveInPackets field is four octets, and is copied from the
657 current MIB ifInUniPackets and ifInNUniPackets on reception. This
658 number MUST include this LQR.
659
660 SaveInDiscards
661
662 The SaveInDiscards field is four octets, and is copied from the
663 current MIB ifInDiscards on reception. This number MUST include
664 this LQR.
665
666
667
668 <span class="grey">Simpson [Page 10]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
670 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
671
672
673 SaveInErrors
674
675 The SaveInErrors field is four octets, and is copied from the
676 current MIB ifInErrors on reception. This number MUST include
677 this LQR.
678
679 SaveInOctets
680
681 The SaveInOctets field is four octets, and is copied from the
682 current InGoodOctets on reception. This number MUST include this
683 LQR.
684
685 Note that InGoodOctets is not the same as the MIB ifInOctets
686 counter, as InGoodOctets does not include octets for packets which
687 are discards or errors.
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724 <span class="grey">Simpson [Page 11]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
726 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
727
728
729 <span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Transmission of Reports</span>
730
731 When the PPP Link Control Protocol has reached the Opened state, the
732 Link Quality Monitoring process MAY commence sending Link-Quality-
733 Reports. If a Protocol-Reject is received specifying a LQR packet,
734 the LQM process MUST cease sending LQRs.
735
736 Usually, the LQR is transmitted when the LQR timer for the link
737 expires. If no LQR timer is used, a LQR is generated upon receipt of
738 an incoming LQR. The negotiation process ensures that at least one
739 side of the link is using a LQR timer.
740
741 In addition, a LQR is generated whenever two successive LQRs are
742 received which have the same PeerInLQRs value. This may indicate
743 that a LQR has been missed, or that the implementation is sending at
744 a significantly slower rate than the peer, or that the peer has
745 accelerated LQR generation to better quantify errors on the link.
746
747 Whenever a LQR is sent, the LQR timer MUST be restarted.
748
749 <span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Calculations</span>
750
751 Each time a Link-Quality-Report packet is received from the inbound
752 link, the Link-Manager can compare the associated fields. The fields
753 of the previous LQR can be subtracted from the current LQR values to
754 obtain an absolute "delta", which allows comparision of the changes
755 seen by each end of the link.
756
757 If the received PeerInLQRs field is zero, the LastOut... fields are
758 indeterminate, and the PeerIn... fields contain the initial values
759 for the peer. No calculations using these fields can be performed at
760 this time.
761
762 Implementation Note:
763
764 The following counters wrap to zero when their maximum value is
765 reached. Care must be taken to ensure that correct "delta"
766 calculations are performed at that time.
767
768 The LastOutLQRs field may be directly compared with the PeerInLQRs
769 field to determine how many outbound LQRs have been lost.
770
771 The LastOutLQRs field may be directly compared with the OutLQRs
772 counter to determine how many outbound LQRs are still in the
773 pipeline.
774
775 The change in PeerInPackets may be compared with the change in
776 LastOutPackets to determine the number of lost packets over the
777
778
779
780 <span class="grey">Simpson [Page 12]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
782 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
783
784
785 outgoing link.
786
787 The change in PeerInOctets may be compared with the change in
788 LastOutOctets to determine the number of lost octets over the
789 outgoing link.
790
791 The change in SaveInPackets may be compared with the change in
792 PeerOutPackets to determine the number of lost packets over the
793 incoming link.
794
795 The change in SaveInOctets may be compared with the change in
796 PeerOutOctets to determine the number of lost octets over the
797 incoming link.
798
799 The change in the PeerInDiscards and PeerInErrors fields may be used
800 to determine whether packet loss is due to congestion in the peer
801 rather than physical link failure.
802
803 <span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Failure Detection</span>
804
805 When the link is operating well in both directions of the link, the
806 LQR is superfluous. The maximum time interval for transmitting LQRs
807 SHOULD be chosen to minimally interfere with active traffic.
808
809 When there is a measurable loss of data in either direction, if the
810 overall throughput is adequate, conditions are not severe enough to
811 warrant dropping the link. Sending LQRs faster will gain nothing,
812 except to measure peaks in the loss rate. The time interval MUST be
813 chosen to be long enough to have a good smoothing effect on the data,
814 while short enough to ensure fast enough response to complete
815 failure.
816
817 When the link is good incoming, but very bad outgoing, incoming LQRs
818 indicate a high loss on the outgoing side of the link. Sending LQRs
819 faster won't help, because they are probably lost on the way to the
820 peer.
821
822 When the link is good outgoing, but very bad incoming, incoming LRQs
823 will be frequently lost. In this case, LQRs SHOULD be sent at a
824 faster rate. This primarily relies on the peer to make an informed
825 policy decision. The peer will also send LQRs in response (due to
826 the duplicate PeerInLQRs field), and some of those LQRs may
827 successfully arrive.
828
829 When a LQR does not arrive within the time expected, or the LQR
830 received indicates that the links are truly bad, at least one
831 additional LQR SHOULD be sent. An algorithmic decision requires at
832 least 2 round trip intervals. The loss rate could be transient, due
833
834
835
836 <span class="grey">Simpson [Page 13]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
838 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
839
840
841 to a heavily loaded link, or a lost outgoing LQR.
842
843 <span class="h3"><a class="selflink" id="section-2.10" href="#section-2.10">2.10</a>. Policy Suggestions</span>
844
845 Link-Quality-Report packets provide a mechanism to determine the link
846 quality, but it is up to each implementation to decide when the link
847 is usable. It is recommended that this policy implement some amount
848 of hysteresis so that the link does not bounce up and down. One
849 policy is to use a K out of N algorithm. In such an algorithm, there
850 must be K successes out of the last N periods for the link to be
851 considered of good quality.
852
853 Procedures for recovery from poor quality links are unspecified and
854 may vary from implementation to implementation. A suggested approach
855 is to immediately close all other Network-Layer protocols (i.e.,
856 cause IPCP to transmit a Terminate-Request), but to continue
857 transmitting Link-Quality-Reports. Once the link quality again
858 reaches an acceptable level, Network-Layer protocols can be
859 reconfigured.
860
861 Security Considerations
862
863 Security issues are not discussed in this memo.
864
865 References
866
867 [<a id="ref-1">1</a>] Simpson, W., "The Point-to-Point Protocol", <a href="./rfc1331">RFC 1331</a>, May 1992.
868
869 [<a id="ref-2">2</a>] McCloghrie, K., and M. Rose, "Management Information Base for
870 Network Management of TCP/IP-based internets: MIB-II", <a href="./rfc1213">RFC</a>
871 <a href="./rfc1213">1213</a>, March 1991.
872
873 [<a id="ref-3">3</a>] Rose, M., and K. McCloghrie, "Structure and Identification of
874 Management Information for TCP/IP-based Internets", <a href="./rfc1155">RFC 1155</a>,
875 May 1990.
876
877 Acknowledgments
878
879 Some of the text in this document is taken from <a href="./rfc1172">RFC 1172</a>, by Drew
880 Perkins of Carnegie Mellon University, and by Russ Hobby of the
881 University of California at Davis.
882
883 Special thanks to Craig Fox (Network Systems), and Karl Fox (Morning
884 Star Technologies), for design suggestions based on implementation
885 experience.
886
887
888
889
890
891
892 <span class="grey">Simpson [Page 14]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
894 <span class="grey"><a href="./rfc1333">RFC 1333</a> PPP Link Quality Monitoring May 1992</span>
895
896
897 Chair's Address
898
899 The working group can be contacted via the current chair:
900
901 Brian Lloyd
902 Lloyd &amp; Associates
903 3420 Sudbury Road
904 Cameron Park, California 95682
905
906 Phone: (916) 676-1147
907
908 EMail: [email protected]
909
910
911
912 Author's Address
913
914 Questions about this memo can also be directed to:
915
916 William Allen Simpson
917 Daydreamer
918 Computer Systems Consulting Services
919 P O Box 6205
920 East Lansing, MI 48826-6025
921
922 EMail: [email protected]
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948 Simpson [Page 15]
949 </pre>