| 1 |
<pre>Network Working Group F. Kastenholz |
| 2 |
Request for Comments: 1473 FTP Software, Inc. |
| 3 |
June 1993 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">The Definitions of Managed Objects for</span> |
| 7 |
<span class="h1">the IP Network 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 IP |
| 23 |
Network Control Protocol on subnetwork interfaces using the family of |
| 24 |
Point-to-Point Protocols [8, 9, 10, 11, & 12]. |
| 25 |
|
| 26 |
Table of Contents |
| 27 |
|
| 28 |
<a href="#section-1">1</a>. The Network Management Framework ...................... <a href="#page-1">1</a> |
| 29 |
<a href="#section-2">2</a>. Objects ............................................... <a href="#page-2">2</a> |
| 30 |
<a href="#section-2.1">2.1</a> Format of Definitions ................................ <a href="#page-2">2</a> |
| 31 |
<a href="#section-3">3</a>. Overview .............................................. <a href="#page-2">2</a> |
| 32 |
<a href="#section-3.1">3.1</a> Object Selection Criteria ............................ <a href="#page-2">2</a> |
| 33 |
<a href="#section-3.2">3.2</a> Structure of the PPP ................................. <a href="#page-2">2</a> |
| 34 |
<a href="#section-3.3">3.3</a> MIB Groups ........................................... <a href="#page-3">3</a> |
| 35 |
<a href="#section-4">4</a>. Definitions ........................................... <a href="#page-4">4</a> |
| 36 |
<a href="#section-5">5</a>. Acknowledgements ...................................... <a href="#page-8">8</a> |
| 37 |
<a href="#section-6">6</a>. Security Considerations ............................... <a href="#page-8">8</a> |
| 38 |
<a href="#section-7">7</a>. References ............................................ <a href="#page-8">8</a> |
| 39 |
<a href="#section-8">8</a>. Author's Address ...................................... <a href="#page-9">9</a> |
| 40 |
|
| 41 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. The Network Management Framework</span> |
| 42 |
|
| 43 |
The Internet-standard Network Management Framework consists of three |
| 44 |
components. They are: |
| 45 |
|
| 46 |
STD 16/RFC 1155 which defines the SMI, the mechanisms used for |
| 47 |
describing and naming objects for the purpose of management. STD |
| 48 |
16/RFC 1212 defines a more concise description mechanism, which is |
| 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="./rfc1473">RFC 1473</a> PPP/IP MIB June 1993</span> |
| 55 |
|
| 56 |
|
| 57 |
wholly consistent with the SMI. |
| 58 |
|
| 59 |
STD 17/RFC 1213 which defines MIB-II, the core set of managed |
| 60 |
objects for the Internet suite of protocols. |
| 61 |
|
| 62 |
STD 15/RFC 1157 which defines the SNMP, the protocol used for |
| 63 |
network access to managed objects. |
| 64 |
|
| 65 |
The Framework permits new objects to be defined for the purpose of |
| 66 |
experimentation and evaluation. |
| 67 |
|
| 68 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Objects</span> |
| 69 |
|
| 70 |
Managed objects are accessed via a virtual information store, termed |
| 71 |
the Management Information Base or MIB. Objects in the MIB are |
| 72 |
defined using the subset of Abstract Syntax Notation One (ASN.1) [<a href="#ref-3" title=" International Organization for Standardization">3</a>] |
| 73 |
defined in the SMI. In particular, each object type is named by an |
| 74 |
OBJECT IDENTIFIER, an administratively assigned name. The object |
| 75 |
type together with an object instance serves to uniquely identify a |
| 76 |
specific instantiation of the object. For human convenience, we |
| 77 |
often use a textual string, termed the descriptor, to refer to the |
| 78 |
object type. |
| 79 |
|
| 80 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Format of Definitions</span> |
| 81 |
|
| 82 |
<a href="#section-4">Section 4</a> contains the specification of all object types contained in |
| 83 |
this MIB module. The object types are defined using the conventions |
| 84 |
defined in the SMI, as amended by the extensions specified in [<a href="#ref-5" title=""Concise MIB Definitions"">5</a>,<a href="#ref-6" title=""A Convention for Defining Traps for use with the SNMP"">6</a>]. |
| 85 |
|
| 86 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Overview</span> |
| 87 |
|
| 88 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Object Selection Criteria</span> |
| 89 |
|
| 90 |
To be consistent with IAB directives and good engineering practice, |
| 91 |
an explicit attempt was made to keep this MIB as simple as possible. |
| 92 |
This was accomplished by applying the following criteria to objects |
| 93 |
proposed for inclusion: |
| 94 |
|
| 95 |
(1) Require objects be essential for either fault or |
| 96 |
configuration management. In particular, objects for |
| 97 |
which the sole purpose was to debug implementations were |
| 98 |
explicitly excluded from the MIB. |
| 99 |
|
| 100 |
(2) Consider evidence of current use and/or utility. |
| 101 |
|
| 102 |
(3) Limit the total number of objects. |
| 103 |
|
| 104 |
(4) Exclude objects which are simply derivable from others in |
| 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="./rfc1473">RFC 1473</a> PPP/IP MIB June 1993</span> |
| 111 |
|
| 112 |
|
| 113 |
this or other MIBs. |
| 114 |
|
| 115 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Structure of the PPP</span> |
| 116 |
|
| 117 |
This section describes the basic model of PPP used in developing the |
| 118 |
PPP MIB. This information should be useful to the implementor in |
| 119 |
understanding some of the basic design decisions of the MIB. |
| 120 |
|
| 121 |
The PPP is not one single protocol but a large family of protocols. |
| 122 |
Each of these is, in itself, a fairly complex protocol. The PPP |
| 123 |
protocols may be divided into three rough categories: |
| 124 |
|
| 125 |
Control Protocols |
| 126 |
The Control Protocols are used to control the operation of the |
| 127 |
PPP. The Control Protocols include the Link Control Protocol |
| 128 |
(LCP), the Password Authentication Protocol (PAP), the Link |
| 129 |
Quality Report (LQR), and the Challenge Handshake Authentication |
| 130 |
Protocol (CHAP). |
| 131 |
|
| 132 |
Network Protocols |
| 133 |
The Network Protocols are used to move the network traffic over |
| 134 |
the PPP interface. A Network Protocol encapsulates the datagrams |
| 135 |
of a specific higher-layer protocol that is using the PPP as a |
| 136 |
data link. Note that within the context of PPP, the term "Network |
| 137 |
Protocol" does not imply an OSI Layer-3 protocol; for instance, |
| 138 |
there is a Bridging network protocol. |
| 139 |
|
| 140 |
Network Control Protocols (NCPs) |
| 141 |
The NCPs are used to control the operation of the Network |
| 142 |
Protocols. Generally, each Network Protocol has its own Network |
| 143 |
Control Protocol; thus, the IP Network Protocol has its IP Control |
| 144 |
Protocol, the Bridging Network Protocol has its Bridging Network |
| 145 |
Control Protocol and so on. |
| 146 |
|
| 147 |
This document specifies the objects used in managing one of these |
| 148 |
protocols, namely the IP Network Control Protocol. |
| 149 |
|
| 150 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. MIB Groups</span> |
| 151 |
|
| 152 |
Objects in this MIB are arranged into several MIB groups. Each group |
| 153 |
is organized as a set of related objects. |
| 154 |
|
| 155 |
These groups are the basic unit of conformance: if the semantics of a |
| 156 |
group are applicable to an implementation then all objects in the |
| 157 |
group must be implemented. |
| 158 |
|
| 159 |
The PPP MIB is organized into several MIB Groups, including, but not |
| 160 |
limited to, the following groups: |
| 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="./rfc1473">RFC 1473</a> PPP/IP MIB June 1993</span> |
| 167 |
|
| 168 |
|
| 169 |
o The PPP Link Group |
| 170 |
o The PPP LQR Group |
| 171 |
o The PPP LQR Extensions Group |
| 172 |
o The PPP IP Group |
| 173 |
o The PPP Bridge Group |
| 174 |
o The PPP Security Group |
| 175 |
|
| 176 |
This document specifies the following group: |
| 177 |
|
| 178 |
The PPP IP Group |
| 179 |
The PPP IP Group contains configuration, status, and control |
| 180 |
variables that apply to the operation of IP over PPP. |
| 181 |
|
| 182 |
Implementation of this group is mandatory for all implementations |
| 183 |
of PPP that support IP over PPP. |
| 184 |
|
| 185 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Definitions</span> |
| 186 |
|
| 187 |
PPP-IP-NCP-MIB DEFINITIONS ::= BEGIN |
| 188 |
|
| 189 |
IMPORTS |
| 190 |
Counter |
| 191 |
FROM <a href="./rfc1155">RFC1155</a>-SMI |
| 192 |
ifIndex |
| 193 |
FROM <a href="./rfc1213">RFC1213</a>-MIB |
| 194 |
OBJECT-TYPE |
| 195 |
FROM <a href="./rfc1212">RFC-1212</a> |
| 196 |
ppp |
| 197 |
FROM PPP-LCP-MIB; |
| 198 |
|
| 199 |
-- The PPP IP Group. |
| 200 |
-- Implementation of this group is mandatory for all |
| 201 |
-- PPP implementations that support operating IP over PPP. |
| 202 |
|
| 203 |
pppIp OBJECT IDENTIFIER ::= { ppp 3 } |
| 204 |
|
| 205 |
|
| 206 |
pppIpTable OBJECT-TYPE |
| 207 |
SYNTAX SEQUENCE OF PppIpEntry |
| 208 |
ACCESS not-accessible |
| 209 |
STATUS mandatory |
| 210 |
DESCRIPTION |
| 211 |
"Table containing the IP parameters and |
| 212 |
statistics for the local PPP entity." |
| 213 |
::= { pppIp 1 } |
| 214 |
|
| 215 |
|
| 216 |
pppIpEntry OBJECT-TYPE |
| 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="./rfc1473">RFC 1473</a> PPP/IP MIB June 1993</span> |
| 223 |
|
| 224 |
|
| 225 |
SYNTAX PppIpEntry |
| 226 |
ACCESS not-accessible |
| 227 |
STATUS mandatory |
| 228 |
DESCRIPTION |
| 229 |
"IPCP status information for a particular PPP |
| 230 |
link." |
| 231 |
INDEX { ifIndex } |
| 232 |
::= { pppIpTable 1 } |
| 233 |
|
| 234 |
|
| 235 |
PppIpEntry ::= SEQUENCE { |
| 236 |
pppIpOperStatus |
| 237 |
INTEGER, |
| 238 |
pppIpLocalToRemoteCompressionProtocol |
| 239 |
INTEGER, |
| 240 |
pppIpRemoteToLocalCompressionProtocol |
| 241 |
INTEGER, |
| 242 |
pppIpRemoteMaxSlotId |
| 243 |
INTEGER, |
| 244 |
pppIpLocalMaxSlotId |
| 245 |
INTEGER |
| 246 |
} |
| 247 |
|
| 248 |
-- The following object reflect the values of the option |
| 249 |
-- parameters used in the PPP IP Control Protocol |
| 250 |
-- pppIpLocalToRemoteCompressionProtocol |
| 251 |
-- pppIpRemoteToLocalCompressionProtocol |
| 252 |
-- pppIpRemoteMaxSlotId |
| 253 |
-- pppIpLocalMaxSlotId |
| 254 |
-- These values are not available until after the PPP Option |
| 255 |
-- negotiation has completed, which is indicated by the link |
| 256 |
-- reaching the open state (i.e., pppIpOperStatus is set to |
| 257 |
-- opened). |
| 258 |
-- |
| 259 |
-- Therefore, when pppIpOperStatus is not opened |
| 260 |
-- the contents of these objects is undefined. The value |
| 261 |
-- returned when accessing the objects is an implementation |
| 262 |
-- dependent issue. |
| 263 |
|
| 264 |
|
| 265 |
pppIpOperStatus OBJECT-TYPE |
| 266 |
SYNTAX INTEGER {opened(1), not-opened(2)} |
| 267 |
ACCESS read-only |
| 268 |
STATUS mandatory |
| 269 |
DESCRIPTION |
| 270 |
"The operational status of the IP network |
| 271 |
protocol. If the value of this object is up |
| 272 |
then the finite state machine for the IP |
| 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="./rfc1473">RFC 1473</a> PPP/IP MIB June 1993</span> |
| 279 |
|
| 280 |
|
| 281 |
network protocol has reached the Opened state." |
| 282 |
::= { pppIpEntry 1 } |
| 283 |
|
| 284 |
|
| 285 |
pppIpLocalToRemoteCompressionProtocol OBJECT-TYPE |
| 286 |
SYNTAX INTEGER { |
| 287 |
none(1), |
| 288 |
vj-tcp(2) |
| 289 |
} |
| 290 |
ACCESS read-only |
| 291 |
STATUS mandatory |
| 292 |
DESCRIPTION |
| 293 |
"The IP compression protocol that the local |
| 294 |
PPP-IP entity uses when sending packets to the |
| 295 |
remote PPP-IP entity. The value of this object |
| 296 |
is meaningful only when the link has reached |
| 297 |
the open state (pppIpOperStatus is opened)." |
| 298 |
::= { pppIpEntry 2 } |
| 299 |
|
| 300 |
|
| 301 |
pppIpRemoteToLocalCompressionProtocol OBJECT-TYPE |
| 302 |
SYNTAX INTEGER { |
| 303 |
none(1), |
| 304 |
vj-tcp(2) |
| 305 |
} |
| 306 |
ACCESS read-only |
| 307 |
STATUS mandatory |
| 308 |
DESCRIPTION |
| 309 |
"The IP compression protocol that the remote |
| 310 |
PPP-IP entity uses when sending packets to the |
| 311 |
local PPP-IP entity. The value of this object |
| 312 |
is meaningful only when the link has reached |
| 313 |
the open state (pppIpOperStatus is opened)." |
| 314 |
::= { pppIpEntry 3 } |
| 315 |
|
| 316 |
|
| 317 |
pppIpRemoteMaxSlotId OBJECT-TYPE |
| 318 |
SYNTAX INTEGER(0..255) |
| 319 |
ACCESS read-only |
| 320 |
STATUS mandatory |
| 321 |
DESCRIPTION |
| 322 |
"The Max-Slot-Id parameter that the remote node |
| 323 |
has advertised and that is in use on the link. |
| 324 |
If vj-tcp header compression is not in use on |
| 325 |
the link then the value of this object shall be |
| 326 |
0. The value of this object is meaningful only |
| 327 |
when the link has reached the open state |
| 328 |
(pppIpOperStatus is opened)." |
| 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="./rfc1473">RFC 1473</a> PPP/IP MIB June 1993</span> |
| 335 |
|
| 336 |
|
| 337 |
::= { pppIpEntry 4 } |
| 338 |
|
| 339 |
|
| 340 |
pppIpLocalMaxSlotId OBJECT-TYPE |
| 341 |
SYNTAX INTEGER(0..255) |
| 342 |
ACCESS read-only |
| 343 |
STATUS mandatory |
| 344 |
DESCRIPTION |
| 345 |
"The Max-Slot-Id parameter that the local node |
| 346 |
has advertised and that is in use on the link. |
| 347 |
If vj-tcp header compression is not in use on |
| 348 |
the link then the value of this object shall be |
| 349 |
0. The value of this object is meaningful only |
| 350 |
when the link has reached the open state |
| 351 |
(pppIpOperStatus is opened)." |
| 352 |
::= { pppIpEntry 5 } |
| 353 |
|
| 354 |
|
| 355 |
-- |
| 356 |
-- The PPP IP Configuration table. |
| 357 |
-- This is a separate table in order to facilitate |
| 358 |
-- placing these variables in a separate MIB view. |
| 359 |
-- |
| 360 |
|
| 361 |
pppIpConfigTable OBJECT-TYPE |
| 362 |
SYNTAX SEQUENCE OF PppIpConfigEntry |
| 363 |
ACCESS not-accessible |
| 364 |
STATUS mandatory |
| 365 |
DESCRIPTION |
| 366 |
"Table containing configuration variables for |
| 367 |
the IPCP for the local PPP entity." |
| 368 |
::= { pppIp 2 } |
| 369 |
|
| 370 |
|
| 371 |
pppIpConfigEntry OBJECT-TYPE |
| 372 |
SYNTAX PppIpConfigEntry |
| 373 |
ACCESS not-accessible |
| 374 |
STATUS mandatory |
| 375 |
DESCRIPTION |
| 376 |
"IPCP information for a particular PPP link." |
| 377 |
INDEX { ifIndex } |
| 378 |
::= { pppIpConfigTable 1 } |
| 379 |
|
| 380 |
|
| 381 |
PppIpConfigEntry ::= SEQUENCE { |
| 382 |
pppIpConfigAdminStatus |
| 383 |
INTEGER, |
| 384 |
pppIpConfigCompression |
| 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="./rfc1473">RFC 1473</a> PPP/IP MIB June 1993</span> |
| 391 |
|
| 392 |
|
| 393 |
INTEGER |
| 394 |
} |
| 395 |
|
| 396 |
pppIpConfigAdminStatus OBJECT-TYPE |
| 397 |
SYNTAX INTEGER {open(1), close(2)} |
| 398 |
ACCESS read-write |
| 399 |
STATUS mandatory |
| 400 |
DESCRIPTION |
| 401 |
"The immediate desired status of the IP network |
| 402 |
protocol. Setting this object to open will |
| 403 |
inject an administrative open event into the IP |
| 404 |
network protocol's finite state machine. |
| 405 |
Setting this object to close will inject an |
| 406 |
administrative close event into the IP network |
| 407 |
protocol's finite state machine." |
| 408 |
::= { pppIpConfigEntry 1 } |
| 409 |
|
| 410 |
|
| 411 |
pppIpConfigCompression OBJECT-TYPE |
| 412 |
SYNTAX INTEGER { |
| 413 |
none(1), |
| 414 |
vj-tcp(2) |
| 415 |
} |
| 416 |
ACCESS read-write |
| 417 |
STATUS mandatory |
| 418 |
DESCRIPTION |
| 419 |
"If none(1) then the local node will not |
| 420 |
attempt to negotiate any IP Compression option. |
| 421 |
Otherwise, the local node will attempt to |
| 422 |
negotiate compression mode indicated by the |
| 423 |
enumerated value. Changing this object will |
| 424 |
have effect when the link is next restarted." |
| 425 |
REFERENCE |
| 426 |
"<a href="#section-4.0">Section 4.0</a>, Van Jacobson TCP/IP Header |
| 427 |
Compression of <a href="./rfc1332">RFC1332</a>." |
| 428 |
DEFVAL { none } |
| 429 |
::= { pppIpConfigEntry 2 } |
| 430 |
|
| 431 |
|
| 432 |
END |
| 433 |
|
| 434 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span> |
| 435 |
|
| 436 |
This document was produced by the PPP working group. In addition to |
| 437 |
the working group, the author wishes to thank the following |
| 438 |
individuals for their comments and contributions: |
| 439 |
|
| 440 |
Bill Simpson -- Daydreamer |
| 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="./rfc1473">RFC 1473</a> PPP/IP MIB June 1993</span> |
| 447 |
|
| 448 |
|
| 449 |
Glenn McGregor -- Merit |
| 450 |
Jesse Walker -- DEC |
| 451 |
Chris Gunner -- DEC |
| 452 |
|
| 453 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 454 |
|
| 455 |
The PPP MIB affords the network operator the ability to configure and |
| 456 |
control the PPP links of a particular system, including the PPP |
| 457 |
authentication protocols. This represents a security risk. |
| 458 |
|
| 459 |
These risks are addressed in the following manners: |
| 460 |
|
| 461 |
(1) All variables which represent a significant security risk |
| 462 |
are placed in separate, optional, MIB Groups. As the MIB |
| 463 |
Group is the quantum of implementation within a MIB, the |
| 464 |
implementor of the MIB may elect not to implement these |
| 465 |
groups. |
| 466 |
|
| 467 |
(2) The implementor may choose to implement the variables |
| 468 |
which present a security risk so that they may not be |
| 469 |
written, i.e., the variables are READ-ONLY. This method |
| 470 |
still presents a security risk, and is not recommended, |
| 471 |
in that the variables, specifically the PPP |
| 472 |
Authentication Protocols' variables, may be easily read. |
| 473 |
|
| 474 |
(3) Using SNMPv2, the operator can place the variables into |
| 475 |
MIB views which are protected in that the parties which |
| 476 |
have access to those MIB views use authentication and |
| 477 |
privacy protocols, or the operator may elect to make |
| 478 |
these views not accessible to any party. In order to |
| 479 |
facilitate this placement, all security-related variables |
| 480 |
are placed in separate MIB Tables. This eases the |
| 481 |
identification of the necessary MIB View Subtree. |
| 482 |
|
| 483 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span> |
| 484 |
|
| 485 |
[<a id="ref-1">1</a>] Rose M., and K. McCloghrie, "Structure and Identification of |
| 486 |
Management Information for TCP/IP-based internets", STD 16, <a href="./rfc1155">RFC</a> |
| 487 |
<a href="./rfc1155">1155</a>, Performance Systems International, Hughes LAN Systems, May |
| 488 |
1990. |
| 489 |
|
| 490 |
[<a id="ref-2">2</a>] McCloghrie K., and M. Rose, Editors, "Management Information Base |
| 491 |
for Network Management of TCP/IP-based internets", STD 17, <a href="./rfc1213">RFC</a> |
| 492 |
<a href="./rfc1213">1213</a>, Performance Systems International, March 1991. |
| 493 |
|
| 494 |
[<a id="ref-3">3</a>] Information processing systems - Open Systems Interconnection - |
| 495 |
Specification of Abstract Syntax Notation One (ASN.1), |
| 496 |
International Organization for Standardization, International |
| 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="./rfc1473">RFC 1473</a> PPP/IP MIB June 1993</span> |
| 503 |
|
| 504 |
|
| 505 |
Standard 8824, December 1987. |
| 506 |
|
| 507 |
[<a id="ref-4">4</a>] Information processing systems - Open Systems Interconnection - |
| 508 |
Specification of Basic Encoding Rules for Abstract Notation One |
| 509 |
(ASN.1), International Organization for Standardization, |
| 510 |
International Standard 8825, December 1987. |
| 511 |
|
| 512 |
[<a id="ref-5">5</a>] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions", |
| 513 |
STD 16, <a href="./rfc1212">RFC 1212</a>, Performance Systems International, Hughes LAN |
| 514 |
Systems, March 1991. |
| 515 |
|
| 516 |
[<a id="ref-6">6</a>] Rose, M., Editor, "A Convention for Defining Traps for use with |
| 517 |
the SNMP", <a href="./rfc1215">RFC 1215</a>, Performance Systems International, March |
| 518 |
1991. |
| 519 |
|
| 520 |
[<a id="ref-7">7</a>] McCloghrie, K., "Extensions to the Generic-Interface MIB", <a href="./rfc1229">RFC</a> |
| 521 |
<a href="./rfc1229">1229</a>, Hughes LAN Systems, Inc., May 1991. |
| 522 |
|
| 523 |
[<a id="ref-8">8</a>] Simpson, W., "The Point-to-Point Protocol for the Transmission of |
| 524 |
Multi-protocol Datagrams over Point-to-Point Links, <a href="./rfc1331">RFC 1331</a>, |
| 525 |
Daydreamer, May 1992. |
| 526 |
|
| 527 |
[<a id="ref-9">9</a>] McGregor, G., "The PPP Internet Protocol Control Protocol", <a href="./rfc1332">RFC</a> |
| 528 |
<a href="./rfc1332">1332</a>, Merit, May 1992. |
| 529 |
|
| 530 |
[<a id="ref-10">10</a>] Baker, F., "Point-to-Point Protocol Extensions for Bridging", <a href="./rfc1220">RFC</a> |
| 531 |
<a href="./rfc1220">1220</a>, ACC, April 1991. |
| 532 |
|
| 533 |
[<a id="ref-11">11</a>] Lloyd, B., and W. Simpson, "PPP Authentication Protocols", <a href="./rfc1334">RFC</a> |
| 534 |
<a href="./rfc1334">1334</a>, L&A, Daydreamer, October 1992. |
| 535 |
|
| 536 |
[<a id="ref-12">12</a>] Simpson, W., "PPP Link Quality Monitoring", <a href="./rfc1333">RFC 1333</a>, Daydreamer, |
| 537 |
May 1992. |
| 538 |
|
| 539 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Author's Address</span> |
| 540 |
|
| 541 |
Frank Kastenholz |
| 542 |
FTP Software, Inc. |
| 543 |
2 High Street |
| 544 |
North Andover, Mass 01845 USA |
| 545 |
|
| 546 |
Phone: (508) 685-4000 |
| 547 |
EMail: [email protected] |
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
Kastenholz [Page 10] |
| 557 |
</pre> |