Internet DRAFT - draft-baillie-adslmib-vdsldmt

draft-baillie-adslmib-vdsldmt



INTERNET-DRAFT                                                S. Baillie
                                                              U. Bonollo
                                                           NEC Australia

                                                                  B. Ray
                                                                Verilink

                                                           February 2001

            Definitions of Managed Objects for VDSL DMT Lines
                    draft-baillie-adslmib-vdsldmt-00.txt

Status of this Memo

This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other 
groups may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt

The list of Internet-Draft Shadow Directories can be accessed at 
http://www.ietf.org/shadow.html.

To view the entire list of current Internet-Drafts, please check the 
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific
Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).

Copyright Notice

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















Expires August 15, 2001                                         Page [1]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001


Table of Contents

1.      Abstract ..................................................    2
2.      The SNMPv2 Network Management Framework ...................    2
3.      Introduction ..............................................    3
3.1     Relationship of the MIB with Standard MIBs ................    4
3.2     Relationship of the MIB with RFC2662 ......................    4
4.      Conventions used in the MIB ...............................    4
4.1     Textual Conventions .......................................    4
4.2     Structure .................................................    5
4.3     Profiles ..................................................    5
5.      Conformance and Compliance ................................    5
6.      Definitions ...............................................    5
7.      Security Considerations ...................................   13
8.      Acknowledgments ...........................................   13
9.      References ................................................   14
10.     Intellectual Property Notice ..............................   15
11.     Authors' Addresses ........................................   15
12.     Full Copyright Statement ..................................   16

1.  Abstract

This document defines an extension to the ADSL Line MIB [18] for managing
VDSL DMT interfaces.

This document specifies a MIB module in a manner that is both compliant 
to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 
definitions.

2.  The SNMP Management Framework

The SNMP Management Framework presently consists of five major
components:

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

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 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
    The second version, called SMIv2, is described in STD 58, RFC
    2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].

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 [8].  A second version of the SNMP
    message protocol, which is not an Internet standards track
    protocol, is called SNMPv2c and described in RFC 1901 [9] and
    RFC 1906 [10].  The third version of the message protocol is
    called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and
    RFC 2574 [12].

Expires August 15, 2001                                         Page [2]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

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

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

A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [16].

Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB.  Objects in the MIB are
defined using the mechanisms defined in the SMI.

