Definitions of Managed Objects for the ADSL Lines
RFC 2662

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 09

Network Working Group                                        G. Bathrick
Request for Comments: 2662                      AG Communication Systems
Category: Standards Track                                          F. Ly
                                                Copper Mountain Networks
                                                             August 1999

           Definitions of Managed Objects for the ADSL Lines

Status of this Memo

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

Copyright Notice

   Copyright (C) The Internet Society (1999).  All Rights Reserved.

Table of Contents

    1.  Abstract  ..............................................   1
    2.  The SNMP Network Management Framework  .................   2
    3.  Object Definitions .....................................   3
    4.  Relationship of the ADSL LINE MIB with standard MIBs ...   3
    5.  Conventions used in the MIB ............................   7
    6.  Conformance and Compliance .............................  17
    7.  Definitions ............................................  17
    8.  Acknowledgments ........................................ 110
    9.  References ............................................. 111
   10.  Security Considerations ................................ 113
   11.  Intellectual Property Notice ........................... 114
   12.  Authors' Addresses ..................................... 114
   13.  Full Copyright Statement ............................... 115

1.  Abstract

   This document defines a standard SNMP MIB for ADSL lines based on the
   ADSL Forum standard data model [9].  The ADSL standard describes
   ATU-C and ATU-R as two sides of the ADSL line.  This MIB covers both
   ATU-C and ATU-R agent's perspectives.  Each instance defined in the

   MIB represents a single ADSL line.

Bathrick & Ly               Standards Track                     [Page 1]
RFC 2662                     ADSL Line MIB                   August 1999

   It should be noted that the ADSL Forum Network Management Working
   Group provided input towards the content of this document.  See the
   Acknowledgement Section for a list of individuals who made this
   document possible.

2.  The SNMP Network Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o  An overall architecture, described in RFC 2571 [13].

   o  Mechanisms for describing and naming objects and events for the
      purpose of management.  The first version of this Structure of
      Management Information (SMI) is called SMIv1 and described in STD
      16, RFC 1155 [14], STD 16, RFC 1212 [15] and RFC 1215 [16].  The
      second version, called SMIv2, is described in STD 58, RFC 2578
      [1], STD 58, RFC 2579 [2] and STD 58, RFC 2580 [17].

   o  Message protocols for transferring management information.  The
      first version of the SNMP message protocol is called SNMPv1 and
      described in STD 15, RFC 1157 [7].  A second version of the SNMP
      message protocol, which is not an Internet standards track
      protocol, is called SNMPv2c and described in RFC 1901 [18] and RFC
      1906 [19].  The third version of the message protocol is called
      SNMPv3 and described in RFC 1906 [19], RFC 2572 [20] and RFC 2574
      [21].

   o  Protocol operations for accessing management information.  The
      first set of protocol operations and associated PDU formats is
      described in STD 15, RFC 1157 [7].  A second set of protocol
      operations and associated PDU formats is described in RFC 1905
      [8].

   o  A set of fundamental applications described in RFC 2573 [22] and
      the view-based access control mechanism described in RFC 2575
      [23].

   This document specifies a MIB module that is compliant to the SMIv2.
   A MIB conforming to the SMIv1 can be produced through the appropriate
   translations.  The resulting translated MIB must be semantically
   equivalent, except where objects or events are omitted because no
   translation is possible (e.g., use of Counter64).  Some machine
   readable information in SMIv2 will be converted into textual
   descriptions in SMIv1 during the translation process.  However, this
   loss of machine readable information is not considered to change the
   semantics of the MIB.

Bathrick & Ly               Standards Track                     [Page 2]
RFC 2662                     ADSL Line MIB                   August 1999

3.  Object Definitions

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the extended subset of Abstract Syntax Notation One