Debian Codegraph @

rfc1989.html

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