RFC 3440 (rfc3440) - Page 2 of 36
Definitions of Extension Managed Objects for Asymmetric Digital Subscriber Lines
Alternative Format: Original Text Document
RFC 3440 ADSL Line Extension MIB December 2002
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 [RFC 3410].
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 [RFC 2578], STD 58, RFC 2579 [RFC 2579] and STD 58, RFC 2580
[RFC 2580].
2. Introduction
The purpose of this memo is to define a supplemental set of managed
objects that is not covered by the ADSL Line MIB as defined in
[RFC 2662]. This memo addresses the additional objects defined in ITU
G.997.1 [ITU G.997.1].
3. Relationship of ADSL Line Extension MIB with standard MIBs
This section outlines the relationship of the ADSL Line Extension MIB
with other MIBs described in RFCs and in their various degrees of
standardization. In regards to these relationships, the ADSL Line
Extension MIB follows conventions as used by the ADSL Line MIB with
one exception. The value of the RFC 2863 object, ifOperstatus, SHALL
be down(2) when the ADSL line interface is in power state L3, as
defined in ITU G.992.1 [ITU G.992.1], which means no power. Its
value shall be up(1) if the ADSL line interface is in power state L0
(power on) [ITU G.992.1] or L1 (reduced power). Power Status L2 [ITU
G.992.1] is not applicable.
4. Conventions used in the MIB
4.1 Structure
The MIB is organized to follow the same structure of the ADSL Line
MIB [RFC 2662].
Ly & Bathrick Standards Track