datatracker.ietf.org
Sign in
Version 5.6.1.p1, 2014-07-16
Report a bug

Definitions of Managed Objects for Very High Speed Digital Subscriber Lines (VDSL)
RFC 3728

Document type: RFC - Proposed Standard (February 2004; 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 3728 (Proposed Standard)
Responsible AD: Bert Wijnen
Send notices to: <sneedmike@hotmail.com>, <Randy_Presuhn@mindspring.com>

Network Working Group                                             B. Ray
Request for Comments: 3728                        PESA Switching Systems
Category: Standards Track                                        R. Abbi
                                                                 Alcatel
                                                           February 2004

              Definitions of Managed Objects for Very High
                 Speed Digital Subscriber Lines (VDSL)

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 (2004).  All Rights Reserved.

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 Very High Speed
   Digital Subscriber Line (VDSL) interfaces.

Table of Contents

   1.  The Internet-Standard Management Framework . . . . . . . . . .  2
   2.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  2
       2.1.  Relationship of the VDSL Line MIB Module to other MIB
             Modules. . . . . . . . . . . . . . . . . . . . . . . . .  2
       2.2.  Conventions used in the MIB Module . . . . . . . . . . .  4
       2.3.  Structure. . . . . . . . . . . . . . . . . . . . . . . .  5
       2.4.  Counters, Interval Buckets and Thresholds. . . . . . . .  7
       2.5.  Profiles . . . . . . . . . . . . . . . . . . . . . . . .  8
       2.6.  Notifications. . . . . . . . . . . . . . . . . . . . . .  9
       2.7.  Persistence. . . . . . . . . . . . . . . . . . . . . . . 10
   3.  Conformance and Compliance . . . . . . . . . . . . . . . . . . 11
   4.  Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 11
   5.  Security Considerations. . . . . . . . . . . . . . . . . . . . 71
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 72
       6.1.  Normative References . . . . . . . . . . . . . . . . . . 72
       6.2.  Informative References . . . . . . . . . . . . . . . . . 74
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 74

Ray & Abbi                  Standards Track                     [Page 1]
RFC 3728                     VDSL-LINE MIB                 February 2004

   8.  Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 75
   9.  Full Copyright Statement . . . . . . . . . . . . . . . . . . . 76

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].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Overview

   This document describes an SNMP MIB module for managing VDSL Lines.
   These definitions are based upon the specifications for VDSL as
   defined in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011,
   T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971].

   The MIB module is located in the MIB tree under MIB 2 transmission,
   as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of
   this document.

2.1.   Relationship of the VDSL Line MIB Module to other MIB Modules

   This section outlines the relationship of this MIB with other MIBs
   described in RFCs.  Specifically, IF-MIB as presented in RFC 2863
   [RFC2863] is discussed.

2.1.1.   General IF-MIB Integration (RFC 2863)

   The VDSL Line MIB specifies the detailed attributes of a data
   interface.  As such, it needs to integrate with RFC 2863 [RFC2863].
   The IANA has assigned the following ifType to VDSL:

Ray & Abbi                  Standards Track                     [Page 2]

[include full document text]