draft-ietf-adslmib-vdsl-ext-mcm-04.txt   draft-ietf-adslmib-vdsl-ext-mcm-05.txt 
Network Working Group M. Dodge Network Working Group M. Dodge
Category: Internet Draft Infineon Technologies Category: Internet Draft ECI Telecom
B. Ray B. Ray
PESA Switching Systems PESA Switching Systems
May 2004 December 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-04.txt draft-ietf-adslmib-vdsl-ext-mcm-05.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 subject to all provisions
all provisions of Section 10 of RFC2026. 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 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.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
skipping to change at page 1, line 38 skipping to change at page 1, line 43
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, which handles line code independent
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 .................................... 5 3. Conformance and Compliance .................................... 4
4. Definitions ................................................... 5 4. Definitions ................................................... 5
5. Acknowledgements .............................................. 18 5. Acknowledgements .............................................. 18
6. Security Considerations ....................................... 18 6. Security Considerations ....................................... 18
7. References .................................................... 19 7. IANA Considerations ............................................ 19
7.1 Normative References .......................................... 19 8. References ..................................................... 19
7.2 Informative References ........................................ 20 8.1 Normative References ........................................... 19
Authors' Addresses ............................................ 21 8.2 Informative References ......................................... 21
Full Copyright Statement ...................................... 21 Authors' Addresses ............................................. 21
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 (PMD), Layer of MCM VDSL Code Dependent, Physical Medium Dependent (PMD), Layer of MCM VDSL
Lines. These definitions are based upon the specifications for VDSL Lines. These definitions are based upon the specifications for VDSL
as defined in T1E1, European Telecommunications Standards Institute as 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
[DSLFTR057]. [DSLFTR57].
The MIB module is located in the MIB tree under the vdslMIB, which The MIB module is located in the MIB tree under MIB-2 transmission.
in turn is found under MIB 2 transmission. The reader is referred to
RFC 3728 [RFC3728] for further discussion of this subject. The key words "MUST", "MUST NOT", "RECOMMENDED", and "SHOULD" in this
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 in particular to the IF-MIB, as presented in RFC 2863 [RFC2863], and in particular to the IF-MIB, as presented in RFC 2863 [RFC2863],
is discussed in the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section is 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
skipping to change at page 3, line 35 skipping to change at page 3, line 34
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 montioring 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
- vdslLineMCMConfProfileTxBandTable - vdslLineMCMConfProfileTxBandTable
- vdslLineMCMConfProfileRxBandTable - vdslLineMCMConfProfileRxBandTable
- vdslLineMCMConfProfileTxPSDTable - vdslLineMCMConfProfileTxPSDTable
- vdslLineMCMConfProfileMaxTxPSDTable - vdslLineMCMConfProfileMaxTxPSDTable
- vdslLineMCMConfProfileMaxRxPSDTable - vdslLineMCMConfProfileMaxRxPSDTable
If the MCM VDSL Line Extension MIB is implemented then all of the If the MCM VDSL Line Extension MIB is implemented then all of the
skipping to change at page 4, line 20 skipping to change at page 4, line 15
----> 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 is used as the index to vdslLineConfProfileName is used as the index to each of the six
vdslLineMCMConfProfileTxBandTable. The existence of an entry in vdslLineMCMConfProfile Tables. The existence of an entry in
any of the tables of the vdslMCMGroup is optional. any of the tables of the 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
skipping to change at page 5, line 18 skipping to change at page 5, line 10
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
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,
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, 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 "200405300000Z" -- May 30, 2004 LAST-UPDATED "200412160000Z" -- December 16, 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
Co-Chair: 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
Co-editor: Menachem Dodge Co-editor: Menachem Dodge
Infineon Technologies Savan Ltd. ECI Telecom Ltd.
6 Hagavish St. Postal: 30 hasivim St.
Postal: Poleg Industrial Area, Petach Tikva 49517,
Netanya 42504,
Israel. Israel.
Email: menachem.dodge@infineon.com Email: mbdodge@ieee.org
Phone: +972 9 892 4116 Phone: +972 3 926 8421
Co-editor: Bob Ray 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
" "
DESCRIPTION DESCRIPTION
skipping to change at page 6, line 33 skipping to change at page 6, line 33
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 "200405300000Z" -- May 30, 2004 REVISION "200412160000Z" -- December 16, 2004
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
::= { vdslMIB XX } -- To be assigned by IANA -- RFC Ed.: replace XX with assigned number & remove this note
::= { transmission XX } -- To be assigned by IANA
-- RFC Ed.: we suggest to put it under { transmission 228 } because
-- this is the next available number, transmission 227
-- would be used for the SCM 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.
If an entry in this table is referenced by a line which If an entry in this table is referenced by a line which
does not use MCM, it has no effect on the operation of that does not use MCM, it has no effect on the operation of that
line." line.
All read-create objects defined in this MIB module SHOULD be
stored persistently."
::= { 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
exist and its parameters will be set to vendor specific
values, unless otherwise specified in this document."
INDEX { vdslLineConfProfileName } INDEX { vdslLineConfProfileName }
::= { vdslLineMCMConfProfileTable 1 } ::= { vdslLineMCMConfProfileTable 1 }
VdslLineMCMConfProfileEntry ::= VdslLineMCMConfProfileEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineMCMConfProfileTxWindowLength Unsigned32, vdslLineMCMConfProfileTxWindowLength Unsigned32,
vdslLineMCMConfProfileRowStatus RowStatus vdslLineMCMConfProfileRowStatus RowStatus
} }
skipping to change at page 7, line 53 skipping to change at page 7, line 53
::= { vdslLineMCMConfProfileEntry 1 } ::= { vdslLineMCMConfProfileEntry 1 }
vdslLineMCMConfProfileRowStatus OBJECT-TYPE vdslLineMCMConfProfileRowStatus 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
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
`outOfService') it must be first unreferenced `notInService') it must be first 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
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.
If an entry in this table is referenced by a line which If an entry in this table is referenced by a line which
does not use MCM, it has no effect on the operation of that does not use MCM, it has no effect on the operation of that
line." line.
All read-create objects defined in this MIB module SHOULD be
stored persistently."
::= { 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
always exist and its parameters will be set to vendor
specific values, unless otherwise specified in this
document."
INDEX { vdslLineConfProfileName, INDEX { vdslLineConfProfileName,
vdslLineMCMConfProfileTxBandNumber } vdslLineMCMConfProfileTxBandNumber }
::= { vdslLineMCMConfProfileTxBandTable 1 } ::= { vdslLineMCMConfProfileTxBandTable 1 }
VdslLineMCMConfProfileTxBandEntry ::= VdslLineMCMConfProfileTxBandEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineMCMConfProfileTxBandNumber Unsigned32, vdslLineMCMConfProfileTxBandNumber Unsigned32,
vdslLineMCMConfProfileTxBandStart Unsigned32, vdslLineMCMConfProfileTxBandStart Unsigned32,
vdslLineMCMConfProfileTxBandStop Unsigned32, vdslLineMCMConfProfileTxBandStop Unsigned32,
vdslLineMCMConfProfileTxBandRowStatus RowStatus vdslLineMCMConfProfileTxBandRowStatus RowStatus
} }
vdslLineMCMConfProfileTxBandNumber OBJECT-TYPE vdslLineMCMConfProfileTxBandNumber OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..4096)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this band descriptor entry." "The index for this band descriptor entry."
::= { vdslLineMCMConfProfileTxBandEntry 1 } ::= { vdslLineMCMConfProfileTxBandEntry 1 }
vdslLineMCMConfProfileTxBandStart OBJECT-TYPE vdslLineMCMConfProfileTxBandStart OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..4096)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Start tone index for this band." "Start tone index for this band."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileTxBandEntry 2 } ::= { vdslLineMCMConfProfileTxBandEntry 2 }
vdslLineMCMConfProfileTxBandStop OBJECT-TYPE vdslLineMCMConfProfileTxBandStop OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..4096)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Stop tone index for this band." "Stop tone index for this band."
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
skipping to change at page 9, line 42 skipping to change at page 9, line 43
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 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
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
`outOfService') it must be first unreferenced `notInService') 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.
If an entry in this table is referenced by a line which If an entry in this table is referenced by a line which
does not use MCM, it has no effect on the operation of that does not use MCM, it has no effect on the operation of that
line." line.
All read-create objects defined in this MIB module SHOULD be
stored persistently."
::= { 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."
A default profile with an index of 'DEFVAL', will
always exist and its parameters will be set to vendor
specific values, unless otherwise specified in this
document."
INDEX { vdslLineConfProfileName, INDEX { vdslLineConfProfileName,
vdslLineMCMConfProfileRxBandNumber } vdslLineMCMConfProfileRxBandNumber }
::= { vdslLineMCMConfProfileRxBandTable 1 } ::= { vdslLineMCMConfProfileRxBandTable 1 }
VdslLineMCMConfProfileRxBandEntry ::= VdslLineMCMConfProfileRxBandEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineMCMConfProfileRxBandNumber Unsigned32, vdslLineMCMConfProfileRxBandNumber Unsigned32,
vdslLineMCMConfProfileRxBandStart Unsigned32, vdslLineMCMConfProfileRxBandStart Unsigned32,
vdslLineMCMConfProfileRxBandStop Unsigned32, vdslLineMCMConfProfileRxBandStop Unsigned32,
vdslLineMCMConfProfileRxBandRowStatus RowStatus vdslLineMCMConfProfileRxBandRowStatus RowStatus
} }
vdslLineMCMConfProfileRxBandNumber OBJECT-TYPE vdslLineMCMConfProfileRxBandNumber OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..4096)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this band descriptor entry." "The index for this band descriptor entry."
::= { vdslLineMCMConfProfileRxBandEntry 1 } ::= { vdslLineMCMConfProfileRxBandEntry 1 }
vdslLineMCMConfProfileRxBandStart OBJECT-TYPE vdslLineMCMConfProfileRxBandStart OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..4096)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Start tone index for this band." "Start tone index for this band."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileRxBandEntry 2 } ::= { vdslLineMCMConfProfileRxBandEntry 2 }
vdslLineMCMConfProfileRxBandStop OBJECT-TYPE vdslLineMCMConfProfileRxBandStop OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..4096)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Stop tone index for this band." "Stop tone index for this band."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileRxBandEntry 3 } ::= { vdslLineMCMConfProfileRxBandEntry 3 }
vdslLineMCMConfProfileRxBandRowStatus OBJECT-TYPE vdslLineMCMConfProfileRxBandRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 11, line 29 skipping to change at page 11, line 34
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 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
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
`outOfService') it must be first unreferenced `notInService') 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.
If an entry in this table is referenced by a line which If an entry in this table is referenced by a line which
does not use MCM, it has no effect on the operation of that does not use MCM, it has no effect on the operation of that
line." line.
All read-create objects defined in this MIB module SHOULD be
stored persistently."
::= { 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."
A default profile with an index of 'DEFVAL', will
always exist and its parameters will be set to vendor
specific values, unless otherwise specified in this
document."
INDEX { vdslLineConfProfileName, INDEX { vdslLineConfProfileName,
vdslLineMCMConfProfileTxPSDNumber } vdslLineMCMConfProfileTxPSDNumber }
::= { vdslLineMCMConfProfileTxPSDTable 1 } ::= { vdslLineMCMConfProfileTxPSDTable 1 }
VdslLineMCMConfProfileTxPSDEntry ::= VdslLineMCMConfProfileTxPSDEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineMCMConfProfileTxPSDNumber Unsigned32, vdslLineMCMConfProfileTxPSDNumber Unsigned32,
vdslLineMCMConfProfileTxPSDTone Unsigned32, vdslLineMCMConfProfileTxPSDTone Unsigned32,
vdslLineMCMConfProfileTxPSDPSD Unsigned32, vdslLineMCMConfProfileTxPSDPSD Unsigned32,
vdslLineMCMConfProfileTxPSDRowStatus RowStatus vdslLineMCMConfProfileTxPSDRowStatus RowStatus
} }
vdslLineMCMConfProfileTxPSDNumber OBJECT-TYPE vdslLineMCMConfProfileTxPSDNumber OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..4096)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this mask descriptor entry." "The index for this mask descriptor entry."
::= { vdslLineMCMConfProfileTxPSDEntry 1 } ::= { vdslLineMCMConfProfileTxPSDEntry 1 }
vdslLineMCMConfProfileTxPSDTone OBJECT-TYPE vdslLineMCMConfProfileTxPSDTone OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..4096)
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/Hz" UNITS "0.5dBm/Hz"
skipping to change at page 13, line 15 skipping to change at page 13, line 20
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.
None of the columns in this row may be modified while the
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
`outOfService') it must be first unreferenced `notInService') it must be first unreferenced
from all associated lines." from all associated lines."
::= { vdslLineMCMConfProfileTxPSDEntry 4 } ::= { vdslLineMCMConfProfileTxPSDEntry 4 }
vdslLineMCMConfProfileMaxTxPSDTable OBJECT-TYPE vdslLineMCMConfProfileMaxTxPSDTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxTxPSDEntry SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxTxPSDEntry
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.
If an entry in this table is referenced by a line which If an entry in this table is referenced by a line which
does not use MCM, it has no effect on the operation of that does not use MCM, it has no effect on the operation of that
line." line.
All read-create objects defined in this MIB module SHOULD be
stored persistently."
::= { 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."
A default profile with an index of 'DEFVAL', will
always exist and its parameters will be set to vendor
specific values, unless otherwise specified in this
document."
INDEX { vdslLineConfProfileName, INDEX { vdslLineConfProfileName,
vdslLineMCMConfProfileMaxTxPSDNumber } vdslLineMCMConfProfileMaxTxPSDNumber }
::= { vdslLineMCMConfProfileMaxTxPSDTable 1 } ::= { vdslLineMCMConfProfileMaxTxPSDTable 1 }
VdslLineMCMConfProfileMaxTxPSDEntry ::= VdslLineMCMConfProfileMaxTxPSDEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineMCMConfProfileMaxTxPSDNumber Unsigned32, vdslLineMCMConfProfileMaxTxPSDNumber Unsigned32,
vdslLineMCMConfProfileMaxTxPSDTone Unsigned32, vdslLineMCMConfProfileMaxTxPSDTone Unsigned32,
vdslLineMCMConfProfileMaxTxPSDPSD Unsigned32, vdslLineMCMConfProfileMaxTxPSDPSD Unsigned32,
vdslLineMCMConfProfileMaxTxPSDRowStatus RowStatus vdslLineMCMConfProfileMaxTxPSDRowStatus RowStatus
} }
vdslLineMCMConfProfileMaxTxPSDNumber OBJECT-TYPE vdslLineMCMConfProfileMaxTxPSDNumber OBJECT-TYPE
skipping to change at page 14, line 14 skipping to change at page 14, line 19
VdslLineMCMConfProfileMaxTxPSDEntry ::= VdslLineMCMConfProfileMaxTxPSDEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineMCMConfProfileMaxTxPSDNumber Unsigned32, vdslLineMCMConfProfileMaxTxPSDNumber Unsigned32,
vdslLineMCMConfProfileMaxTxPSDTone Unsigned32, vdslLineMCMConfProfileMaxTxPSDTone Unsigned32,
vdslLineMCMConfProfileMaxTxPSDPSD Unsigned32, vdslLineMCMConfProfileMaxTxPSDPSD Unsigned32,
vdslLineMCMConfProfileMaxTxPSDRowStatus RowStatus vdslLineMCMConfProfileMaxTxPSDRowStatus RowStatus
} }
vdslLineMCMConfProfileMaxTxPSDNumber OBJECT-TYPE vdslLineMCMConfProfileMaxTxPSDNumber OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..4096)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
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 (1..4096)
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 There must not be multiple rows defined, for a particular
profile, with the same value for this field." 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
skipping to change at page 15, line 5 skipping to change at page 15, line 11
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 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
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
`outOfService') it must be first unreferenced `notInService') 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.
If an entry in this table is referenced by a line which If an entry in this table is referenced by a line which
does not use MCM, it has no effect on the operation of that does not use MCM, it has no effect on the operation of that
line." line.
All read-create objects defined in this MIB module SHOULD be
stored persistently."
::= { 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."
A default profile with an index of 'DEFVAL', will
always exist and its parameters will be set to vendor
specific values, unless otherwise specified in this
document."
INDEX { vdslLineConfProfileName, INDEX { vdslLineConfProfileName,
vdslLineMCMConfProfileMaxRxPSDNumber } vdslLineMCMConfProfileMaxRxPSDNumber }
::= { vdslLineMCMConfProfileMaxRxPSDTable 1 } ::= { vdslLineMCMConfProfileMaxRxPSDTable 1 }
VdslLineMCMConfProfileMaxRxPSDEntry ::= VdslLineMCMConfProfileMaxRxPSDEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineMCMConfProfileMaxRxPSDNumber Unsigned32, vdslLineMCMConfProfileMaxRxPSDNumber Unsigned32,
vdslLineMCMConfProfileMaxRxPSDTone Unsigned32, vdslLineMCMConfProfileMaxRxPSDTone Unsigned32,
vdslLineMCMConfProfileMaxRxPSDPSD Unsigned32, vdslLineMCMConfProfileMaxRxPSDPSD Unsigned32,
vdslLineMCMConfProfileMaxRxPSDRowStatus RowStatus vdslLineMCMConfProfileMaxRxPSDRowStatus RowStatus
} }
vdslLineMCMConfProfileMaxRxPSDNumber OBJECT-TYPE vdslLineMCMConfProfileMaxRxPSDNumber OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..4096)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
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 (1..4096)
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 There must not be multiple rows defined, for a particular
profile, with the same value for this field." 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
skipping to change at page 16, line 48 skipping to change at page 17, line 5
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 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
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
`outOfService') it must be first unreferenced `notInService') 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 18, line 7 skipping to change at page 18, line 17
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 This document contains many definitions taken from an earlier
draft-ietf-adslmib-vdsl-07.txt. As such, any credit for the text draft of the VDSL MIB [RFC3728]. As such any credit for the text
found within should be fully attributed to the authors of that found 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 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.
These are the tables and objects and their sensitivity/vulnerability:
vdslLineMCMConfProfileTable,
vdslLineMCMConfProfileTxWindowLength,
vdslLineMCMConfProfileRowStatus,
vdslLineMCMConfProfileTxBandTable,
vdslLineMCMConfProfileTxBandStart,
vdslLineMCMConfProfileTxBandStop,
vdslLineMCMConfProfileTxBandRowStatus,
vdslLineMCMConfProfileRxBandTable,
vdslLineMCMConfProfileRxBandStart,
vdslLineMCMConfProfileRxBandStop,
vdslLineMCMConfProfileRxBandRowStatus,
vdslLineMCMConfProfileTxPSDTable,
vdslLineMCMConfProfileTxPSDTone,
vdslLineMCMConfProfileTxPSDPSD,
vdslLineMCMConfProfileTxPSDRowStatus,
vdslLineMCMConfProfileMaxTxPSDTable
vdslLineMCMConfProfileMaxTxPSDTone,
vdslLineMCMConfProfileMaxTxPSDPSD,
vdslLineMCMConfProfileMaxTxPSDRowStatus,
vdslLineMCMConfProfileMaxRxPSDTable
vdslLineMCMConfProfileMaxRxPSDTone,
vdslLineMCMConfProfileMaxRxPSDPSD,
vdslLineMCMConfProfileMaxRxPSDRowStatus
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.
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 end- an end-user to increase their service levels or affect other
users in either a positive or negative manner. For this reason, the end-users in either a positive or negative manner. For this reason,
following tables should be considered to contain sensitive the tables and objects listed above should be considered to contain
information: sensitive information.
- vdslLineMCMConfProfileTable
- vdslLineMCMConfProfileTxBandTable
- vdslLineMCMConfProfileRxBandTable
- vdslLineMCMConfProfileTxPSDTable
- vdslLineMCMConfProfileMaxTxPSDTable
- vdslLineMCMConfProfileMaxRxPSDTable
It is thus important to control even GET access to the objects within
these tables and possibly to even encrypt the values of these objects
when sending them over the network via SNMP. Not all versions of
SNMP provide features for such a secure environment.
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 19, line 16 skipping to change at page 19, line 41
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. References 7. IANA Considerations
The IANA is kindly requested to assign the value of the
MODULE-IDENTITY. The authors suggest transmission 228,
see section 4.
7.1. Normative References 8. References
[DSLFTR057]DSL Forum TR-057, "VDSL Network Element Management", 8.1. Normative References
[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
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);
skipping to change at page 20, line 5 skipping to change at page 20, line 37
2578, April 1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Textual Conventions J., Rose, M. and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999. for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Conformance J., Rose, M. and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999. Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual
Conventions for Additional High Capacity Data Types",
RFC 2856, June 2000.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
Group MIB", RFC 2863, June 2000. Group MIB", RFC 2863, June 2000.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, RFC
3418, December 2002.
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC
3593, September 2003.
[RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", RFC 3411,
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:
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: 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.
7.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)", 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
Standard Management Framework", RFC 3410, December 2002. Internet-Standard Management Framework", RFC 3410,
December 2002.
Authors' Addresses Authors' Addresses
Menachem Dodge Menachem Dodge
Infineon Technologies Savan Ltd. ECI Telecom Ltd.
6 Hagavish St. 30 Hasivim St.
Poleg Industrial Area, Petach Tikva 49517,
Netanya 42504, Israel.
Israel
Phone: +972 9 892 4116 Phone: +972 3 926 8421
Fax: +972 9 865 8756 Fax: +972 3 928 7342
Email: menachem.dodge@infineon.com 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
 End of changes. 

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