datatracker.ietf.org
Sign in
Version 5.6.4.p1, 2014-10-20
Report a bug

Definitions of Extension Managed Objects for Asymmetric Digital Subscriber Lines
RFC 3440

Document type: RFC - Proposed Standard (January 2003; No errata)
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 3440 (Proposed Standard)
Responsible AD: Bert Wijnen
IESG Note: Published as RFC 3440
Send notices to: <sneedmike@hotmail.com>

Network Working Group                                              F. Ly
Request for Comments: 3440                             Pedestal Networks
Category: Standards Track                                    G. Bathrick
                                                                   Nokia
                                                           December 2002

                Definitions of Extension Managed Objects
                for Asymmetric Digital Subscriber 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 (2002).  All Rights Reserved.

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes additional managed objects used for
   managing Asymmetric Digital Subscriber Line (ADSL) interfaces not
   covered by the ADSL Line MIB (RFC 2662).

Table of Contents

   1.  The Internet-Standard Management Framework ................. 2
   2.  Introduction ............................................... 2
   3.  Relationship of ADSL LINE EXTENSION MIB with standard MIBs . 2
   4.  Conventions used in the MIB ................................ 2
   5.  Conformance and Compliance ................................. 6
   6.  Definitions ................................................ 6
   7.  Acknowledgments ............................................31
   8.  References .................................................31
   9.  Security Considerations ....................................32
   10. Intellectual Property Notice ...............................34
   11. Authors' Addresses .........................................35
   12. Full Copyright Statement ...................................36

Ly & Bathrick               Standards Track                     [Page 1]
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 [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.  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
   [RFC2662].  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 [RFC2662].

Ly & Bathrick               Standards Track                     [Page 2]
RFC 3440                ADSL Line Extension MIB            December 2002

4.2  Additional Managed Objects

   Objects specific to the management of ADSL G.Lite as defined in ITU
   G.992.2 [ITU G.992.2] are:

   - ADSL Transceiver Unit - Central Office End (ATU-C)
     Transmission System and Line Mode
   - Power Management
   - Counters for Fast Retrains and Failed Fast Retrains
   - Counters for Severe Error Second-line and Unavailable Second

[include full document text]