This memo 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 (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.

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 RFC 2119 [17].

2.1.  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 subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name. The object
type together with an object instance serves to uniquely identify a
specific instantiation of the object. For human convenience, we
often use a textual string, termed the descriptor, to also refer to
the object type.

3.  Introduction

This document describes an SNMP MIB for managing VDSL DMT Lines.  The 
MIB provides support for a VDSL-DMT specific profile table to be used 
as an extension of the ADSL Line MIB (RFC2662) [18].

The MIB is intended to be compatible with both the SNMPv1 and SNMPv2.   
The MIB will eventually be located in the MIB tree under MIB 2 
transmission, as discussed in the MIB-2 Integration (RFC 1213 [19] and 
RFC 2863 [20]) section of this document.  Until approved by the IETF, 

Expires August 15, 2001                                         Page [3]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

vendors may also choose to support it under the experimental tree.

NOTE TO RFC EDITOR: please replace the above paragraph with the
following paragraph when appropriate:

The MIB is located in the MIB tree under MIB-2 transmission, as
discussing in the MIB-2 Integration (RFC 1213 [19] and RFC 2863 [20])
section of this document.

3.1.  Relationship of the MIB with Standard MIBs

This section outlines the relationship of this MIB with other MIBs 
described in RFCs and in various degrees of "standardization".
Specifically, MIB-2 as presented in RFC 1213 [19] and RFC 2863 [20]
is discussed.

3.1.1  General MIB-2 Integration (RFCs 1213 and 2863)

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

IANAifType ::= TEXTUAL-CONVENTION
    ...
SYNTAX INTEGER {
    ...
    vdsl(97), -- Very H-Speed Digital Subscrib. Loop
    ...
    }

This MIB will be accessed through the transmission subtree as shown:

vdslInterface  ::= { transmission xxx }
NOTE TO RFC EDITOR: please replace the xxx with an assigned number

3.2   Relationship of the MIB with RFC2662

To be written.

4.  Conventions used in the MIB

4.1.  Textual Conventions

The following textual conventions are defined in the MIB.

o    VdslDmtConfProfileSSF 

    This type is used to specify the number of Symbols per Super 
    Frame.

o    VdslDmtConfProfileSpectrum 

    This type specifies the bin on which to start/stop transmission/

Expires August 15, 2001                                         Page [4]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

    reception on.

o    VdslDmtConfProfileRFIEnable 

    This type is used to enable/disable the Radio Frequency 
    Interference (RFI) canceller.

o    VdslDmtConfProfileRFIBand 

    This type is used to specify the start/stop frequency of the 
    RFI bands.

o    VdslDmtConfProfilePowerCutback 

    For 256 tones, 6-bit values specify the desired receive Power 
    Spectral Density (PSD).

o    VdslDmtConfProfilePowerBoost 

    This type is used to specify a boost value for the transmit 
    Power Spectral Density (PSD).

o    VdslDmtConfProfileEnergyRedist 

    This type is used to enable/disable energy redistribution.

4.2.  Structure

The MIB provides a profile table for configuring a VDSL DMT line.

o   Line Configuration Group:

    This group supports MIB objects for configuring parameters for
    the VDSL DMT Line.  It contains the following table(s):

    - vdslDMTConfProfileTable

4.3.  Profiles

The MIB defines a profile table, vdslDMTConfProfileTable, that contains
VDSL-specific configuration information.  Further discussion on profile
implementation may be found in RFC2662.

5.  Conformance and Compliance

The following group(s) are mandatory:

    vdslDMTConfProfileGroup

6.  Definitions

VDSL-DMT-LINE-MIB DEFINITIONS ::= BEGIN


Expires August 15, 2001                                         Page [5]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

IMPORTS
MODULE-IDENTITY, 
OBJECT-TYPE                   FROM SNMPv2-SMI
TEXTUAL-CONVENTION,
TruthValue                    FROM SNMPv2-TC
adslLineConfProfileName,
adslMIB                       FROM ADSL-LINE-MIB;

vdslDMTMib MODULE-IDENTITY
    LAST-UPDATED "200102150000Z"    -- February 15, 2001
    ORGANIZATION "ADSLMIB Working Group"
    CONTACT-INFO
    "
        Scott Baillie
        NEC Australia Pty. Ltd.
        649-655 Springvale Road
        Mulgrave 3170, Victoria, Australia
        Tel: +61 3 9262 1111
        Fax: +61 3 9264 3892
        E-mail: scottb@nstc.nec.com.au

        Umberto Bonollo
        NEC Australia Pty. Ltd.
        649-655 Springvale Road
        Mulgrave 3170, Victoria, Australia
        Tel: +61 3 9262 1111
        Fax: +61 3 9264 3892
        E-mail: umberto@nstc.nec.com.au
    
        Bob Ray
        Verilink Corporation
        950 Explorer Blvd. 
        Huntsville, AL 35758 USA
        Tel: +1 256-327-2380
        Fax: +1 256-327-2880
        E-mail: bray@verilink.com
        "

    DESCRIPTION
        "This MIB module defines a collection of objects for
        managing VDSL DMT Lines.  These objects extend the ADSL-LINE-MIB
        (RFC2662)."

    ::= { adslMIB 4 }  

vdslDMTMibObjects OBJECT IDENTIFIER ::= { vdslDMTMib 1 }

-- Textual Conventions used in this MIB
--



Expires August 15, 2001                                         Page [6]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

VdslDmtConfProfileSSF ::= TEXTUAL-CONVENTION
    STATUS current
    DESCRIPTION
        "This type is used to specify the number of Symbols per Super
        Frame. The super frame consists of a number of symbols, the
        symbols are grouped as upstream symbols, downstream symbols
        and quiescent symbols. The number of symbols in a super frame
        is fixed but the number of upstream and downstream symbols
        can be varied, hence the upstream and downstream bandwidth
        can be varied."
    SYNTAX INTEGER (0..255)

VdslDmtConfProfileSpectrum ::= TEXTUAL-CONVENTION
    STATUS current
    DESCRIPTION
        "This type specifies the bin on which to start/stop
        transmission/reception on."
    SYNTAX INTEGER (4..255)

VdslDmtConfProfileRFIEnable ::= TEXTUAL-CONVENTION
    STATUS current
    DESCRIPTION
        "This type is used to enable/disable the Radio Frequency
        Interference (RFI) canceller.  The RFI Canceler is a system
        that allows the VDSL modems to avoid transmitting on certain
        frequency bands.  The position and range of each frequency
        band can be specified. The frequency bands are positioned
        such that they lie over a known source of RFI."
    SYNTAX TruthValue

VdslDmtConfProfileRFIBand ::= TEXTUAL-CONVENTION
    STATUS current
    DESCRIPTION
        "This type is used to specify the start/stop frequency of the
        RFI bands."
    SYNTAX INTEGER (4..255)

VdslDmtConfProfilePowerCutback ::= TEXTUAL-CONVENTION
    STATUS current
    DESCRIPTION
        "For 256 tones, 6-bit values specify the desired receive
        Power Spectral Density (PSD).  The units of the values are 'dB
        down from maximum power,' and each value is valid for 8
        tones.  For example, if the third value in the 32-value table
        is 22, then the desired receive PSD for tones 16-23 is 22 dB
        below the maximum transmit PSD."
    SYNTAX OCTET STRING (SIZE(32))

VdslDmtConfProfilePowerBoost ::= TEXTUAL-CONVENTION
    STATUS current
    DESCRIPTION
        "This type is used to specify a boost value for the transmit


Expires August 15, 2001                                         Page [7]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

        Power Spectral Density (PSD)."
    SYNTAX INTEGER {
      noPsdBoost(0),  -- No boost to transmit Power Spectral 
                      -- Density (PSD).
      psdBoost3dB(1), -- Restricts transmission in both Directions 
                      -- to within the lower 128 subchannels but at 
                      -- 3 dB higher transmit PSD.
      psdBoost6dB(2), -- Restricts transmission in both Directions to 
                      -- within the lower 64 subchannels but at 6 dB 
                      -- higher transmit PSD.
      psdBoost1dB(3)  -- Restricts transmission in both Directions to 
                      -- within the lower 192 subchannels but at 1 dB 
                      -- higher transmit PSD.
    }

VdslDmtConfProfileEnergyRedist ::= TEXTUAL-CONVENTION
    STATUS current
    DESCRIPTION
        "This type is used to enable/disable energy redistribution.
        Use of energy redistribution allows energy that would have
        been allocated to subchannels that are not used to be
        redistributed to subchannels supporting data transmission."
    SYNTAX TruthValue

-- Profile Group
--

vdslDMTConfProfileTable OBJECT-TYPE
    SYNTAX	SEQUENCE OF VdslDMTConfProfileEntry
    MAX-ACCESS	not-accessible
    STATUS	current
    DESCRIPTION
        "This table contains configuration parameters that
         apply to VDSL modems."
    ::= { vdslDMTMibObjects 1 }

vdslDMTConfProfileEntry OBJECT-TYPE
    SYNTAX	VdslDMTConfProfileEntry
    MAX-ACCESS	not-accessible
    STATUS	current
    DESCRIPTION
        "An entry for the vdslDMTConfProfileTable"
    INDEX { IMPLIED adslLineConfProfileName }
    ::= { vdslDMTConfProfileTable 1 }

VdslDMTConfProfileEntry ::= SEQUENCE 
    {
    vdslDmtConfProfileSSFTotal      VdslDmtConfProfileSSF,
    vdslDmtConfProfileSSFDownStream VdslDmtConfProfileSSF,
    vdslDmtConfProfileLowSpectrum   VdslDmtConfProfileSpectrum,
    vdslDmtConfProfileHighSpectrum  VdslDmtConfProfileSpectrum,
    vdslDmtConfProfileRFIEnable     VdslDmtConfProfileRFIEnable,


Expires August 15, 2001                                         Page [8]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

    vdslDmtConfProfileRFIBand1Low   VdslDmtConfProfileRFIBand,
    vdslDmtConfProfileRFIBand1High  VdslDmtConfProfileRFIBand,
    vdslDmtConfProfileRFIBand2Low   VdslDmtConfProfileRFIBand,
    vdslDmtConfProfileRFIBand2High  VdslDmtConfProfileRFIBand,
    vdslDmtConfProfileRFIBand3Low   VdslDmtConfProfileRFIBand,
    vdslDmtConfProfileRFIBand3High  VdslDmtConfProfileRFIBand,
    vdslDmtConfProfileRFIBand4Low   VdslDmtConfProfileRFIBand,
    vdslDmtConfProfileRFIBand4High  VdslDmtConfProfileRFIBand,
    vdslDmtConfProfilePowerCutback  VdslDmtConfProfilePowerCutback,
    vdslDmtConfProfilePowerBoost    VdslDmtConfProfilePowerBoost,
    vdslDmtConfProfileEnergyRedist  VdslDmtConfProfileEnergyRedist
    }

vdslDmtConfProfileSSFTotal OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileSSF
    UNITS       "Number of Symbols"
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "Total number of symbols per superframe. Note that currently
        the total must be set to 20. The sum of
        up-stream-symbols+down-stream-symbols+quiescent-symbols must
        be equal to total-symbols. Note that currently
        quiescent-symbols=2. Note that currently down-stream-symbols
        can be in the range 7..16"
    ::= { vdslDmtConfProfileEntry 1 }

vdslDmtConfProfileSSFDownStream OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileSSF
    UNITS       "Number of Symbols"
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "Number of down stream symbols per superframe.  The sum of
        up-stream-symbols+down-stream-symbols+quiescent-symbols must
        be equal to total-symbols.  Note that currently
        quiescent-symbols = 2.  Note that currently
        down-stream-symbols can be in the range 7..16"
    ::= { vdslDmtConfProfileEntry 2 }

vdslDmtConfProfileLowSpectrum OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileSpectrum
    UNITS       "Bin number"
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "The lower edge of the down stream and up stream transmit
        spectrum is controlled by this setting. This setting is the
        first bin on which to transmit/receive."
    ::= { vdslDmtConfProfileEntry 3 }

vdslDmtConfProfileHighSpectrum OBJECT-TYPE


Expires August 15, 2001                                         Page [9]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

    SYNTAX      VdslDmtConfProfileSpectrum
    UNITS       "Bin number"
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "The highest edge of the down stream and up stream transmit
        spectrum is controlled by this setting. This setting is the
        last bin on which to transmit/receive"
    ::= { vdslDmtConfProfileEntry 4 }

vdslDmtConfProfileRFIEnable OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileRFIEnable
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "Enable/disable the RFI canceller.  Enabling the RFI
        canceller mitigates egress into the bands specified by
        RFIBands and prevents the modems from transmitting on
        subchannels within those bands."
    ::= { vdslDmtConfProfileEntry 5 }

vdslDmtConfProfileRFIBand1Low OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileRFIBand
    UNITS       "Bin number"
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "This setting specifies the start frequency of RFI band 1."
    ::= { vdslDmtConfProfileEntry 6 }

vdslDmtConfProfileRFIBand1High OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileRFIBand
    UNITS       "Bin number"
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "This setting specifies the stop frequency of RFI band 1."
    ::= { vdslDmtConfProfileEntry 7 }

vdslDmtConfProfileRFIBand2Low OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileRFIBand
    UNITS       "Bin number"
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "This setting specifies the start frequency of RFI band 2."
    ::= { vdslDmtConfProfileEntry 8 }

vdslDmtConfProfileRFIBand2High OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileRFIBand
    UNITS       "Bin number"
    MAX-ACCESS	read-create


Expires August 15, 2001                                        Page [10]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

    STATUS	current
    DESCRIPTION
        "This setting specifies the stop frequency of RFI band 2."
    ::= { vdslDmtConfProfileEntry 9 }

vdslDmtConfProfileRFIBand3Low OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileRFIBand
    UNITS       "Bin number"
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "This setting specifies the start frequency of RFI band 3."
    ::= { vdslDmtConfProfileEntry 10 }

vdslDmtConfProfileRFIBand3High OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileRFIBand
    UNITS       "Bin number"
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "This setting specifies the stop frequency of RFI band 3."
    ::= { vdslDmtConfProfileEntry 11 }

vdslDmtConfProfileRFIBand4Low OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileRFIBand
    UNITS       "Bin number"
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "This setting specifies the start frequency of RFI band 4."
    ::= { vdslDmtConfProfileEntry 12 }

vdslDmtConfProfileRFIBand4High OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileRFIBand
    UNITS       "Bin number"
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "This setting specifies the stop frequency of RFI band 4."
    ::= { vdslDmtConfProfileEntry 13 }

vdslDmtConfProfilePowerCutback OBJECT-TYPE
    SYNTAX       VdslDmtConfProfilePowerCutback
    UNITS       "dB down from maximum power"
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "This array is used to set the desired receive Power Spectral
        Density (PSD) at a value below the maximum transmit PSD."
    ::= { vdslDmtConfProfileEntry 14 }

vdslDmtConfProfilePowerBoost OBJECT-TYPE


Expires August 15, 2001                                        Page [11]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

    SYNTAX      VdslDmtConfProfilePowerBoost
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "This variable is used to specify a boost value for the
        transmit Power Spectral Density (PSD)."
    ::= { vdslDmtConfProfileEntry 15 }

vdslDmtConfProfileEnergyRedist OBJECT-TYPE
    SYNTAX      VdslDmtConfProfileEnergyRedist
    MAX-ACCESS	read-create
    STATUS	current
    DESCRIPTION
        "This variable enables/disable energy redistribution.
         Use of energy redistribution allows energy that would have
         been allocated to subchannels that are not used to be
         redistributed to subchannels supporting data transmission."
    ::= { vdslDmtConfProfileEntry 16 }

-- conformance information
--

vdslConformance OBJECT IDENTIFIER ::= { vdslDMTMib 2 }
vdslGroups      OBJECT IDENTIFIER ::= { vdslConformance 1 }
vdslCompliances OBJECT IDENTIFIER ::= { vdslConformance 2 }

-- agent compliance statements

vdslLineMibCompliance MODULE-COMPLIANCE
    STATUS  current
    DESCRIPTION
        "The section outlines compliance requirements for this MIB."
    MODULE
    MANDATORY-GROUPS
    {
    vdslDMTConfProfileGroup
    }
::= { vdslCompliances 1 }

-- units of conformance
--

vdslDMTConfProfileGroup OBJECT-GROUP
    OBJECTS
    {
    vdslDmtConfProfileSSFTotal,
    vdslDmtConfProfileSSFDownStream,
    vdslDmtConfProfileLowSpectrum,
    vdslDmtConfProfileHighSpectrum,
    vdslDmtConfProfileRFIEnable,
    vdslDmtConfProfileRFIBand1Low,
    vdslDmtConfProfileRFIBand1High,


Expires August 15, 2001                                        Page [12]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

    vdslDmtConfProfileRFIBand2Low,
    vdslDmtConfProfileRFIBand2High,
    vdslDmtConfProfileRFIBand3Low,
    vdslDmtConfProfileRFIBand3High,
    vdslDmtConfProfileRFIBand4Low,
    vdslDmtConfProfileRFIBand4High,
    vdslDmtConfProfilePowerCutback,
    vdslDmtConfProfilePowerBoost,
    vdslDmtConfProfileEnergyRedist
    }
    STATUS      current
    DESCRIPTION
        "This group supports objects for configuring VDSL DMT lines."
    ::= { vdslGroups 1 }

END

7.  Security Considerations

There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create.  Such
objects may be considered sensitive or vulnerable in some network
environments.  The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.

No managed objects in this MIB contain sensitive information.

SNMPv1 by itself is not a secure environment.  Even if the network
itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB.

It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework.  Specifically, the use
of the User-based Security Model RFC 2574 [12] and the View-
based Access Control Model RFC 2575 [15] is recommended.

It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET
(change/create/delete) them.

8.  Acknowledgments

The authors are deeply grateful to the authors of the ADSL-LINE-EXT-MIB,
Gregory Bathrick and Faye Ly, as much of the text and structure of this 
document originates in their documents.

Contributions have been received from, but not limited to the following:

Brian Johnson (NEC Australia)

Expires August 15, 2001                                        Page [13]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

9.  References

[1]  Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 
Describing SNMP Management Frameworks", RFC 2571, April 1999.

[2]  Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990.

[3]  Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.

[4]  M. Rose, "A Convention for Defining Traps for use with the SNMP",
RFC 1215, March 1991.

[5]  McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

[6]  McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
RFC 2579, April 1999.

[7]  McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58,
RFC 2580, April 1999.

[8]  Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990.

[9]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January
1996.

[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 
Mappings for Version 2 of the Simple Network Management Protocol 
(SNMPv2)", RFC 1906, January 1996.

[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999.

[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol (SNMPv3)",
RFC 2574, April 1999.

[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 
Operations for Version 2 of the Simple Network Management Protocol 
(SNMPv2)", RFC 1905, January 1996.

[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2573, April 1999.


Expires August 15, 2001                                        Page [14]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999.

[16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to
Version 3 of the Internet-standard Network Management Framework",
RFC 2570, April 1999.

[17] Bradner, S., "Key Words for use in RFCs to Indicate Requirement 
Levels", RFC 2119, March 1997.

[18] Bathrick, G., Ly, F., "Definitions of Managed Objects for the ADSL 
Lines",  RFC 2662, August 1999.

[19] McCloghrie, K., and M. Rose, Editors, "Management Information Base
for Network Management of TCP/IP-based internets: MIB-II", STD 17,
RFC 1213, March 1991.

[20] McCloghrie, K., and Kastenholz, F., "The Interfaces Group MIB",
RFC 2863, June 2000.

10.  Intellectual Property Notice

The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights.  Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11.  Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.

The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard.  Please address the information to the IETF Executive 
Director.

11.  Authors' Addresses

Scott Baillie
NEC Australia Pty. Ltd.
649-655 Springvale Road
Mulgrave 3170, Victoria, Australia
Tel: +61 3 9262 1111
Fax: +61 3 9264 3892
E-mail: scottb@nstc.nec.com.au


Expires August 15, 2001                                        Page [15]

INTERNET-DRAFT               VDSL-DMT-LINE MIB             February 2001

Umberto Bonollo
NEC Australia Pty. Ltd.
649-655 Springvale Road
Mulgrave 3170, Victoria, Australia
Tel: +61 3 9262 1111
Fax: +61 3 9264 3892
E-mail: umberto@nstc.nec.com.au

Bob Ray
Verilink Corporation
950 Explorer Blvd. 
Huntsville, AL 35806 USA
Tel: +1 256-327-2380
Fax: +1 256-327-2880
E-mail: bray@verilink.com

12.  Full Copyright Statement

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

This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works.  However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.

The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.











Expires August 15, 2001                                        Page [16]