draft-ietf-adslmib-vdsl-ext-mcm-02.txt   draft-ietf-adslmib-vdsl-ext-mcm-03.txt 
Network Working Group M. Dodge Network Working Group M. Dodge
Category: Internet Draft Infineon Technologies Category: Internet Draft Infineon Technologies
B. Ray B. Ray
PESA Switching Systems PESA Switching Systems
March 2004 March 2004
Definitions of Managed Object Extensions Definitions of Managed Object Extensions
for Very High Speed Digital Subscriber Lines (VDSL) Using for Very High Speed Digital Subscriber Lines (VDSL) Using
Multiple Carrier Modulation (MCM) Line Coding Multiple Carrier Modulation (MCM) Line Coding
draft-ietf-adslmib-vdsl-ext-mcm-02.txt draft-ietf-adslmib-vdsl-ext-mcm-03.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at page 1, line 39 skipping to change at page 1, line 38
The list of current Internet-Drafts can be accessed at: The list of current Internet-Drafts can be accessed at:
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at: The list of Internet-Draft Shadow Directories can be accessed at:
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
IPR Disclosure Acknowledgement
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Abstract Abstract
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) module for use with network management protocols in the (MIB) module for use with network management protocols in the
Internet community. In particular, it describes objects used for Internet community. In particular, it describes objects used for
managing the Line Code Specific parameters of Very High Speed managing the Line Code Specific parameters of Very High Speed
Digital Subscriber Line (VDSL) interfaces using Multiple Carrier Digital Subscriber Line (VDSL) interfaces using Multiple Carrier
Modulation (MCM) Line Coding. It is an optional extension to the Modulation (MCM) Line Coding. It is an optional extension to the
VDSL-LINE-MIB, RFC 3728 [RFC3728], which handles line code VDSL-LINE-MIB, RFC 3728 [RFC3728], which handles line code
independent objects. independent objects.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework .................... 2 1. The Internet-Standard Management Framework .................... 2
2. Overview ...................................................... 2 2. Overview ...................................................... 2
2.1 Relationship of this MIB Module to other MIB Modules .......... 2 2.1 Relationship of this MIB Module to other MIB Modules .......... 3
2.2 Conventions used in the MIB Module ............................ 3 2.2 Conventions used in the MIB Module ............................ 3
2.3 Structure ..................................................... 3 2.3 Structure ..................................................... 3
2.4 Persistence ................................................... 4 2.4 Persistence ................................................... 4
3. Conformance and Compliance .................................... 5 3. Conformance and Compliance .................................... 5
4. Definitions ................................................... 5 4. Definitions ................................................... 5
5. Security Considerations ....................................... 17 5. Acknowledgements .............................................. 18
6. References .................................................... 18 6. Security Considerations ....................................... 18
6.1 Normative References .......................................... 18 7. References .................................................... 19
6.2 Informative References ........................................ 19 7.1 Normative References .......................................... 19
7. Acknowledgements .............................................. 19 7.2 Informative References ........................................ 20
8. Authors' Addresses ............................................ 20 8. Authors' Addresses ............................................ 21
9. Full Copyright Statement ...................................... 20 9. Full Copyright Statement ...................................... 21
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a Structure of Management Information (SMI). This memo specifies a
MIB module that is compliant to the SMIv2, which is described in STD 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 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
2580 [RFC2580]. 2580 [RFC2580].
The key words "MAY", "MUST", "MUST NOT", "RECOMMENDED",
"NOT RECOMMENDED", and "SHOULD" in this document are to be
interpreted as described in [RFC2119].
2. Overview 2. Overview
This document describes an SNMP MIB module for managing the line This document describes an SNMP MIB module for managing the Line
code dependent (Physical Medium Dependent) Layer of MCM VDSL Lines. Code Dependent, Physical Medium Dependent (PMD), Layer of MCM VDSL
These definitions are based upon the specifications for VDSL as Lines. These definitions are based upon the specifications for VDSL
defined in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011, as defined in T1E1, European Telecommunications Standards Institute
T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. Additionally the (ETSI), and International Telecommunication Union (ITU) documentation
protocol-dependent (and line-code dependent) management framework [T1E1311, T1E1011, T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971].
for VDSL lines specified by DSLF has been taken into consideration Additionally the protocol-dependent (and line-code dependent)
management framework for VDSL lines specified by the Digital
Subscriber Line Forum (DSLF) has been taken into consideration
[DSLFTR057]. [DSLFTR057].
The MIB module is located in the MIB tree under MIB 2 transmission, The MIB module is located in the MIB tree under the vdslMIB, which
as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section in turn is found under MIB 2 transmission. The reader is referred to
of this document. RFC 3728 [RFC3728] for further discussion of this subject.
2.1 Relationship of this MIB Module to other MIB Modules 2.1 Relationship of this MIB Module to other MIB Modules
The relationship of the VDSL Line MIB to other MIBS and in particular The relationship of the VDSL Line MIB module to other MIB modules
to the IF-MIB, as presented in RFC 2863 [RFC2863], is discussed in and in particular to the IF-MIB, as presented in RFC 2863 [RFC2863],
the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section outlines the is discussed in the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section
relationship of this VDSL Line Extension MIB to the VDSL-LINE-MIB, outlines the relationship of this VDSL Line Extension MIB to the
RFC 3728 [RFC3728]. VDSL-LINE-MIB, RFC 3728 [RFC3728].
2.2 Conventions used in the MIB Module 2.2 Conventions used in the MIB Module
2.2.1 Naming Conventions 2.2.1 Naming Conventions
A. Vtuc -- (VTUC) transceiver at near (Central) end of line A. Vtuc -- (VTUC) transceiver at near (Central) end of line
B. Vtur -- (VTUR) transceiver at Remote end of line B. Vtur -- (VTUR) transceiver at Remote end of line
C. Vtu -- One of either Vtuc or Vtur C. Vtu -- One of either Vtuc or Vtur
D. Curr -- Current D. Curr -- Current
E. LCS -- Line Code Specific E. LCS -- Line Code Specific
skipping to change at page 3, line 39 skipping to change at page 3, line 45
and for montioring individual bands of Multiple Carrier Modulation and for montioring individual bands of Multiple Carrier Modulation
(MCM) VDSL modems. It contains the following tables: (MCM) VDSL modems. It contains the following tables:
- vdslLineMCMConfProfileTable - vdslLineMCMConfProfileTable
- vdslLineMCMConfProfileTxBandTable - vdslLineMCMConfProfileTxBandTable
- vdslLineMCMConfProfileRxBandTable - vdslLineMCMConfProfileRxBandTable
- vdslLineMCMConfProfileTxPSDTable - vdslLineMCMConfProfileTxPSDTable
- vdslLineMCMConfProfileMaxTxPSDTable - vdslLineMCMConfProfileMaxTxPSDTable
- vdslLineMCMConfProfileMaxRxPSDTable - vdslLineMCMConfProfileMaxRxPSDTable
None, some or all of the objects in this group MAY be If the MCM VDSL Line Extension MIB is implemented then all of the
implemented for MCM VDSL lines. objects in this group MUST be implemented.
Figure 1, below, displays the relationship of the tables in the Figure 1, below, displays the relationship of the tables in the
vdslMCMGroup to the vdslGroup and to the ifEntry: vdslMCMGroup to the vdslGroup and to the ifEntry:
ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1)
vdslLineTableEntry (vdslLineCoding=MCM) vdslLineTableEntry (vdslLineCoding=MCM)
vdslLineConfProfileEntry(vdslLineConfProfileName) vdslLineConfProfileEntry(vdslLineConfProfileName)
----> vdslLineMCMConfProfileTable 1:(0..1) ----> vdslLineMCMConfProfileTable 1:(0..1)
----> vdslLineMCMConfProfileTxBandTable 1:(0..1) ----> vdslLineMCMConfProfileTxBandTable 1:(0..n)
----> vdslLineMCMConfProfileRxBandTable 1:(0..1) ----> vdslLineMCMConfProfileRxBandTable 1:(0..n)
----> vdslLineMCMConfProfileTxPSDTable 1:(0..1) ----> vdslLineMCMConfProfileTxPSDTable 1:(0..n)
----> vdslLineMCMConfProfileMaxTxPSDTable 1:(0..1) ----> vdslLineMCMConfProfileMaxTxPSDTable 1:(0..n)
----> vdslLineMCMConfProfileMaxRxPSDTable 1:(0..1) ----> vdslLineMCMConfProfileMaxRxPSDTable 1:(0..n)
Figure 1: Table Relationships Figure 1: Table Relationships
When the object vdslLineCoding is set to MCM, When the object vdslLineCoding is set to MCM,
vdslLineConfProfileName is used as the index to vdslLineConfProfileName is used as the index to
vdslLineMCMConfProfileTxBandTable. The existence of an entry in vdslLineMCMConfProfileTxBandTable. The existence of an entry in
any of the tables of the vdslMCMGroup is optional. None, some or any of the tables of the vdslMCMGroup is optional.
all of the vdslMCMGroup tables MAY be implemented for a particular
VDSL line entity using MCM line coding.
2.4 Persistence 2.4 Persistence
All read-create objects defined in this MIB module SHOULD be stored All read-create objects defined in this MIB module SHOULD be stored
persistently. Following is an exhaustive list of these persistent persistently. Following is an exhaustive list of these persistent
objects: objects:
vdslMCMConfProfileTxWindowLength vdslMCMConfProfileTxWindowLength
vdslMCMConfProfileRowStatus vdslMCMConfProfileRowStatus
vdslMCMConfProfileTxBandNumber vdslMCMConfProfileTxBandNumber
skipping to change at page 4, line 51 skipping to change at page 4, line 49
vdslMCMConfProfileTxPSDTone vdslMCMConfProfileTxPSDTone
vdslMCMConfProfileTxPSDPSD vdslMCMConfProfileTxPSDPSD
vdslMCMConfProfileTxPSDRowStatus vdslMCMConfProfileTxPSDRowStatus
vdslMCMConfProfileMaxTxPSDTone vdslMCMConfProfileMaxTxPSDTone
vdslMCMConfProfileMaxTxPSDPSD vdslMCMConfProfileMaxTxPSDPSD
vdslMCMConfProfileMaxTxPSDRowStatus vdslMCMConfProfileMaxTxPSDRowStatus
vdslMCMConfProfileMaxRxPSDTone vdslMCMConfProfileMaxRxPSDTone
vdslMCMConfProfileMaxRxPSDPSD vdslMCMConfProfileMaxRxPSDPSD
vdslMCMConfProfileMaxRxPSDRowStatus vdslMCMConfProfileMaxRxPSDRowStatus
It SHOULD also be noted that interface indices in this MIB are Note also that the interface indices in this MIB are maintained
maintained persistently. VACM data relating to these SHOULD be persistently. View-based Access Control Model (VACM) data
stored persistently as well [RFC2575]. relating to these SHOULD be stored persistently as well [RFC3415].
3. Conformance and Compliance 3. Conformance and Compliance
For MCM VDSL lines, the following group is optional: An MCM based VDSL agent does not have to implement this MIB to be
compliant with RFC 3728 [RFC3728]. If the MCM VDSL Line Extension
MIB is implemented then the following group is mandatory:
- vdslMCMGroup - vdslMCMGroup
4. Definitions 4. Definitions
VDSL-LINE-EXT-MCM-MIB DEFINITIONS ::= BEGIN VDSL-LINE-EXT-MCM-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Unsigned32 FROM SNMPv2-SMI -- [RFC2578] Unsigned32 FROM SNMPv2-SMI -- [RFC2578]
RowStatus FROM SNMPv2-TC -- [RFC2579] RowStatus FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
vdslMIB,
vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728] vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728]
vdslExtMCMMIB MODULE-IDENTITY vdslExtMCMMIB MODULE-IDENTITY
LAST-UPDATED "200403140000Z" -- March 14, 2004 LAST-UPDATED "200403300000Z" -- March 30, 2004
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
Sand Channel Systems Sand Channel Systems
Postal: P.O. Box 37324 Postal: P.O. Box 37324
Raleigh NC 27627-732 Raleigh NC 27627-732
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
Phone: +1 206 600 7022 Phone: +1 206 600 7022
skipping to change at page 6, line 11 skipping to change at page 6, line 13
" "
DESCRIPTION DESCRIPTION
"The VDSL-LINE-MIB found in RFC 3728 defines objects for "The VDSL-LINE-MIB found in RFC 3728 defines objects for
the management of a pair of VDSL transceivers at each end of the management of a pair of VDSL transceivers at each end of
the VDSL line. The VDSL-LINE-MIB configures and monitors the the VDSL line. The VDSL-LINE-MIB configures and monitors the
line code independent parameters (TC layer) of the VDSL line. line code independent parameters (TC layer) of the VDSL line.
This MIB module is an optional extension of the VDSL-LINE-MIB This MIB module is an optional extension of the VDSL-LINE-MIB
and defines objects for configuration and monitoring of the and defines objects for configuration and monitoring of the
line code specific (LCS) elements (PMD layer) for VDSL lines line code specific (LCS) elements (PMD layer) for VDSL lines
using MCM coding. The objects in this extension MIB MUST NOT using MCM coding. The objects in this extension MIB MUST NOT
be used for VDSL lines using SCM line coding. be used for VDSL lines using Single Carrier Modulation (SCM)
line coding. If an object in this extension MIB is referenced
by a line which does not use MCM, it has no effect on the
operation of that line.
Naming Conventions: Naming Conventions:
Vtuc -- (VTUC) transceiver at near (Central) end of line Vtuc -- (VTUC) transceiver at near (Central) end of line
Vtur -- (VTUR) transceiver at Remote end of line Vtur -- (VTUR) transceiver at Remote end of line
Vtu -- One of either Vtuc or Vtur Vtu -- One of either Vtuc or Vtur
Curr -- Current Curr -- Current
LCS -- Line Code Specific LCS -- Line Code Specific
Max -- Maximum Max -- Maximum
PSD -- Power Spectral Density PSD -- Power Spectral Density
Rx -- Receive Rx -- Receive
Tx -- Transmit Tx -- Transmit
Copyright (C) The Internet Society (2004). This version Copyright (C) The Internet Society (2004). This version
of this MIB module is part of RFC XXXX: see the RFC of this MIB module is part of RFC XXXX: see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
REVISION "200403140000Z" -- March 14, 2004 REVISION "200403300000Z" -- March 30, 2004
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
::= { vdslMIB XX } -- To be assigned by IANA ::= { vdslMIB XX } -- To be assigned by IANA
-- RFC Ed.: we suggest to put it under { vdslMIB 3 } because -- RFC Ed.: we suggest to put it under { vdslMIB 3 } because
-- vdslMIB 1 is the VDSL-LINE-MIB, vdslMIB 2 is the SCM
-- extension MIB, while vdslMIB 3 is this MCM extension MIB.
vdslLineExtMCMMib OBJECT IDENTIFIER ::= { vdslExtMCMMIB 1 } vdslLineExtMCMMib OBJECT IDENTIFIER ::= { vdslExtMCMMIB 1 }
vdslLineExtMCMMibObjects OBJECT IDENTIFIER ::= {vdslLineExtMCMMib 1} vdslLineExtMCMMibObjects OBJECT IDENTIFIER ::= {vdslLineExtMCMMib 1}
-- --
-- Multiple carrier modulation (MCM) configuration profile tables -- Multiple carrier modulation (MCM) configuration profile tables
-- --
vdslLineMCMConfProfileTable OBJECT-TYPE vdslLineMCMConfProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains additional information on multiple "This table contains additional information on multiple
carrier VDSL lines. One entry in this table reflects a carrier VDSL lines. One entry in this table reflects a
profile defined by a manager which can be used to profile defined by a manager which can be used to
configure the VDSL line. configure the VDSL line.
The entries in this table MUST NOT be used for single If an entry in this table is referenced by a line which
carrier (SCM) VDSL lines." does not use MCM, it has no effect on the operation of that
line."
::= { vdslLineExtMCMMibObjects 1 } ::= { vdslLineExtMCMMibObjects 1 }
vdslLineMCMConfProfileEntry OBJECT-TYPE vdslLineMCMConfProfileEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileEntry SYNTAX VdslLineMCMConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a list of parameters that "Each entry consists of a list of parameters that
represents the configuration of a multiple carrier represents the configuration of a multiple carrier
modulation VDSL modem. modulation VDSL modem.
A default profile with an index of 'DEFVAL', will always A default profile with an index of 'DEFVAL', will always
skipping to change at page 8, line 15 skipping to change at page 8, line 23
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains transmit band descriptor configuration "This table contains transmit band descriptor configuration
information for a VDSL line. Each entry in this table information for a VDSL line. Each entry in this table
reflects the configuration for one of possibly many bands reflects the configuration for one of possibly many bands
with a multiple carrier modulation (MCM) VDSL line. with a multiple carrier modulation (MCM) VDSL line.
These entries are defined by a manager and can be used to These entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
The entries in this table MUST NOT be used for single If an entry in this table is referenced by a line which
carrier (SCM) VDSL lines." does not use MCM, it has no effect on the operation of that
line."
::= { vdslLineExtMCMMibObjects 2 } ::= { vdslLineExtMCMMibObjects 2 }
vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileTxBandEntry SYNTAX VdslLineMCMConfProfileTxBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit band descriptor, which "Each entry consists of a transmit band descriptor, which
is defined by a start and a stop tone index. is defined by a start and a stop tone index.
A default profile with an index of 'DEFVAL', will A default profile with an index of 'DEFVAL', will
skipping to change at page 9, line 27 skipping to change at page 9, line 36
vdslLineMCMConfProfileTxBandRowStatus OBJECT-TYPE vdslLineMCMConfProfileTxBandRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create a new row or modify or "This object is used to create a new row or modify or
delete an existing row in this table. delete an existing row in this table.
A profile activated by setting this object to `active'. A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile. When `active' is set, the system will validate the profile.
Each entry must be internally consistent, the Stop Tone must
be greater than the Start Tone. Each entry must also be
externally consistent, all entries indexed by a specific
profile must not overlap. Validation of the profile will
check both internal and external consistency.
Before a profile can be deleted or taken out of Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced `outOfService') it must be first unreferenced
from all associated lines." from all associated lines."
::= { vdslLineMCMConfProfileTxBandEntry 4 } ::= { vdslLineMCMConfProfileTxBandEntry 4 }
vdslLineMCMConfProfileRxBandTable OBJECT-TYPE vdslLineMCMConfProfileRxBandTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineMCMConfProfileRxBandEntry SYNTAX SEQUENCE OF VdslLineMCMConfProfileRxBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains receive band descriptor configuration "This table contains receive band descriptor configuration
information for a VDSL line. Each entry in this table information for a VDSL line. Each entry in this table
reflects the configuration for one of possibly many bands reflects the configuration for one of possibly many bands
with a multiple carrier modulation (MCM) VDSL line. with a multiple carrier modulation (MCM) VDSL line.
These entries are defined by a manager and can be used to These entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
The entries in this table MUST NOT be used for single If an entry in this table is referenced by a line which
carrier (SCM) VDSL lines." does not use MCM, it has no effect on the operation of that
line."
::= { vdslLineExtMCMMibObjects 3 } ::= { vdslLineExtMCMMibObjects 3 }
vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileRxBandEntry SYNTAX VdslLineMCMConfProfileRxBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit band descriptor, which "Each entry consists of a transmit band descriptor, which
is defined by a start and a stop tone index. is defined by a start and a stop tone index.
skipping to change at page 11, line 4 skipping to change at page 11, line 22
vdslLineMCMConfProfileRxBandRowStatus OBJECT-TYPE vdslLineMCMConfProfileRxBandRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create a new row or modify or "This object is used to create a new row or modify or
delete an existing row in this table. delete an existing row in this table.
A profile activated by setting this object to `active'. A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile. When `active' is set, the system will validate the profile.
Each entry must be internally consistent, the Stop Tone must
be greater than the Start Tone. Each entry must also be
externally consistent, all entries indexed by a specific
profile must not overlap. Validation of the profile will
check both internal and external consistency.
Before a profile can be deleted or taken out of Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced `outOfService') it must be first unreferenced
from all associated lines." from all associated lines."
::= { vdslLineMCMConfProfileRxBandEntry 4 } ::= { vdslLineMCMConfProfileRxBandEntry 4 }
vdslLineMCMConfProfileTxPSDTable OBJECT-TYPE vdslLineMCMConfProfileTxPSDTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxPSDEntry SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains transmit PSD mask descriptor "This table contains transmit PSD mask descriptor
configuration information for a VDSL line. Each entry in configuration information for a VDSL line. Each entry in
this table reflects the configuration for one tone within this table reflects the configuration for one tone within
a multiple carrier modulation (MCM) VDSL line. These a multiple carrier modulation (MCM) VDSL line. These
entries are defined by a manager and can be used to entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
The entries in this table MUST NOT be used for single If an entry in this table is referenced by a line which
carrier (SCM) VDSL lines." does not use MCM, it has no effect on the operation of that
line."
::= { vdslLineExtMCMMibObjects 4 } ::= { vdslLineExtMCMMibObjects 4 }
vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileTxPSDEntry SYNTAX VdslLineMCMConfProfileTxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit PSD mask descriptor, "Each entry consists of a transmit PSD mask descriptor,
which defines the power spectral density (PSD) for a tone. which defines the power spectral density (PSD) for a tone.
skipping to change at page 12, line 20 skipping to change at page 12, line 44
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tone index for which the PSD is being specified." "The tone index for which the PSD is being specified."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileTxPSDEntry 2 } ::= { vdslLineMCMConfProfileTxPSDEntry 2 }
vdslLineMCMConfProfileTxPSDPSD OBJECT-TYPE vdslLineMCMConfProfileTxPSDPSD OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "0.5dBm" UNITS "0.5dBm/Hz"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Power Spectral Density level in steps of 0.5dB with "Power Spectral Density level in steps of 0.5dBm/Hz with
an offset of -140dbm/Hz." an offset of -140dBm/Hz."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileTxPSDEntry 3 } ::= { vdslLineMCMConfProfileTxPSDEntry 3 }
vdslLineMCMConfProfileTxPSDRowStatus OBJECT-TYPE vdslLineMCMConfProfileTxPSDRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create a new row or modify or "This object is used to create a new row or modify or
delete an existing row in this table. delete an existing row in this table.
A profile activated by setting this object to `active'. A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile. When `active' is set, the system will validate the profile.
skipping to change at page 13, line 6 skipping to change at page 13, line 33
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains transmit maximum PSD mask descriptor "This table contains transmit maximum PSD mask descriptor
configuration information for a VDSL line. Each entry in configuration information for a VDSL line. Each entry in
this table reflects the configuration for one tone within this table reflects the configuration for one tone within
a multiple carrier modulation (MCM) VDSL modem. These a multiple carrier modulation (MCM) VDSL modem. These
entries are defined by a manager and can be used to entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
The entries in this table MUST NOT be used for single If an entry in this table is referenced by a line which
carrier (SCM) VDSL lines." does not use MCM, it has no effect on the operation of that
line."
::= { vdslLineExtMCMMibObjects 5 } ::= { vdslLineExtMCMMibObjects 5 }
vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit PSD mask descriptor, "Each entry consists of a transmit PSD mask descriptor,
which defines the maximum power spectral density (PSD) which defines the maximum power spectral density (PSD)
for a tone. for a tone.
skipping to change at page 13, line 49 skipping to change at page 14, line 26
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this band descriptor entry." "The index for this band descriptor entry."
::= { vdslLineMCMConfProfileMaxTxPSDEntry 1 } ::= { vdslLineMCMConfProfileMaxTxPSDEntry 1 }
vdslLineMCMConfProfileMaxTxPSDTone OBJECT-TYPE vdslLineMCMConfProfileMaxTxPSDTone OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tone index for which the PSD is being specified." "The tone index for which the PSD is being specified.
There must not be multiple rows defined, for a particular
profile, with the same value for this field."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileMaxTxPSDEntry 2 } ::= { vdslLineMCMConfProfileMaxTxPSDEntry 2 }
vdslLineMCMConfProfileMaxTxPSDPSD OBJECT-TYPE vdslLineMCMConfProfileMaxTxPSDPSD OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "0.5dBm" UNITS "0.5dBm/Hz"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Power Spectral Density level in steps of 0.5dB with "Power Spectral Density level in steps of 0.5dBm/Hz with
an offset of -140dbm/Hz." an offset of -140dBm/Hz."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileMaxTxPSDEntry 3 } ::= { vdslLineMCMConfProfileMaxTxPSDEntry 3 }
vdslLineMCMConfProfileMaxTxPSDRowStatus OBJECT-TYPE vdslLineMCMConfProfileMaxTxPSDRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create a new row or modify or "This object is used to create a new row or modify or
delete an existing row in this table. delete an existing row in this table.
A profile activated by setting this object to `active'. A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile. When `active' is set, the system will validate the profile.
There must be only one entry in this table for each tone
associated with a specific profile. This will be checked
during the validation process.
Before a profile can be deleted or taken out of Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced `outOfService') it must be first unreferenced
from all associated lines." from all associated lines."
::= { vdslLineMCMConfProfileMaxTxPSDEntry 4 } ::= { vdslLineMCMConfProfileMaxTxPSDEntry 4 }
vdslLineMCMConfProfileMaxRxPSDTable OBJECT-TYPE vdslLineMCMConfProfileMaxRxPSDTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxRxPSDEntry SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxRxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains maximum receive PSD mask descriptor "This table contains maximum receive PSD mask descriptor
configuration information for a VDSL line. Each entry in configuration information for a VDSL line. Each entry in
this table reflects the configuration for one tone within this table reflects the configuration for one tone within
a multiple carrier modulation (MCM) VDSL modem. These a multiple carrier modulation (MCM) VDSL modem. These
entries are defined by a manager and can be used to entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
The entries in this table MUST NOT be used for single If an entry in this table is referenced by a line which
carrier (SCM) VDSL lines." does not use MCM, it has no effect on the operation of that
line."
::= { vdslLineExtMCMMibObjects 6 } ::= { vdslLineExtMCMMibObjects 6 }
vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit PSD mask descriptor, "Each entry consists of a transmit PSD mask descriptor,
which defines the power spectral density (PSD) for a which defines the power spectral density (PSD) for a
tone. tone.
skipping to change at page 15, line 32 skipping to change at page 16, line 17
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this band descriptor entry." "The index for this band descriptor entry."
::= { vdslLineMCMConfProfileMaxRxPSDEntry 1 } ::= { vdslLineMCMConfProfileMaxRxPSDEntry 1 }
vdslLineMCMConfProfileMaxRxPSDTone OBJECT-TYPE vdslLineMCMConfProfileMaxRxPSDTone OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tone index for which the PSD is being specified." "The tone index for which the PSD is being specified.
There must not be multiple rows defined, for a particular
profile, with the same value for this field."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileMaxRxPSDEntry 2 } ::= { vdslLineMCMConfProfileMaxRxPSDEntry 2 }
vdslLineMCMConfProfileMaxRxPSDPSD OBJECT-TYPE vdslLineMCMConfProfileMaxRxPSDPSD OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "0.5dBm" UNITS "0.5dBm/Hz"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Power Spectral Density level in steps of 0.5dB with "Power Spectral Density level in steps of 0.5dBm/Hz with
an offset of -140dbm/Hz." an offset of -140dBm/Hz."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileMaxRxPSDEntry 3 } ::= { vdslLineMCMConfProfileMaxRxPSDEntry 3 }
vdslLineMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE vdslLineMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create a new row or modify or "This object is used to create a new row or modify or
delete an existing row in this table. delete an existing row in this table.
skipping to change at page 16, line 4 skipping to change at page 16, line 43
vdslLineMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE vdslLineMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create a new row or modify or "This object is used to create a new row or modify or
delete an existing row in this table. delete an existing row in this table.
A profile activated by setting this object to `active'. A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile. When `active' is set, the system will validate the profile.
There must be only one entry in this table for each tone
associated with a specific profile. This will be checked
during the validation process.
Before a profile can be deleted or taken out of Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced `outOfService') it must be first unreferenced
from all associated lines." from all associated lines."
::= { vdslLineMCMConfProfileMaxRxPSDEntry 4 } ::= { vdslLineMCMConfProfileMaxRxPSDEntry 4 }
-- conformance information -- conformance information
vdslLineExtMCMConformance OBJECT IDENTIFIER ::= vdslLineExtMCMConformance OBJECT IDENTIFIER ::=
{ vdslLineExtMCMMib 2 } { vdslLineExtMCMMib 2 }
vdslLineExtMCMGroups OBJECT IDENTIFIER ::= vdslLineExtMCMGroups OBJECT IDENTIFIER ::=
{ vdslLineExtMCMConformance 1 } { vdslLineExtMCMConformance 1 }
vdslLineExtMCMCompliances OBJECT IDENTIFIER ::= vdslLineExtMCMCompliances OBJECT IDENTIFIER ::=
{ vdslLineExtMCMConformance 2 } { vdslLineExtMCMConformance 2 }
vdslLineExtMCMMibCompliance MODULE-COMPLIANCE vdslLineExtMCMMibCompliance MODULE-COMPLIANCE
skipping to change at page 17, line 11 skipping to change at page 17, line 53
vdslLineMCMConfProfileMaxTxPSDRowStatus, vdslLineMCMConfProfileMaxTxPSDRowStatus,
vdslLineMCMConfProfileMaxRxPSDTone, vdslLineMCMConfProfileMaxRxPSDTone,
vdslLineMCMConfProfileMaxRxPSDPSD, vdslLineMCMConfProfileMaxRxPSDPSD,
vdslLineMCMConfProfileMaxRxPSDRowStatus vdslLineMCMConfProfileMaxRxPSDRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration
information for a VDSL line based upon multiple information for a VDSL line based upon multiple
carrier modulation modem." carrier modulation modem."
::= { vdslLineExtMCMGroup 1 } ::= { vdslLineExtMCMGroups 1 }
END END
5. Security Considerations 5. Acknowledgments
This document contains many definitions taken from
draft-ietf-adslmib-vdsl-07.txt. As such, any credit for the text
found within should be fully attributed to the authors of that
document.
6. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-create. Such objects may be with a MAX-ACCESS clause of read-create. Such objects may be
considered sensitive or vulnerable in some network environments. considered sensitive or vulnerable in some network environments.
The support for SET operations in a non-secure environment without The support for SET operations in a non-secure environment without
proper protection can have a negative effect on network operations. proper protection can have a negative effect on network operations.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. vulnerable in some network environments.
skipping to change at page 18, line 14 skipping to change at page 19, line 11
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of a MIB module which utilizes the textual conventions
defined in this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
6. References 7. References
6.1. Normative References 7.1. Normative References
[DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management", [DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management",
February 2003. February 2003.
[ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing [ETSI2701] ETSI TS 101 270-1 V1.2.1, "Transmission and Multiplexing
(TM); Access transmission systems on metallic access (TM); Access transmission systems on metallic access
cables; Very high speed Digital Subscriber Line (VDSL); cables; Very high speed Digital Subscriber Line (VDSL);
Part 1: Functional requirements", October 1999. Part 1: Functional requirements", October 1999.
[ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing [ETSI2702] ETSI TS 101 270-2 V1.1.1, "Transmission and Multiplexing
(TM); Access transmission systems on metallic access (TM); Access transmission systems on metallic access
cables; Very high speed Digital Subscriber Line (VDSL); cables; Very high speed Digital Subscriber Line (VDSL);
Part 1: Transceiver specification", February 2001. Part 1: Transceiver specification", February 2001.
[ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line [ITU9931] ITU-T G.993.1, "Very-high-speed digital subscriber line
foundation", November 2001. foundation", November 2001.
[ITU9971] ITU-T G.997.1 "Physical layer management for Digital [ITU9971] ITU-T G.997.1, "Physical layer management for Digital
Subscriber Line (DSL) Transceivers", July 1999. Subscriber Line (DSL) Transceivers", July 1999.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Structure of J., Rose, M. and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999. 2578, April 1999.
skipping to change at page 19, line 20 skipping to change at page 20, line 20
Group MIB", RFC 2863, June 2000. Group MIB", RFC 2863, June 2000.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, RFC Simple Network Management Protocol (SNMP)", STD 62, RFC
3418, December 2002. 3418, December 2002.
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC Performance History Based on 15 Minute Intervals", RFC
3593, September 2003. 3593, September 2003.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", RFC 3411, Protocol (SNMP) Management Frameworks", RFC 3411,
December 2002. December 2002.
[RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for [RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for
Very High Speed Digital Subscriber Lines (VDSL)", RFC Very High Speed Digital Subscriber Lines (VDSL)", RFC
3728, February 2004. 3728, February 2004.
[T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital
Subscriber Line (VDSL) Metallic Interface, Part 1: Subscriber Line (VDSL) Metallic Interface, Part 1:
skipping to change at page 19, line 42 skipping to change at page 20, line 42
February 2001. February 2001.
[T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part
2: Technical Specification for a Single-Carrier 2: Technical Specification for a Single-Carrier
Modulation (SCM) Transceiver", November 2001. Modulation (SCM) Transceiver", November 2001.
[T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part
3: Technical Specification for a Multi-Carrier 3: Technical Specification for a Multi-Carrier
Modulation (MCM) Transceiver", November 2000. Modulation (MCM) Transceiver", November 2000.
6.2. Informative References 7.2. Informative References
[RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999. Management Protocol (SNMP)", RFC 3415, December 2002.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
7. Acknowledgments
This document contains many definitions taken from
draft-ietf-adslmib-vdsl-07.txt. As such, any credit for the text
found within should be fully attributed to the authors of that
document.
8. Authors' Addresses 8. Authors' Addresses
Menachem Dodge Menachem Dodge
Infineon Technologies Savan Ltd. Infineon Technologies Savan Ltd.
6 Hagavish St. 6 Hagavish St.
Poleg Industrial Area, Poleg Industrial Area,
Netanya 42504, Netanya 42504,
Israel Israel
Phone: +972 9 892 4116 Phone: +972 9 892 4116
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/