Debian Codegraph @

rfc1471.html

raw
1 <pre>Network Working Group F. Kastenholz
2 Request for Comments: 1471 FTP Software, Inc.
3 June 1993
4
5
6 <span class="h1">The Definitions of Managed Objects for</span>
7 <span class="h1">the Link Control Protocol of</span>
8 <span class="h1">the Point-to-Point Protocol</span>
9
10 Status of this Memo
11
12 This RFC specifies an IAB standards track protocol for the Internet
13 community, and requests discussion and suggestions for improvements.
14 Please refer to the current edition of the "IAB Official Protocol
15 Standards" for the standardization state and status of this protocol.
16 Distribution of this memo is unlimited.
17
18 Abstract
19
20 This memo defines a portion of the Management Information Base (MIB)
21 for use with network management protocols in TCP/IP-based internets.
22 In particular, it describes managed objects used for managing the
23 Link Control Protocol and Link Quality Monitoring on subnetwork
24 interfaces that use the family of Point-to-Point Protocols [8, 9, 10,
25 11, &amp; 12].
26
27 Table of Contents
28
29 <a href="#section-1">1</a>. The Network Management Framework ...................... <a href="#page-2">2</a>
30 <a href="#section-2">2</a>. Objects ............................................... <a href="#page-2">2</a>
31 <a href="#section-2.1">2.1</a> Format of Definitions ................................ <a href="#page-2">2</a>
32 <a href="#section-3">3</a>. Overview .............................................. <a href="#page-2">2</a>
33 <a href="#section-3.1">3.1</a> Object Selection Criteria ............................ <a href="#page-2">2</a>
34 <a href="#section-3.2">3.2</a> Structure of the PPP ................................. <a href="#page-3">3</a>
35 <a href="#section-3.3">3.3</a> MIB Groups ........................................... <a href="#page-4">4</a>
36 3.4 Relationship to Interface and Interface Extensions
37 Groups ............................................... <a href="#page-5">5</a>
38 <a href="#section-4">4</a>. Definitions ........................................... <a href="#page-6">6</a>
39 <a href="#section-4.1">4.1</a> PPP Link Group ....................................... <a href="#page-7">7</a>
40 <a href="#section-4.2">4.2</a> PPP LQR Group ........................................ <a href="#page-16">16</a>
41 <a href="#section-4.3">4.3</a> PPP LQR Extensions Group ............................. <a href="#page-21">21</a>
42 <a href="#section-4.4">4.4</a> PPP Tests ............................................ <a href="#page-22">22</a>
43 <a href="#section-4.4.1">4.4.1</a> PPP Echo Test ...................................... <a href="#page-22">22</a>
44 <a href="#section-4.4.2">4.4.2</a> PPP Discard Test ................................... <a href="#page-23">23</a>
45 <a href="#section-5">5</a>. Acknowledgements ...................................... <a href="#page-23">23</a>
46 <a href="#section-6">6</a>. Security Considerations ............................... <a href="#page-23">23</a>
47 <a href="#section-7">7</a>. References ............................................ <a href="#page-24">24</a>
48 <a href="#section-8">8</a>. Author's Address ...................................... <a href="#page-25">25</a>
49
50
51
52 <span class="grey">Kastenholz [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. The Network Management Framework</span>
58
59 The Internet-standard Network Management Framework consists of three
60 components. They are:
61
62 STD 16/RFC 1155 which defines the SMI, the mechanisms used for
63 describing and naming objects for the purpose of management. STD
64 16/RFC 1212 defines a more concise description mechanism, which is
65 wholly consistent with the SMI.
66
67 STD 17/RFC 1213 which defines MIB-II, the core set of managed
68 objects for the Internet suite of protocols.
69
70 STD 15/RFC 1157 which defines the SNMP, the protocol used for
71 network access to managed objects.
72
73 The Framework permits new objects to be defined for the purpose of
74 experimentation and evaluation.
75
76 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Objects</span>
77
78 Managed objects are accessed via a virtual information store, termed
79 the Management Information Base or MIB. Objects in the MIB are
80 defined using the subset of Abstract Syntax Notation One (ASN.1) [<a href="#ref-3" title=" International Organization for Standardization">3</a>]
81 defined in the SMI. In particular, each object type is named by an
82 OBJECT IDENTIFIER, an administratively assigned name. The object
83 type together with an object instance serves to uniquely identify a
84 specific instantiation of the object. For human convenience, we
85 often use a textual string, termed the descriptor, to refer to the
86 object type.
87
88 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Format of Definitions</span>
89
90 <a href="#section-4">Section 4</a> contains the specification of all object types contained in
91 this MIB module. The object types are defined using the conventions
92 defined in the SMI, as amended by the extensions specified in [<a href="#ref-5" title="&quot;Concise MIB Definitions&quot;">5</a>,<a href="#ref-6" title="&quot;A Convention for Defining Traps for use with the SNMP&quot;">6</a>].
93
94 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Overview</span>
95
96 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Object Selection Criteria</span>
97
98 To be consistent with IAB directives and good engineering practice,
99 an explicit attempt was made to keep this MIB as simple as possible.
100 This was accomplished by applying the following criteria to objects
101 proposed for inclusion:
102
103 (1) Require objects be essential for either fault or
104 configuration management. In particular, objects for
105
106
107
108 <span class="grey">Kastenholz [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
111
112
113 which the sole purpose was to debug implementations were
114 explicitly excluded from the MIB.
115
116 (2) Consider evidence of current use and/or utility.
117
118 (3) Limit the total number of objects.
119
120 (4) Exclude objects which are simply derivable from others in
121 this or other MIBs.
122
123 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Structure of the PPP</span>
124
125 This section describes the basic model of PPP used in developing the
126 PPP MIB. This information should be useful to the implementor in
127 understanding some of the basic design decisions of the MIB.
128
129 The PPP is not one single protocol but a large family of protocols.
130 Each of these is, in itself, a fairly complex protocol. The PPP
131 protocols may be divided into three rough categories:
132
133 Control Protocols
134 The Control Protocols are used to control the operation of the
135 PPP. The Control Protocols include the Link Control Protocol
136 (LCP), the Password Authentication Protocol (PAP), the Link
137 Quality Report (LQR), and the Challenge Handshake Authentication
138 Protocol (CHAP).
139
140 Network Protocols
141 The Network Protocols are used to move the network traffic over
142 the PPP interface. A Network Protocol encapsulates the datagrams
143 of a specific higher-layer protocol that is using the PPP as a
144 data link. Note that within the context of PPP, the term "Network
145 Protocol" does not imply an OSI Layer-3 protocol; for instance,
146 there is a Bridging network protocol.
147
148 Network Control Protocols (NCPs)
149 The NCPs are used to control the operation of the Network
150 Protocols. Generally, each Network Protocol has its own Network
151 Control Protocol; thus, the IP Network Protocol has its IP Control
152 Protocol, the Bridging Network Protocol has its Bridging Network
153 Control Protocol and so on.
154
155 This document specifies the objects used in managing one of these
156 protocols, namely the Link Control Protocol and Link Quality
157 Monitoring Protocol.
158
159
160
161
162
163
164 <span class="grey">Kastenholz [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
167
168
169 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. MIB Groups</span>
170
171 Objects in this MIB are arranged into several MIB groups. Each group
172 is organized as a set of related objects.
173
174 These groups are the basic unit of conformance: if the semantics of a
175 group are applicable to an implementation then all objects in the
176 group must be implemented.
177
178 The PPP MIB is organized into several MIB Groups, including, but not
179 limited to, the following groups:
180
181 o The PPP Link Group
182 o The PPP LQR Group
183 o The PPP LQR Extensions Group
184 o The PPP IP Group
185 o The PPP Bridge Group
186 o The PPP Security Group
187
188 This document specifies the following groups:
189
190 The PPP Link Group
191 This group represents the lowest "level" of the PPP protocol.
192
193 This group contains two tables, one containing status information
194 and the other configuration information. The configuration table
195 is split off of the status so that it may be placed in a separate
196 MIB View for security purposes.
197
198 Implementation of this group is mandatory for all PPP
199 implementations.
200
201 The PPP LQR Group
202 This group provides the basic MIB variables that apply to the PPP
203 LQR Protocol. This group provides MIB access to the information
204 required for LQR processing. This group contains two tables, one
205 containing status information and the other configuration
206 information. The configuration table is split off of the status
207 so that it may be placed in a separate MIB View for security
208 purposes.
209
210 Implementation of the PPP LQR Group is mandatory for all PPP
211 implementations that implement LQR.
212
213 The PPP LQR Extensions Group
214 The PPP LQR Extensions group contains the most recently received
215 LQR packet, as well as the "save" fields that are "logically
216 appended" [<a href="#ref-12" title="&quot;PPP Link Quality Monitoring&quot;">12</a>] to received LQR packets. This is done in order to
217
218
219
220 <span class="grey">Kastenholz [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
223
224
225 facilitate external implementations of the Link Quality Monitoring
226 policies.
227
228 It is not practical to examine the relevant MIB objects which are
229 used to generate LQR packets since LQR policies may require
230 synchronization of the values of all data used to determine Link
231 Quality; i.e., the values of the relevant counters must all be
232 taken at the same instant in time. Thus, by recording the last
233 received LQR packet, a synchronized record of the relevant data is
234 available.
235
236 As this information may not be efficiently maintained on all PPP
237 implementations, implementation of this group is optional.
238
239 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Relationship to Interface and Interface Extensions</span>
240 <span class="h3"> Groups</span>
241
242 The PPP Mib is a medium-specific extension to the standard MIB-2
243 interface group [<a href="#ref-2" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">2</a>] and to the Interface Extensions MIB [<a href="#ref-7" title="&quot;Extensions to the Generic-Interface MIB&quot;">7</a>]. This
244 section discusses certain components of these groups when the
245 interface is a PPP interface.
246
247 The PPP interface represents a single interface in the sense used in
248 [<a href="#ref-2" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">2</a>] and thus has a single entry in the ifTable.
249
250 Furthermore, the PPP interface may be operating over a lower layer
251 hardware interface (such as an RS-232 port). It is important to
252 capture the relationship between the PPP interface and the lower-
253 layer interface over which it operates. This MIB presumes that the
254 lower-layer interface has an ifEntry associated with it. The lower-
255 layer ifEntry is identified via the pppLinkStatusPhysicalIndex
256 object, which contains the value of ifIndex for the lower-layer
257 ifEntry.
258
259 For example, suppose that you run PPP over a RS-232 port. This would
260 use two entries in the ifTable. Let's suppose that entry number 123
261 is for the PPP "interface" and entry number 987 is for the RS-232
262 port. So, ifSpecific.123 would contain the ppp OBJECT IDENTIFIER,
263 pppLinkStatusPhysicalIndex.123 would contain 987, and ifSpecific.987
264 would contain the rs_232 OBJECT IDENTIFIER (or whatever it is).
265
266 All PPP packets are defined in [<a href="#ref-8" title="W.">8</a>] as being broadcast packets. Thus,
267 the packets are counted as non-unicast packets in the ifTable
268 (ifInNUcastPkts and ifOutNUCastPkts) and as broadcasts in the
269 ifExtnsTable (ifExtnsBroadcastsReceivedOks and
270 ifExtnsBroadcastsTransmittedOks).
271
272
273
274
275
276 <span class="grey">Kastenholz [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
279
280
281 ifSpecific
282 Contains the OBJECT IDENTIFIER ppp.
283
284 ifAdminStatus
285 Setting this object to up will inject an administrative open event
286 into the LCP's finite state machine. Setting this object to down
287 will inject an administrative close event into the LCP's finite
288 state machine.
289
290 The use of the testing value is beyond the scope of this document.
291
292 ifOperStatus
293 Represents the state of the LCP Finite State Machine. If the
294 Finite State Machine is in the Opened state then the value of
295 ifOperStatus is up, otherwise the value of ifOperStatus is down.
296
297 The meaning of the testing value is beyond the scope of this
298 document.
299
300 Per the SNMP Protocol Specification [<a href="#ref-13" title="&quot;Simple Network Management Protocol&quot;">13</a>], the linkUp and linkDown
301 traps apply to the PPP Protocol entity. When the LCP's Finite State
302 Machine attains the Opened state, a linkUp trap should be sent. When
303 the Finite State Machine leaves the Opened state, a linkDown trap
304 should be sent.
305
306 Some tests for the link are defined in this document. Execution of
307 these tests does not place the link's ifOperStatus in the testing
308 state as these tests do not prevent normal data transmission from
309 occuring over the link.
310
311 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Definitions</span>
312
313 PPP-LCP-MIB DEFINITIONS ::= BEGIN
314
315 IMPORTS
316 Counter
317 FROM <a href="./rfc1155">RFC1155</a>-SMI
318 ifIndex, transmission
319 FROM <a href="./rfc1213">RFC1213</a>-MIB
320 OBJECT-TYPE
321 FROM <a href="./rfc1212">RFC-1212</a>;
322
323 -- PPP MIB
324
325 ppp OBJECT IDENTIFIER ::= { transmission 23 }
326
327 pppLcp OBJECT IDENTIFIER ::= { ppp 1 }
328
329
330
331
332 <span class="grey">Kastenholz [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
335
336
337 -- The individual groups within the PPP-LCP-MIB
338
339 pppLink OBJECT IDENTIFIER ::= { pppLcp 1 }
340 pppLqr OBJECT IDENTIFIER ::= { pppLcp 2 }
341 pppTests OBJECT IDENTIFIER ::= { pppLcp 3 }
342
343
344 -- 4.1. PPP Link Group
345
346
347 --
348 -- The PPP Link Group. Implementation of this
349 -- group is mandatory for all PPP entities.
350 --
351
352 -- The following object reflect the values of the option
353 -- parameters used in the PPP Link Control Protocol
354 -- pppLinkStatusLocalMRU
355 -- pppLinkStatusRemoteMRU
356 -- pppLinkStatusLocalToPeerACCMap
357 -- pppLinkStatusPeerToLocalACCMap
358 -- pppLinkStatusLocalToRemoteProtocolCompression
359 -- pppLinkStatusRemoteToLocalProtocolCompression
360 -- pppLinkStatusLocalToRemoteACCompression
361 -- pppLinkStatusRemoteToLocalACCompression
362 -- pppLinkStatusTransmitFcsSize
363 -- pppLinkStatusReceiveFcsSize
364 --
365 -- These values are not available until after the PPP Option
366 -- negotiation has completed, which is indicated by the link
367 -- reaching the open state (i.e., ifOperStatus is set to
368 -- up).
369 --
370 -- Therefore, when ifOperStatus is not up
371 -- the contents of these objects is undefined. The value
372 -- returned when accessing the objects is an implementation
373 -- dependent issue.
374
375
376 pppLinkStatusTable OBJECT-TYPE
377 SYNTAX SEQUENCE OF PppLinkStatusEntry
378 ACCESS not-accessible
379 STATUS mandatory
380 DESCRIPTION
381 "A table containing PPP-link specific variables
382 for this PPP implementation."
383 ::= { pppLink 1 }
384
385
386
387
388 <span class="grey">Kastenholz [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
391
392
393 pppLinkStatusEntry OBJECT-TYPE
394 SYNTAX PppLinkStatusEntry
395 ACCESS not-accessible
396 STATUS mandatory
397 DESCRIPTION
398 "Management information about a particular PPP
399 Link."
400 INDEX { ifIndex }
401 ::= { pppLinkStatusTable 1 }
402
403
404 PppLinkStatusEntry ::= SEQUENCE {
405 pppLinkStatusPhysicalIndex
406 INTEGER,
407 pppLinkStatusBadAddresses
408 Counter,
409 pppLinkStatusBadControls
410 Counter,
411 pppLinkStatusPacketTooLongs
412 Counter,
413 pppLinkStatusBadFCSs
414 Counter,
415 pppLinkStatusLocalMRU
416 INTEGER,
417 pppLinkStatusRemoteMRU
418 INTEGER,
419 pppLinkStatusLocalToPeerACCMap
420 OCTET STRING,
421 pppLinkStatusPeerToLocalACCMap
422 OCTET STRING,
423 pppLinkStatusLocalToRemoteProtocolCompression
424 INTEGER,
425 pppLinkStatusRemoteToLocalProtocolCompression
426 INTEGER,
427 pppLinkStatusLocalToRemoteACCompression
428 INTEGER,
429 pppLinkStatusRemoteToLocalACCompression
430 INTEGER,
431 pppLinkStatusTransmitFcsSize
432 INTEGER,
433 pppLinkStatusReceiveFcsSize
434 INTEGER
435 }
436 pppLinkStatusPhysicalIndex OBJECT-TYPE
437 SYNTAX INTEGER(0..2147483647)
438 ACCESS read-only
439 STATUS mandatory
440 DESCRIPTION
441
442
443
444 <span class="grey">Kastenholz [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
447
448
449 "The value of ifIndex that identifies the
450 lower-level interface over which this PPP Link
451 is operating. This interface would usually be
452 an HDLC or RS-232 type of interface. If there
453 is no lower-layer interface element, or there
454 is no ifEntry for the element, or the element
455 can not be identified, then the value of this
456 object is 0. For example, suppose that PPP is
457 operating over a serial port. This would use
458 two entries in the ifTable. The PPP could be
459 running over `interface' number 123 and the
460 serial port could be running over `interface'
461 number 987. Therefore, ifSpecific.123 would
462 contain the OBJECT IDENTIFIER ppp
463 pppLinkStatusPhysicalIndex.123 would contain
464 987, and ifSpecific.987 would contain the
465 OBJECT IDENTIFIER for the serial-port's media-
466 specific MIB."
467 ::= { pppLinkStatusEntry 1 }
468
469
470 pppLinkStatusBadAddresses OBJECT-TYPE
471 SYNTAX Counter
472 ACCESS read-only
473 STATUS mandatory
474 DESCRIPTION
475 "The number of packets received with an
476 incorrect Address Field. This counter is a
477 component of the ifInErrors variable that is
478 associated with the interface that represents
479 this PPP Link."
480 REFERENCE
481 "<a href="#section-3.1">Section 3.1</a>, Address Field, of <a href="./rfc1331">RFC1331</a>."
482 ::= { pppLinkStatusEntry 2 }
483
484
485 pppLinkStatusBadControls OBJECT-TYPE
486 SYNTAX Counter
487 ACCESS read-only
488 STATUS mandatory
489 DESCRIPTION
490 "The number of packets received on this link
491 with an incorrect Control Field. This counter
492 is a component of the ifInErrors variable that
493 is associated with the interface that
494 represents this PPP Link."
495 REFERENCE
496 "<a href="#section-3.1">Section 3.1</a>, Control Field, of <a href="./rfc1331">RFC1331</a>."
497
498
499
500 <span class="grey">Kastenholz [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
503
504
505 ::= { pppLinkStatusEntry 3 }
506
507
508 pppLinkStatusPacketTooLongs OBJECT-TYPE
509 SYNTAX Counter
510 ACCESS read-only
511 STATUS mandatory
512 DESCRIPTION
513 "The number of received packets that have been
514 discarded because their length exceeded the
515 MRU. This counter is a component of the
516 ifInErrors variable that is associated with the
517 interface that represents this PPP Link. NOTE,
518 packets which are longer than the MRU but which
519 are successfully received and processed are NOT
520 included in this count."
521 ::= { pppLinkStatusEntry 4 }
522
523
524 pppLinkStatusBadFCSs OBJECT-TYPE
525 SYNTAX Counter
526 ACCESS read-only
527 STATUS mandatory
528 DESCRIPTION
529 "The number of received packets that have been
530 discarded due to having an incorrect FCS. This
531 counter is a component of the ifInErrors
532 variable that is associated with the interface
533 that represents this PPP Link."
534 ::= { pppLinkStatusEntry 5 }
535
536
537 pppLinkStatusLocalMRU OBJECT-TYPE
538 SYNTAX INTEGER(1..2147483648)
539 ACCESS read-only
540 STATUS mandatory
541 DESCRIPTION
542 "The current value of the MRU for the local PPP
543 Entity. This value is the MRU that the remote
544 entity is using when sending packets to the
545 local PPP entity. The value of this object is
546 meaningful only when the link has reached the
547 open state (ifOperStatus is up)."
548 ::= { pppLinkStatusEntry 6 }
549
550
551 pppLinkStatusRemoteMRU OBJECT-TYPE
552 SYNTAX INTEGER(1..2147483648)
553
554
555
556 <span class="grey">Kastenholz [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
559
560
561 ACCESS read-only
562 STATUS mandatory
563 DESCRIPTION
564 "The current value of the MRU for the remote
565 PPP Entity. This value is the MRU that the
566 local entity is using when sending packets to
567 the remote PPP entity. The value of this object
568 is meaningful only when the link has reached
569 the open state (ifOperStatus is up)."
570 ::= { pppLinkStatusEntry 7 }
571
572
573 pppLinkStatusLocalToPeerACCMap OBJECT-TYPE
574 SYNTAX OCTET STRING (SIZE (4))
575 ACCESS read-only
576 STATUS mandatory
577 DESCRIPTION
578 "The current value of the ACC Map used for
579 sending packets from the local PPP entity to
580 the remote PPP entity. The value of this object
581 is meaningful only when the link has reached
582 the open state (ifOperStatus is up)."
583 ::= { pppLinkStatusEntry 8 }
584
585
586 pppLinkStatusPeerToLocalACCMap OBJECT-TYPE
587 SYNTAX OCTET STRING (SIZE (4))
588 ACCESS read-only
589 STATUS mandatory
590 DESCRIPTION
591 "The ACC Map used by the remote PPP entity when
592 transmitting packets to the local PPP entity.
593 The value of this object is meaningful only
594 when the link has reached the open state
595 (ifOperStatus is up)."
596 ::= { pppLinkStatusEntry 9 }
597
598
599 pppLinkStatusLocalToRemoteProtocolCompression
600 OBJECT-TYPE
601 SYNTAX INTEGER {
602 enabled(1),
603 disabled(2)
604 }
605 ACCESS read-only
606 STATUS mandatory
607 DESCRIPTION
608 "Indicates whether the local PPP entity will
609
610
611
612 <span class="grey">Kastenholz [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
615
616
617 use Protocol Compression when transmitting
618 packets to the remote PPP entity. The value of
619 this object is meaningful only when the link
620 has reached the open state (ifOperStatus is
621 up)."
622 ::= { pppLinkStatusEntry 10 }
623
624
625 pppLinkStatusRemoteToLocalProtocolCompression
626 OBJECT-TYPE
627 SYNTAX INTEGER {
628 enabled(1),
629 disabled(2)
630 }
631 ACCESS read-only
632 STATUS mandatory
633 DESCRIPTION
634 "Indicates whether the remote PPP entity will
635 use Protocol Compression when transmitting
636 packets to the local PPP entity. The value of
637 this object is meaningful only when the link
638 has reached the open state (ifOperStatus is
639 up)."
640 ::= { pppLinkStatusEntry 11 }
641
642
643 pppLinkStatusLocalToRemoteACCompression OBJECT-TYPE
644 SYNTAX INTEGER {
645 enabled(1),
646 disabled(2)
647 }
648 ACCESS read-only
649 STATUS mandatory
650 DESCRIPTION
651 "Indicates whether the local PPP entity will
652 use Address and Control Compression when
653 transmitting packets to the remote PPP entity.
654 The value of this object is meaningful only
655 when the link has reached the open state
656 (ifOperStatus is up)."
657 ::= { pppLinkStatusEntry 12 }
658
659
660 pppLinkStatusRemoteToLocalACCompression OBJECT-TYPE
661 SYNTAX INTEGER {
662 enabled(1),
663 disabled(2)
664 }
665
666
667
668 <span class="grey">Kastenholz [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
671
672
673 ACCESS read-only
674 STATUS mandatory
675 DESCRIPTION
676 "Indicates whether the remote PPP entity will
677 use Address and Control Compression when
678 transmitting packets to the local PPP entity.
679 The value of this object is meaningful only
680 when the link has reached the open state
681 (ifOperStatus is up)."
682 ::= { pppLinkStatusEntry 13 }
683
684
685 pppLinkStatusTransmitFcsSize OBJECT-TYPE
686 SYNTAX INTEGER (0..128)
687 ACCESS read-only
688 STATUS mandatory
689 DESCRIPTION
690 "The size of the Frame Check Sequence (FCS) in
691 bits that the local node will generate when
692 sending packets to the remote node. The value
693 of this object is meaningful only when the link
694 has reached the open state (ifOperStatus is
695 up)."
696 ::= { pppLinkStatusEntry 14 }
697
698
699 pppLinkStatusReceiveFcsSize OBJECT-TYPE
700 SYNTAX INTEGER (0..128)
701 ACCESS read-only
702 STATUS mandatory
703 DESCRIPTION
704 "The size of the Frame Check Sequence (FCS) in
705 bits that the remote node will generate when
706 sending packets to the local node. The value of
707 this object is meaningful only when the link
708 has reached the open state (ifOperStatus is
709 up)."
710 ::= { pppLinkStatusEntry 15 }
711
712
713 pppLinkConfigTable OBJECT-TYPE
714 SYNTAX SEQUENCE OF PppLinkConfigEntry
715 ACCESS not-accessible
716 STATUS mandatory
717 DESCRIPTION
718 "A table containing the LCP configuration
719 parameters for this PPP Link. These variables
720 represent the initial configuration of the PPP
721
722
723
724 <span class="grey">Kastenholz [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
727
728
729 Link. The actual values of the parameters may
730 be changed when the link is brought up via the
731 LCP options negotiation mechanism."
732 ::= { pppLink 2 }
733
734
735 pppLinkConfigEntry OBJECT-TYPE
736 SYNTAX PppLinkConfigEntry
737 ACCESS not-accessible
738 STATUS mandatory
739 DESCRIPTION
740 "Configuration information about a particular
741 PPP Link."
742 INDEX { ifIndex }
743 ::= { pppLinkConfigTable 1 }
744
745
746 PppLinkConfigEntry ::= SEQUENCE {
747 pppLinkConfigInitialMRU
748 INTEGER,
749 pppLinkConfigReceiveACCMap
750 OCTET STRING,
751 pppLinkConfigTransmitACCMap
752 OCTET STRING,
753 pppLinkConfigMagicNumber
754 INTEGER,
755 pppLinkConfigFcsSize
756 INTEGER
757 }
758
759 pppLinkConfigInitialMRU OBJECT-TYPE
760 SYNTAX INTEGER(0..2147483647)
761 ACCESS read-write
762 STATUS mandatory
763 DESCRIPTION
764 "The initial Maximum Receive Unit (MRU) that
765 the local PPP entity will advertise to the
766 remote entity. If the value of this variable is
767 0 then the local PPP entity will not advertise
768 any MRU to the remote entity and the default
769 MRU will be assumed. Changing this object will
770 have effect when the link is next restarted."
771 REFERENCE
772 "<a href="#section-7.2">Section 7.2</a>, Maximum Receive Unit of <a href="./rfc1331">RFC1331</a>."
773 DEFVAL { 1500 }
774 ::= { pppLinkConfigEntry 1 }
775
776
777
778
779
780 <span class="grey">Kastenholz [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
783
784
785 pppLinkConfigReceiveACCMap OBJECT-TYPE
786 SYNTAX OCTET STRING (SIZE (4))
787 ACCESS read-write
788 STATUS mandatory
789 DESCRIPTION
790 "The Asynchronous-Control-Character-Map (ACC)
791 that the local PPP entity requires for use on
792 its receive side. In effect, this is the ACC
793 Map that is required in order to ensure that
794 the local modem will successfully receive all
795 characters. The actual ACC map used on the
796 receive side of the link will be a combination
797 of the local node's pppLinkConfigReceiveACCMap
798 and the remote node's
799 pppLinkConfigTransmitACCMap. Changing this
800 object will have effect when the link is next
801 restarted."
802 REFERENCE
803 "<a href="#section-7.3">Section 7.3</a>, page 4, Async-Control-Character-
804 Map of <a href="./rfc1331">RFC1331</a>."
805 DEFVAL { 'ffffffff'h }
806 ::= { pppLinkConfigEntry 2 }
807
808
809 pppLinkConfigTransmitACCMap OBJECT-TYPE
810 SYNTAX OCTET STRING (SIZE (4))
811 ACCESS read-write
812 STATUS mandatory
813 DESCRIPTION
814 "The Asynchronous-Control-Character-Map (ACC)
815 that the local PPP entity requires for use on
816 its transmit side. In effect, this is the ACC
817 Map that is required in order to ensure that
818 all characters can be successfully transmitted
819 through the local modem. The actual ACC map
820 used on the transmit side of the link will be a
821 combination of the local node's
822 pppLinkConfigTransmitACCMap and the remote
823 node's pppLinkConfigReceiveACCMap. Changing
824 this object will have effect when the link is
825 next restarted."
826 REFERENCE
827 "<a href="#section-7.3">Section 7.3</a>, page 4, Async-Control-Character-
828 Map of <a href="./rfc1331">RFC1331</a>."
829 DEFVAL { 'ffffffff'h }
830 ::= { pppLinkConfigEntry 3 }
831
832
833
834
835
836 <span class="grey">Kastenholz [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
839
840
841 pppLinkConfigMagicNumber OBJECT-TYPE
842 SYNTAX INTEGER {false (1), true (2)}
843 ACCESS read-write
844 STATUS mandatory
845 DESCRIPTION
846 "If true(2) then the local node will attempt to
847 perform Magic Number negotiation with the
848 remote node. If false(1) then this negotiation
849 is not performed. In any event, the local node
850 will comply with any magic number negotiations
851 attempted by the remote node, per the PPP
852 specification. Changing this object will have
853 effect when the link is next restarted."
854 REFERENCE
855 "<a href="#section-7.6">Section 7.6</a>, Magic Number, of <a href="./rfc1331">RFC1331</a>."
856 DEFVAL { false }
857 ::= { pppLinkConfigEntry 4 }
858
859
860 pppLinkConfigFcsSize OBJECT-TYPE
861 SYNTAX INTEGER (0..128)
862 ACCESS read-write
863 STATUS mandatory
864 DESCRIPTION
865 "The size of the FCS, in bits, the local node
866 will attempt to negotiate for use with the
867 remote node. Regardless of the value of this
868 object, the local node will comply with any FCS
869 size negotiations initiated by the remote node,
870 per the PPP specification. Changing this object
871 will have effect when the link is next
872 restarted."
873 DEFVAL { 16 }
874 ::= { pppLinkConfigEntry 5 }
875
876
877 -- 4.2. PPP LQR Group
878
879
880 --
881 -- The PPP LQR Group.
882 -- Implementation of this group is mandatory for all
883 -- PPP implementations that implement LQR.
884 --
885
886 pppLqrTable OBJECT-TYPE
887 SYNTAX SEQUENCE OF PppLqrEntry
888 ACCESS not-accessible
889
890
891
892 <span class="grey">Kastenholz [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
895
896
897 STATUS mandatory
898 DESCRIPTION
899 "Table containing the LQR parameters and
900 statistics for the local PPP entity."
901 ::= { pppLqr 1 }
902
903
904 pppLqrEntry OBJECT-TYPE
905 SYNTAX PppLqrEntry
906 ACCESS not-accessible
907 STATUS mandatory
908 DESCRIPTION
909 "LQR information for a particular PPP link. A
910 PPP link will have an entry in this table if
911 and only if LQR Quality Monitoring has been
912 successfully negotiated for said link."
913 INDEX { ifIndex }
914 ::= { pppLqrTable 1 }
915
916
917 PppLqrEntry ::= SEQUENCE {
918 pppLqrQuality
919 INTEGER,
920 pppLqrInGoodOctets
921 Counter,
922 pppLqrLocalPeriod
923 INTEGER,
924 pppLqrRemotePeriod
925 INTEGER,
926 pppLqrOutLQRs
927 Counter,
928 pppLqrInLQRs
929 Counter
930 }
931
932 pppLqrQuality OBJECT-TYPE
933 SYNTAX INTEGER {
934 good(1),
935 bad(2),
936 not-determined(3)
937 }
938 ACCESS read-only
939 STATUS mandatory
940 DESCRIPTION
941 "The current quality of the link as declared by
942 the local PPP entity's Link-Quality Management
943 modules. No effort is made to define good or
944 bad, nor the policy used to determine it. The
945
946
947
948 <span class="grey">Kastenholz [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
951
952
953 not-determined value indicates that the entity
954 does not actually evaluate the link's quality.
955 This value is used to disambiguate the
956 `determined to be good' case from the `no
957 determination made and presumed to be good'
958 case."
959 ::= { pppLqrEntry 1 }
960
961
962 pppLqrInGoodOctets OBJECT-TYPE
963 SYNTAX Counter
964 ACCESS read-only
965 STATUS mandatory
966 DESCRIPTION
967 "The LQR InGoodOctets counter for this link."
968 REFERENCE
969 "<a href="#section-2.2">Section 2.2</a>, Counters, of <a href="./rfc1333">RFC1333</a>."
970 ::= { pppLqrEntry 2 }
971
972
973 pppLqrLocalPeriod OBJECT-TYPE
974 SYNTAX INTEGER(1..2147483648)
975 ACCESS read-only
976 STATUS mandatory
977 DESCRIPTION
978 "The LQR reporting period, in hundredths of a
979 second that is in effect for the local PPP
980 entity."
981 REFERENCE
982 "<a href="#section-2.5">Section 2.5</a>, Configuration Option Format, of
983 <a href="./rfc1333">RFC1333</a>."
984 ::= { pppLqrEntry 3 }
985
986
987 pppLqrRemotePeriod OBJECT-TYPE
988 SYNTAX INTEGER(1..2147483648)
989 ACCESS read-only
990 STATUS mandatory
991 DESCRIPTION
992 "The LQR reporting period, in hundredths of a
993 second, that is in effect for the remote PPP
994 entity."
995 REFERENCE
996 "<a href="#section-2.5">Section 2.5</a>, Configuration Option Format, of
997 <a href="./rfc1333">RFC1333</a>."
998 ::= { pppLqrEntry 4 }
999
1000
1001
1002
1003
1004 <span class="grey">Kastenholz [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
1007
1008
1009 pppLqrOutLQRs OBJECT-TYPE
1010 SYNTAX Counter
1011 ACCESS read-only
1012 STATUS mandatory
1013 DESCRIPTION
1014 "The value of the OutLQRs counter on the local
1015 node for the link identified by ifIndex."
1016 REFERENCE
1017 "<a href="#section-2.2">Section 2.2</a>, Counters, of <a href="./rfc1333">RFC1333</a>."
1018 ::= { pppLqrEntry 5 }
1019
1020
1021 pppLqrInLQRs OBJECT-TYPE
1022 SYNTAX Counter
1023 ACCESS read-only
1024 STATUS mandatory
1025 DESCRIPTION
1026 "The value of the InLQRs counter on the local
1027 node for the link identified by ifIndex."
1028 REFERENCE
1029 "<a href="#section-2.2">Section 2.2</a>, Counters, of <a href="./rfc1333">RFC1333</a>."
1030 ::= { pppLqrEntry 6 }
1031
1032
1033 --
1034 -- The PPP LQR Configuration table.
1035 --
1036
1037 pppLqrConfigTable OBJECT-TYPE
1038 SYNTAX SEQUENCE OF PppLqrConfigEntry
1039 ACCESS not-accessible
1040 STATUS mandatory
1041 DESCRIPTION
1042 "Table containing the LQR Configuration
1043 parameters for the local PPP entity."
1044 ::= { pppLqr 2 }
1045
1046
1047 pppLqrConfigEntry OBJECT-TYPE
1048 SYNTAX PppLqrConfigEntry
1049 ACCESS not-accessible
1050 STATUS mandatory
1051 DESCRIPTION
1052 "LQR configuration information for a particular
1053 PPP link."
1054 INDEX { ifIndex }
1055 ::= { pppLqrConfigTable 1 }
1056
1057
1058
1059
1060 <span class="grey">Kastenholz [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
1063
1064
1065 PppLqrConfigEntry ::= SEQUENCE {
1066 pppLqrConfigPeriod
1067 INTEGER,
1068 pppLqrConfigStatus
1069 INTEGER
1070 }
1071
1072 pppLqrConfigPeriod OBJECT-TYPE
1073 SYNTAX INTEGER(0..2147483647)
1074 ACCESS read-write
1075 STATUS mandatory
1076 DESCRIPTION
1077 "The LQR Reporting Period that the local PPP
1078 entity will attempt to negotiate with the
1079 remote entity, in units of hundredths of a
1080 second. Changing this object will have effect
1081 when the link is next restarted."
1082 REFERENCE
1083 "<a href="#section-2.5">Section 2.5</a>, Configuration Option Format, of
1084 <a href="./rfc1333">RFC1333</a>."
1085 DEFVAL { 0 }
1086 ::= { pppLqrConfigEntry 1 }
1087
1088
1089 pppLqrConfigStatus OBJECT-TYPE
1090 SYNTAX INTEGER {disabled (1), enabled (2)}
1091 ACCESS read-write
1092 STATUS mandatory
1093 DESCRIPTION
1094 "If enabled(2) then the local node will attempt
1095 to perform LQR negotiation with the remote
1096 node. If disabled(1) then this negotiation is
1097 not performed. In any event, the local node
1098 will comply with any magic number negotiations
1099 attempted by the remote node, per the PPP
1100 specification. Changing this object will have
1101 effect when the link is next restarted.
1102 Setting this object to the value disabled(1)
1103 has the effect of invalidating the
1104 corresponding entry in the pppLqrConfigTable
1105 object. It is an implementation-specific matter
1106 as to whether the agent removes an invalidated
1107 entry from the table. Accordingly, management
1108 stations must be prepared to receive tabular
1109 information from agents that corresponds to
1110 entries not currently in use."
1111 REFERENCE
1112 "<a href="#section-7.6">Section 7.6</a>, Magic Number, of <a href="./rfc1331">RFC1331</a>."
1113
1114
1115
1116 <span class="grey">Kastenholz [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
1119
1120
1121 DEFVAL { enabled }
1122 ::= { pppLqrConfigEntry 2 }
1123
1124
1125 -- 4.3. PPP LQR Extensions Group
1126
1127
1128 --
1129 -- The PPP LQR Extensions Group.
1130 -- Implementation of this group is optional.
1131 --
1132 -- The intent of this group is to allow external
1133 -- implementation of the policy mechanisms that
1134 -- are used to declare a link to be "bad" or not.
1135 --
1136 -- It is not practical to examine the MIB objects
1137 -- which are used to generate LQR packets since
1138 -- LQR policies tend to require synchronization of
1139 -- the values of all data used to determine Link
1140 -- Quality; i.e. the values of the relevant counters
1141 -- must all be taken at the same instant in time.
1142 --
1143
1144 pppLqrExtnsTable OBJECT-TYPE
1145 SYNTAX SEQUENCE OF PppLqrExtnsEntry
1146 ACCESS not-accessible
1147 STATUS mandatory
1148 DESCRIPTION
1149 "Table containing additional LQR information
1150 for the local PPP entity."
1151 ::= { pppLqr 3 }
1152
1153
1154 pppLqrExtnsEntry OBJECT-TYPE
1155 SYNTAX PppLqrExtnsEntry
1156 ACCESS not-accessible
1157 STATUS mandatory
1158 DESCRIPTION
1159 "Extended LQR information for a particular PPP
1160 link. Assuming that this group has been
1161 implemented, a PPP link will have an entry in
1162 this table if and only if LQR Quality
1163 Monitoring has been successfully negotiated for
1164 said link."
1165 INDEX { ifIndex }
1166 ::= { pppLqrExtnsTable 1 }
1167
1168 PppLqrExtnsEntry ::= SEQUENCE {
1169
1170
1171
1172 <span class="grey">Kastenholz [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
1175
1176
1177 pppLqrExtnsLastReceivedLqrPacket
1178 OCTET STRING(SIZE(68))
1179 }
1180
1181 pppLqrExtnsLastReceivedLqrPacket OBJECT-TYPE
1182 SYNTAX OCTET STRING(SIZE(68))
1183 ACCESS read-only
1184 STATUS mandatory
1185 DESCRIPTION
1186 "This object contains the most recently
1187 received LQR packet. The format of the packet
1188 is as described in the LQM Protocol
1189 specificiation. All fields of the packet,
1190 including the `save' fields, are stored in this
1191 object.
1192
1193 The LQR packet is stored in network byte order.
1194 The LAP-B and PPP headers are not stored in
1195 this object; the first four octets of this
1196 variable contain the Magic-Number field, the
1197 second four octets contain the LastOutLQRs
1198 field and so on. The last four octets of this
1199 object contain the SaveInOctets field of the
1200 LQR packet."
1201 REFERENCE
1202 "<a href="#section-2.6">Section 2.6</a>, Packet Format, of <a href="./rfc1333">RFC1333</a>"
1203 ::= { pppLqrExtnsEntry 1 }
1204
1205
1206 -- 4.4. PPP Tests
1207
1208 -- The extensions to the interface table in <a href="./rfc1229">RFC1229</a> define a
1209 -- table through which the network manager can instruct the
1210 -- managed object to perform various tests of the interface. This
1211 -- is the ifExtnsTestTable.
1212
1213 -- The PPP MIB defines two such tests.
1214
1215 -- 4.4.1. PPP Echo Test
1216
1217 -- The PPP Echo Test is defined as
1218
1219 pppEchoTest OBJECT IDENTIFIER ::= { pppTests 1 }
1220
1221 -- Invoking this test causes a PPP Echo Packet to be sent on the
1222 -- line. ifExtnsTestResult returns success(2) if the echo
1223 -- response came back properly. It returns failed(7) if the
1224 -- response did not properly return. The definition of "proper"
1225
1226
1227
1228 <span class="grey">Kastenholz [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
1231
1232
1233 -- in this context is left to the discretion of the implementor.
1234
1235 -- 4.4.2. PPP Discard Test
1236
1237 -- The PPP Discard Test is defined as
1238
1239 pppDiscardTest OBJECT IDENTIFIER ::= { pppTests 2 }
1240
1241 -- Invoking this test causes a PPP Discard Packet to be sent on
1242 -- the line. ifExtnsTestResult returns success(2) if the discard
1243 -- packet was successfully transmitted and failed(7) if an error
1244 -- was detected on transmission. The definition of "transmission
1245 -- error" in this context is left to the discretion of the
1246 -- implementor.
1247
1248 END
1249
1250 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
1251
1252 This document was produced by the PPP working group. In addition to
1253 the working group, the author wishes to thank the following
1254 individuals for their comments and contributions:
1255
1256 Bill Simpson -- Daydreamer
1257 Glenn McGregor -- Merit
1258 Jesse Walker -- DEC
1259 Chris Gunner -- DEC
1260
1261 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
1262
1263 The PPP MIB affords the network operator the ability to configure and
1264 control the PPP links of a particular system. This represents a
1265 security risk.
1266
1267 These risks are addressed in the following manners:
1268
1269 (1) All variables which represent a significant security risk
1270 are placed in separate, optional, MIB Groups. As the MIB
1271 Group is the quantum of implementation within a MIB, the
1272 implementor of the MIB may elect not to implement these
1273 groups.
1274
1275 (2) The implementor may choose to implement the variables
1276 which present a security risk so that they may not be
1277 written, i.e., the variables are READ-ONLY. This method
1278 still presents a security risk, and is not recommended,
1279 in that the variables, specifically the PPP
1280 Authentication Protocols' variables, may be easily read.
1281
1282
1283
1284 <span class="grey">Kastenholz [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
1287
1288
1289 (3) Using SNMPv2, the operator can place the variables into
1290 MIB views which are protected in that the parties which
1291 have access to those MIB views use authentication and
1292 privacy protocols, or the operator may elect to make
1293 these views not accessible to any party. In order to
1294 facilitate this placement, all security-related variables
1295 are placed in separate MIB Tables. This eases the
1296 identification of the necessary MIB View Subtree.
1297
1298 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
1299
1300 [<a id="ref-1">1</a>] Rose M., and K. McCloghrie, "Structure and Identification of
1301 Management Information for TCP/IP-based internets", STD 16, <a href="./rfc1155">RFC</a>
1302 <a href="./rfc1155">1155</a>, Performance Systems International, Hughes LAN Systems, May
1303 1990.
1304
1305 [<a id="ref-2">2</a>] McCloghrie K., and M. Rose, Editors, "Management Information Base
1306 for Network Management of TCP/IP-based internets", STD 17, <a href="./rfc1213">RFC</a>
1307 <a href="./rfc1213">1213</a>, Performance Systems International, March 1991.
1308
1309 [<a id="ref-3">3</a>] Information processing systems - Open Systems Interconnection -
1310 Specification of Abstract Syntax Notation One (ASN.1),
1311 International Organization for Standardization, International
1312 Standard 8824, December 1987.
1313
1314 [<a id="ref-4">4</a>] Information processing systems - Open Systems Interconnection -
1315 Specification of Basic Encoding Rules for Abstract Notation One
1316 (ASN.1), International Organization for Standardization,
1317 International Standard 8825, December 1987.
1318
1319 [<a id="ref-5">5</a>] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
1320 STD 16, <a href="./rfc1212">RFC 1212</a>, Performance Systems International, Hughes LAN
1321 Systems, March 1991.
1322
1323 [<a id="ref-6">6</a>] Rose, M., Editor, "A Convention for Defining Traps for use with
1324 the SNMP", <a href="./rfc1215">RFC 1215</a>, Performance Systems International, March
1325 1991.
1326
1327 [<a id="ref-7">7</a>] McCloghrie, K., "Extensions to the Generic-Interface MIB", <a href="./rfc1229">RFC</a>
1328 <a href="./rfc1229">1229</a>, Hughes LAN Systems, Inc., May 1991.
1329
1330 [<a id="ref-8">8</a>] Simpson, W., "The Point-to-Point Protocol for the Transmission of
1331 Multi-protocol Datagrams over Point-to-Point Links, <a href="./rfc1331">RFC 1331</a>,
1332 Daydreamer, May 1992.
1333
1334 [<a id="ref-9">9</a>] McGregor, G., "The PPP Internet Protocol Control Protocol", <a href="./rfc1332">RFC</a>
1335 <a href="./rfc1332">1332</a>, Merit, May 1992.
1336
1337
1338
1339
1340 <span class="grey">Kastenholz [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc1471">RFC 1471</a> PPP/LCP MIB June 1993</span>
1343
1344
1345 [<a id="ref-10">10</a>] Baker, F., "Point-to-Point Protocol Extensions for Bridging", <a href="./rfc1220">RFC</a>
1346 <a href="./rfc1220">1220</a>, ACC, April 1991.
1347
1348 [<a id="ref-11">11</a>] Lloyd, B., and W. Simpson, "PPP Authentication Protocols", <a href="./rfc1334">RFC</a>
1349 <a href="./rfc1334">1334</a>, L&amp;A, Daydreamer, October 1992.
1350
1351 [<a id="ref-12">12</a>] Simpson, W., "PPP Link Quality Monitoring", <a href="./rfc1333">RFC 1333</a>, Daydreamer,
1352 May 1992.
1353
1354 [<a id="ref-13">13</a>] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
1355 Network Management Protocol", STD 15, <a href="./rfc1157">RFC 1157</a>, SNMP Research,
1356 Performance Systems International, Performance Systems
1357 International, MIT Laboratory for Computer Science, May 1990.
1358
1359 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Author's Address</span>
1360
1361 Frank Kastenholz
1362 FTP Software, Inc.
1363 2 High Street
1364 North Andover, Mass 01845 USA
1365
1366 Phone: (508) 685-4000
1367 EMail: [email protected]
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396 Kastenholz [Page 25]
1397 </pre>