draft-ietf-adslmib-vdsl-ext-mcm-06.txt   rfc4070.txt 
Network Working Group M. Dodge Network Working Group M. Dodge
Category: Internet Draft ECI Telecom Request for Comments: 4070 ECI Telecom
B. Ray Category: Standards Track B. Ray
PESA Switching Systems PESA Switching Systems
January 2005 May 2005
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-06.txt
Status of this Memo
This document is an Internet-Draft and is subject to all provisions Status of This Memo
of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of
which he or she becomes aware will be disclosed, in accordance with
RFC 3668.
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: This document specifies an Internet standards track protocol for the
http://www.ietf.org/shadow.html. 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 Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2005).
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
Digital Subscriber Line (VDSL) interfaces using Multiple Carrier Subscriber Line (VDSL) interfaces using Multiple Carrier Modulation
Modulation (MCM) Line Coding. It is an optional extension to the (MCM) Line Coding. It is an optional extension to the VDSL-LINE-MIB,
VDSL-LINE-MIB, RFC 3728, which handles line code independent RFC 3728, which handles line code independent objects.
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 .......... 3 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 .................................... 4 3. Conformance and Compliance ......................................5
4. Definitions ................................................... 5 4. Definitions .....................................................5
5. Acknowledgements .............................................. 18 5. Acknowledgments ................................................19
6. Security Considerations ....................................... 18 6. Security Considerations ........................................19
7. IANA Considerations ............................................ 20 7. IANA Considerations ............................................21
8. References ..................................................... 20 8. References .....................................................21
8.1 Normative References ........................................... 20 8.1. Normative References ......................................21
8.2 Informative References ......................................... 21 8.2. Informative References ....................................23
Authors' Addresses ............................................. 21
Full Copyright Statement ....................................... 22
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
MIB module that is compliant to the SMIv2, which is described in STD module that is compliant to the SMIv2, which is described in STD 58,
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
2580 [RFC2580]. [RFC2580].
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
Code Dependent, Physical Medium Dependent (PMD), Layer of MCM VDSL Dependent, Physical Medium Dependent (PMD), Layer of MCM VDSL Lines.
Lines. These definitions are based upon the specifications for VDSL These definitions are based upon the specifications for VDSL as
as defined in T1E1, European Telecommunications Standards Institute defined in T1E1, European Telecommunications Standards Institute
(ETSI), and International Telecommunication Union (ITU) documentation (ETSI), and International Telecommunication Union (ITU) documentation
[T1E1311, T1E1011, T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. [T1E1311, T1E1011, T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971].
Additionally the protocol-dependent (and line-code dependent) Additionally the protocol-dependent (and line-code dependent)
management framework for VDSL lines specified by the Digital management framework for VDSL lines specified by the Digital
Subscriber Line Forum (DSLF) has been taken into consideration Subscriber Line Forum (DSLF) has been taken into consideration
[DSLFTR57]. [DSLFTR57].
The MIB module is located in the MIB tree under MIB-2 transmission. The MIB module is located in the MIB tree under MIB-2 transmission.
The key words "MUST", "MUST NOT", "RECOMMENDED", and "SHOULD" in this The key words "MUST", "MUST NOT", "RECOMMENDED", and "SHOULD" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
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 module to other MIB modules The relationship of the VDSL Line MIB module to other MIB modules and
and in particular to the IF-MIB, as presented in RFC 2863 [RFC2863], in particular to the IF-MIB, as presented in RFC 2863 [RFC2863], is
is discussed in the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section discussed in the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section
outlines the relationship of this VDSL Line Extension MIB to the outlines the relationship of this VDSL Line Extension MIB to the
VDSL-LINE-MIB, 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
F. Max -- Maximum F. Max -- Maximum
G. PSD -- Power Spectral Density G. PSD -- Power Spectral Density
H. Rx -- Receive H. Rx -- Receive
I. Tx -- Transmit I. Tx -- Transmit
2.3 Structure 2.3. Structure
The MCM VDSL Line Extension MIB contains the following MIB group: The MCM VDSL Line Extension MIB contains the following MIB group:
o vdslMCMGroup : o vdslMCMGroup :
This group supports MIB objects for defining configuration profiles This group supports MIB objects for defining configuration profiles
and for monitoring individual bands of Multiple Carrier Modulation and for monitoring individual bands of Multiple Carrier Modulation
(MCM) VDSL modems. It contains the following tables: (MCM) VDSL modems. It contains the following tables:
- vdslLineMCMConfProfileTable - vdslLineMCMConfProfileTable
skipping to change at page 4, line 14 skipping to change at page 4, line 22
vdslLineConfProfileEntry(vdslLineConfProfileName) vdslLineConfProfileEntry(vdslLineConfProfileName)
----> vdslLineMCMConfProfileTable 1:(0..1) ----> vdslLineMCMConfProfileTable 1:(0..1)
----> vdslLineMCMConfProfileTxBandTable 1:(0..n) ----> vdslLineMCMConfProfileTxBandTable 1:(0..n)
----> vdslLineMCMConfProfileRxBandTable 1:(0..n) ----> vdslLineMCMConfProfileRxBandTable 1:(0..n)
----> vdslLineMCMConfProfileTxPSDTable 1:(0..n) ----> vdslLineMCMConfProfileTxPSDTable 1:(0..n)
----> vdslLineMCMConfProfileMaxTxPSDTable 1:(0..n) ----> vdslLineMCMConfProfileMaxTxPSDTable 1:(0..n)
----> vdslLineMCMConfProfileMaxRxPSDTable 1:(0..n) ----> 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
vdslLineConfProfileName is used as the index to each of the six is used as the index to each of the six vdslLineMCMConfProfile
vdslLineMCMConfProfile Tables. The existence of an entry in Tables. The existence of an entry in any of the tables of the
any of the tables of the vdslMCMGroup is optional. vdslMCMGroup is optional.
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
vdslMCMConfProfileTxBandStart vdslMCMConfProfileTxBandStart
vdslMCMConfProfileTxBandStop vdslMCMConfProfileTxBandStop
skipping to change at page 4, line 43 skipping to change at page 5, line 4
vdslMCMConfProfileRxBandRowStatus vdslMCMConfProfileRxBandRowStatus
vdslMCMConfProfileTxPSDTone vdslMCMConfProfileTxPSDTone
vdslMCMConfProfileTxPSDPSD vdslMCMConfProfileTxPSDPSD
vdslMCMConfProfileTxPSDRowStatus vdslMCMConfProfileTxPSDRowStatus
vdslMCMConfProfileMaxTxPSDTone vdslMCMConfProfileMaxTxPSDTone
vdslMCMConfProfileMaxTxPSDPSD vdslMCMConfProfileMaxTxPSDPSD
vdslMCMConfProfileMaxTxPSDRowStatus vdslMCMConfProfileMaxTxPSDRowStatus
vdslMCMConfProfileMaxRxPSDTone vdslMCMConfProfileMaxRxPSDTone
vdslMCMConfProfileMaxRxPSDPSD vdslMCMConfProfileMaxRxPSDPSD
vdslMCMConfProfileMaxRxPSDRowStatus vdslMCMConfProfileMaxRxPSDRowStatus
Note also that the interface indices in this MIB are maintained Note also that the interface indices in this MIB are maintained
persistently. View-based Access Control Model (VACM) data persistently. View-based Access Control Model (VACM) data relating
relating to these SHOULD be stored persistently as well [RFC3415]. to these SHOULD be stored persistently as well [RFC3415].
3. Conformance and Compliance 3. Conformance and Compliance
An MCM based VDSL agent does not have to implement this MIB to be 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 compliant with RFC 3728 [RFC3728]. If the MCM VDSL Line Extension
MIB is implemented then the following group is mandatory: MIB is implemented then the following group is mandatory:
- vdslMCMGroup - vdslMCMGroup
4. Definitions 4. Definitions
skipping to change at page 5, line 17 skipping to change at page 5, line 28
VDSL-LINE-EXT-MCM-MIB DEFINITIONS ::= BEGIN VDSL-LINE-EXT-MCM-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
transmission, transmission,
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]
ifIndex FROM IF-MIB -- [RFC2863]
vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728] vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728]
vdslExtMCMMIB MODULE-IDENTITY vdslExtMCMMIB MODULE-IDENTITY
LAST-UPDATED "200501160000Z" -- January 16, 2005 LAST-UPDATED "200504280000Z" -- April 28, 2005
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
Co-Chair: Bob Ray Co-Chair/Co-editor:
Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
Postal: 330-A Wynn Drive Postal: 330-A Wynn Drive
Huntsville, AL 35805 Huntsville, AL 35805
USA USA
Email: rray@pesa.com Email: rray@pesa.com
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Co-editor: Menachem Dodge Co-editor: Menachem Dodge
ECI Telecom Ltd. ECI Telecom Ltd.
Postal: 30 hasivim St. Postal: 30 hasivim St.
Petach Tikva 49517, Petach Tikva 49517,
Israel. Israel.
Email: mbdodge@ieee.org Email: mbdodge@ieee.org
Phone: +972 3 926 8421 Phone: +972 3 926 8421
Co-editor: Bob Ray
PESA Switching Systems, Inc.
Postal: 330-A Wynn Drive
Huntsville, AL 35805
USA
Email: rray@pesa.com
Phone: +1 256 726 9200 ext. 142
" "
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 Single Carrier Modulation (SCM) be used for VDSL lines using Single Carrier Modulation (SCM)
skipping to change at page 6, line 30 skipping to change at page 6, line 39
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 (2005). This version Copyright (C) The Internet Society (2005). This version
of this MIB module is part of RFC XXXX: see the RFC of this MIB module is part of RFC 4070: see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200501160000Z" -- January 16, 2005 REVISION "200504280000Z" -- April 28, 2005
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC 4070."
::= { transmission XX } -- To be assigned by IANA ::= { transmission 229 }
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.
skipping to change at page 8, line 10 skipping to change at page 8, line 20
delete an existing row in this table. delete an existing row in this table.
A profile is activated by setting this object to `active'. A profile is 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.
None of the columns in this row may be modified while the None of the columns in this row may be modified while the
row is in the 'active' state. row is in the 'active' state.
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
`notInService') it must be first unreferenced `notInService') it must first be unreferenced
from all associated lines." from all associated lines."
::= { vdslLineMCMConfProfileEntry 2 } ::= { vdslLineMCMConfProfileEntry 2 }
vdslLineMCMConfProfileTxBandTable OBJECT-TYPE vdslLineMCMConfProfileTxBandTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxBandEntry SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxBandEntry
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
skipping to change at page 9, line 34 skipping to change at page 9, line 49
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileTxBandEntry 3 } ::= { vdslLineMCMConfProfileTxBandEntry 3 }
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 is 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 Each entry must be internally consistent, the Stop Tone must
be greater than the Start Tone. Each entry must also be be greater than the Start Tone. Each entry must also be
externally consistent, all entries indexed by a specific externally consistent, all entries indexed by a specific
profile must not overlap. Validation of the profile will profile must not overlap. Validation of the profile will
check both internal and external consistency. check both internal and external consistency.
None of the columns in this row may be modified while the None of the columns in this row may be modified while the
row is in the 'active' state. row is in the 'active' state.
skipping to change at page 11, line 26 skipping to change at page 11, line 46
::= { vdslLineMCMConfProfileRxBandEntry 3 } ::= { vdslLineMCMConfProfileRxBandEntry 3 }
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 is 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 Each entry must be internally consistent, the Stop Tone must
be greater than the Start Tone. Each entry must also be be greater than the Start Tone. Each entry must also be
externally consistent, all entries indexed by a specific externally consistent, all entries indexed by a specific
profile must not overlap. Validation of the profile will profile must not overlap. Validation of the profile will
check both internal and external consistency. check both internal and external consistency.
None of the columns in this row may be modified while the None of the columns in this row may be modified while the
row is in the 'active' state. row is in the 'active' state.
skipping to change at page 13, line 17 skipping to change at page 13, line 45
::= { 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 is 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.
None of the columns in this row may be modified while the None of the columns in this row may be modified while the
row is in the 'active' state. row is in the 'active' state.
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
`notInService') it must be first unreferenced `notInService') it must be first unreferenced
from all associated lines." from all associated lines."
::= { vdslLineMCMConfProfileTxPSDEntry 4 } ::= { vdslLineMCMConfProfileTxPSDEntry 4 }
skipping to change at page 15, line 4 skipping to change at page 15, line 39
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 is 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 There must be only one entry in this table for each tone
associated with a specific profile. This will be checked associated with a specific profile. This will be checked
during the validation process. during the validation process.
None of the columns in this row may be modified while the None of the columns in this row may be modified while the
row is in the 'active' state. row is in the 'active' state.
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
skipping to change at page 16, line 51 skipping to change at page 17, line 38
::= { 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.
A profile activated by setting this object to `active'. A profile is 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 There must be only one entry in this table for each tone
associated with a specific profile. This will be checked associated with a specific profile. This will be checked
during the validation process. during the validation process.
None of the columns in this row may be modified while the None of the columns in this row may be modified while the
row is in the 'active' state. row is in the 'active' state.
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
skipping to change at page 18, line 19 skipping to change at page 19, line 12
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."
::= { vdslLineExtMCMGroups 1 } ::= { vdslLineExtMCMGroups 1 }
END END
5. Acknowledgments 5. Acknowledgments
This document contains many definitions taken from an earlier This document contains many definitions taken from an early version
draft of the VDSL MIB [RFC3728]. As such any credit for the text of the VDSL MIB [RFC3728]. As such any credit for the text found
found within should be fully attributed to the authors of that within should be fully attributed to the authors of that document.
document.
6. Security Considerations 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
The support for SET operations in a non-secure environment without support for SET operations in a non-secure environment without proper
proper protection can have a negative effect on network operations. protection can have a negative effect on network operations. These
These are the tables and objects and their sensitivity/vulnerability: are the tables and objects and their sensitivity/vulnerability:
vdslLineMCMConfProfileTable, vdslLineMCMConfProfileTable,
vdslLineMCMConfProfileTxWindowLength, vdslLineMCMConfProfileTxWindowLength,
vdslLineMCMConfProfileRowStatus, vdslLineMCMConfProfileRowStatus,
vdslLineMCMConfProfileTxBandTable, vdslLineMCMConfProfileTxBandTable,
vdslLineMCMConfProfileTxBandStart, vdslLineMCMConfProfileTxBandStart,
vdslLineMCMConfProfileTxBandStop, vdslLineMCMConfProfileTxBandStop,
vdslLineMCMConfProfileTxBandRowStatus, vdslLineMCMConfProfileTxBandRowStatus,
vdslLineMCMConfProfileRxBandTable, vdslLineMCMConfProfileRxBandTable,
vdslLineMCMConfProfileRxBandStart, vdslLineMCMConfProfileRxBandStart,
skipping to change at page 19, line 12 skipping to change at page 20, line 12
vdslLineMCMConfProfileMaxRxPSDPSD, vdslLineMCMConfProfileMaxRxPSDPSD,
vdslLineMCMConfProfileMaxRxPSDRowStatus vdslLineMCMConfProfileMaxRxPSDRowStatus
VDSL layer connectivity from the Vtur will permit the subscriber to VDSL layer connectivity from the Vtur will permit the subscriber to
manipulate both the VDSL link directly and the VDSL embedded manipulate both the VDSL link directly and the VDSL embedded
operations channel (EOC) for their own loop. For example, unchecked operations channel (EOC) for their own loop. For example, unchecked
or unfiltered fluctuations initiated by the subscriber could generate or unfiltered fluctuations initiated by the subscriber could generate
sufficient notifications to potentially overwhelm either the sufficient notifications to potentially overwhelm either the
management interface to the network or the element manager. management interface to the network or the element manager.
Additionally, allowing write access to configuration data may allow Additionally, allowing write access to configuration data may allow
an end-user to increase their service levels or affect other an end-user to increase their service levels or affect other end-
end-users in either a positive or negative manner. For this reason, users in either a positive or negative manner. For this reason, the
the tables and objects listed above should be considered to contain tables and objects listed above should be considered to contain
sensitive information. sensitive information.
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. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
skipping to change at page 19, line 48 skipping to change at page 21, line 4
vdslLineMCMConfProfileTxPSDPSD, vdslLineMCMConfProfileTxPSDPSD,
vdslLineMCMConfProfileTxPSDRowStatus, vdslLineMCMConfProfileTxPSDRowStatus,
vdslLineMCMConfProfileMaxTxPSDTable vdslLineMCMConfProfileMaxTxPSDTable
vdslLineMCMConfProfileMaxTxPSDTone, vdslLineMCMConfProfileMaxTxPSDTone,
vdslLineMCMConfProfileMaxTxPSDPSD, vdslLineMCMConfProfileMaxTxPSDPSD,
vdslLineMCMConfProfileMaxTxPSDRowStatus, vdslLineMCMConfProfileMaxTxPSDRowStatus,
vdslLineMCMConfProfileMaxRxPSDTable vdslLineMCMConfProfileMaxRxPSDTable
vdslLineMCMConfProfileMaxRxPSDTone, vdslLineMCMConfProfileMaxRxPSDTone,
vdslLineMCMConfProfileMaxRxPSDPSD, vdslLineMCMConfProfileMaxRxPSDPSD,
vdslLineMCMConfProfileMaxRxPSDRowStatus vdslLineMCMConfProfileMaxRxPSDRowStatus
Read access of the physical band parameters may provide knowledge to
Read access of the physical band parameters may provide knowledge an end-user that would allow malicious behavior, for example the
to an end-user that would allow malicious behavior, for example application of an intentional interference on one or all of the
the application of an intentional interference on one or all of physical bands in use.
the physical bands in use.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), 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 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 allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
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
skipping to change at page 20, line 26 skipping to change at page 21, line 30
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 a MIB module which utilizes the textual conventions instance of a MIB module which utilizes the textual conventions
defined in this MIB module is properly configured to give access to 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.
7. IANA Considerations 7. IANA Considerations
The IANA is kindly requested to assign the value of the
MODULE-IDENTITY. The authors suggest transmission 228, The IANA has assigned the transmission value 229 to VDSL-LINE-EXT-
see section 4. MCM-MIB.
8. References 8. References
8.1. Normative References 8.1. Normative References
[DSLFTR57] DSL Forum TR-057, "VDSL Network Element Management", [DSLFTR57] 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
skipping to change at page 21, line 5 skipping to change at page 22, line 14
[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., and J. Schoenwaelder,
J., Rose, M. and S. Waldbusser, "Structure of "Structure of Management Information Version 2 (SMIv2)",
Management Information Version 2 (SMIv2)", STD 58, RFC STD 58, RFC 2578, April 1999.
2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M. and S. Waldbusser, "Textual Conventions "Textual Conventions for SMIv2", STD 58, RFC 2579, April
for SMIv2", STD 58, RFC 2579, April 1999. 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M. and S. Waldbusser, "Conformance "Conformance Statements for SMIv2", STD 58, RFC 2580,
Statements for SMIv2", STD 58, RFC 2580, April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
Group MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[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:
Functional Requirements and Common Specification", Functional Requirements and Common Specification",
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:
2: Technical Specification for a Single-Carrier Technical Specification for a Single-Carrier Modulation
Modulation (SCM) Transceiver", November 2001. (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:
3: Technical Specification for a Multi-Carrier Technical Specification for a Multi-Carrier Modulation
Modulation (MCM) Transceiver", November 2000. (MCM) Transceiver", November 2000.
8.2. Informative References 8.2. Informative References
[RFC3415] 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 3415, December 2002. Management Protocol (SNMP)", STD 62, 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 "Introduction and Applicability Statements for Internet-
Internet-Standard Management Framework", RFC 3410, Standard Management Framework", RFC 3410, December 2002.
December 2002.
Authors' Addresses Authors' Addresses
Menachem Dodge Menachem Dodge
ECI Telecom Ltd. ECI Telecom Ltd.
30 Hasivim St. 30 Hasivim St.
Petach Tikva 49517, Petach Tikva 49517,
Israel. Israel
Phone: +972 3 926 8421 Phone: +972 3 926 8421
Fax: +972 3 928 7342 Fax: +972 3 928 7342
Email: mbdodge@ieee.org EMail: mbdodge@ieee.org
Bob Ray Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
330-A Wynn Drive 330-A Wynn Drive
Huntsville, AL 35805 Huntsville, AL 35805
USA USA
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Fax: +1 256 726 9271 Fax: +1 256 726 9271
EMail: rray@pesa.com EMail: rray@pesa.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2005).
to the rights, licenses and restrictions contained in BCP 78 and
except as set forth therein, the authors retain all their rights. This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
skipping to change at page 22, line 46 skipping to change at page 24, line 34
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use attempt made to obtain a general license or permission for the use of
of such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository specification can be obtained from the IETF on-line IPR repository at
at http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
 End of changes. 

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