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

Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2)
RFC 4706

Network Working Group                                     M. Morgenstern
Request for Comments: 4706                                      M. Dodge
Category: Standards Track                               ECI Telecom Ltd.
                                                              S. Baillie
                                                              U. Bonollo
                                                           NEC Australia
                                                           November 2006

                   Definitions of Managed Objects for
              Asymmetric Digital Subscriber Line 2 (ADSL2)

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 (2006).

Abstract

   This document defines a Management Information Base (MIB) module for
   use with network management protocols in the Internet community.  In
   particular, it describes objects used for managing parameters of the
   "Asymmetric Digital Subscriber Line" family of interface types: ADSL,
   ADSL2, ADSL2+, and their variants.

Morgenstern, et al.         Standards Track                     [Page 1]
RFC 4706                     ADSL2-LINE MIB                November 2006

Table of Contents

   1. The Internet-Standard Management Framework ......................3
   2. Overview ........................................................3
      2.1. Relationship to Other MIBs .................................4
           2.1.1. General IF-MIB Integration (RFC 2863) ...............4
           2.1.2. Usage of ifTable ....................................5
      2.2. IANA Considerations ........................................6
      2.3. Conventions Used in the MIB Module .........................6
           2.3.1. Naming Conventions ..................................6
           2.3.2. Textual Conventions .................................7
      2.4. Structure .................................................12
      2.5. Persistence ...............................................15
      2.6. Line Topology .............................................17
      2.7. Counters, Interval Buckets, and Thresholds ................18
           2.7.1. Counters Managed ...................................18
           2.7.2. Minimum Number of Buckets ..........................19
           2.7.3. Interval Buckets Initialization ....................19
           2.7.4. Interval Buckets Validity ..........................19
      2.8. Profiles ..................................................20
           2.8.1. Configuration Profiles and Templates ...............21
           2.8.2. Alarm Configuration Profiles and Templates .........22
           2.8.3. Managing Profiles and Templates ....................22
           2.8.4. Managing Multiple Bearer Channels ..................23
      2.9. Notifications .............................................24
   3. Definitions ....................................................25
   4. Implementation Analysis .......................................155
   5. Security Considerations .......................................155
   6. Acknowledgements ..............................................163
   7. References ....................................................163
      7.1. Normative References .....................................163
      7.2. Informative References ...................................165

Morgenstern, et al.         Standards Track                     [Page 2]
RFC 4706                     ADSL2-LINE MIB                November 2006

1.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to Section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

2.  Overview

   This document defines a Management Information Base (MIB) module for
   use with network management protocols in the Internet community for

[include full document text]