datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol
RFC 1471

Document type: RFC - Proposed Standard (June 1993)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 1471 (Proposed Standard)
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                      F. Kastenholz
Request for Comments: 1471                            FTP Software, Inc.
                                                               June 1993

                 The Definitions of Managed Objects for
                      the Link Control Protocol of
                      the Point-to-Point Protocol

Status of this Memo

   This RFC specifies an IAB standards track protocol for the Internet
   community, and requests discussion and suggestions for improvements.
   Please refer to the current edition of the "IAB Official Protocol
   Standards" for the standardization state and status of this protocol.
   Distribution of this memo is unlimited.

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP-based internets.
   In particular, it describes managed objects used for managing the
   Link Control Protocol and Link Quality Monitoring on subnetwork
   interfaces that use the family of Point-to-Point Protocols [8, 9, 10,
   11, & 12].

Table of Contents

   1. The Network Management Framework ......................    2
   2. Objects ...............................................    2
   2.1 Format of Definitions ................................    2
   3. Overview ..............................................    2
   3.1 Object Selection Criteria ............................    2
   3.2 Structure of the PPP .................................    3
   3.3 MIB Groups ...........................................    4
   3.4 Relationship to Interface and Interface Extensions
       Groups ...............................................    5
   4. Definitions ...........................................    6
   4.1 PPP Link Group .......................................    7
   4.2 PPP LQR Group ........................................   16
   4.3 PPP LQR Extensions Group .............................   21
   4.4 PPP Tests ............................................   22
   4.4.1 PPP Echo Test ......................................   22
   4.4.2 PPP Discard Test ...................................   23
   5. Acknowledgements ......................................   23
   6. Security Considerations ...............................   23
   7. References ............................................   24
   8. Author's Address ......................................   25

Kastenholz                                                      [Page 1]
RFC 1471                      PPP/LCP MIB                      June 1993

1.  The Network Management Framework

   The Internet-standard Network Management Framework consists of three
   components.  They are:

      STD 16/RFC 1155 which defines the SMI, the mechanisms used for
      describing and naming objects for the purpose of management.  STD
      16/RFC 1212 defines a more concise description mechanism, which is
      wholly consistent with the SMI.

      STD 17/RFC 1213 which defines MIB-II, the core set of managed
      objects for the Internet suite of protocols.

      STD 15/RFC 1157 which defines the SNMP, the protocol used for
      network access to managed objects.

   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.

2.  Objects

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1) [3]
   defined in the SMI.  In particular, each object type is named by an
   OBJECT IDENTIFIER, an administratively assigned name.  The object
   type together with an object instance serves to uniquely identify a
   specific instantiation of the object.  For human convenience, we
   often use a textual string, termed the descriptor, to refer to the
   object type.

2.1.  Format of Definitions

   Section 4 contains the specification of all object types contained in
   this MIB module.  The object types are defined using the conventions
   defined in the SMI, as amended by the extensions specified in [5,6].

3.  Overview

3.1.  Object Selection Criteria

   To be consistent with IAB directives and good engineering practice,
   an explicit attempt was made to keep this MIB as simple as possible.
   This was accomplished by applying the following criteria to objects
   proposed for inclusion:

      (1)  Require objects be essential for either fault or
           configuration management.  In particular, objects for

Kastenholz                                                      [Page 2]
RFC 1471                      PPP/LCP MIB                      June 1993

[include full document text]