draft-ietf-adslmib-vdsl-ext-scm-02.txt   draft-ietf-adslmib-vdsl-ext-scm-03.txt 
Network Working Group M. Dodge Network Working Group M. Dodge
Category: Internet Draft Infineon Technologies Category: Internet Draft Infineon Technologies
B. Ray B. Ray
PESA Switching Systems PESA Switching Systems
March 2004 March 2004
Definitions of Managed Object Extensions Definitions of Managed Object Extensions
for Very High Speed Digital Subscriber Lines (VDSL) Using for Very High Speed Digital Subscriber Lines (VDSL) Using
Single Carrier Modulation (SCM) Line Coding Single Carrier Modulation (SCM) Line Coding
draft-ietf-adslmib-vdsl-ext-scm-02.txt draft-ietf-adslmib-vdsl-ext-scm-03.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
The list of current Internet-Drafts can be accessed at: The list of current Internet-Drafts can be accessed at:
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at: The list of Internet-Draft Shadow Directories can be accessed at:
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
IPR Disclosure Acknowledgement
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Abstract Abstract
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) module for use with network management protocols in the (MIB) module for use with network management protocols in the
Internet community. In particular, it describes objects used for Internet community. In particular, it describes objects used for
managing the Line Code Specific parameters of Very High Speed managing the Line Code Specific parameters of Very High Speed
Digital Subscriber Line (VDSL) interfaces using Single Carrier Digital Subscriber Line (VDSL) interfaces using Single Carrier
Modulation (SCM) Line Coding. It is an optional extension to the Modulation (SCM) Line Coding. It is an optional extension to the
VDSL-LINE-MIB, RFC 3728 [RFC3728], which handles line code VDSL-LINE-MIB, RFC 3728 [RFC3728], which handles line code
independent objects. independent objects.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework .................... 2 1. The Internet-Standard Management Framework .................... 2
2. Overview ...................................................... 2 2. Overview ...................................................... 2
2.1 Relationship of this MIB Module to other MIB Modules . 2 2.1 Relationship of this MIB Module to other MIB Modules .......... 3
2.2 Conventions used in the MIB Module ............................ 3 2.2 Conventions used in the MIB Module ............................ 3
2.3 Structure ..................................................... 3 2.3 Structure ..................................................... 3
2.4 Persistence ................................................... 4 2.4 Persistence ................................................... 4
3. Conformance and Compliance .................................... 4 3. Conformance and Compliance .................................... 4
4. Definitions ................................................... 4 4. Definitions ................................................... 4
5. Security Considerations ....................................... 13 5. Acknowledgements .............................................. 13
6. References .................................................... 14 6. Security Considerations ....................................... 13
6.1 Normative References .......................................... 14 7. References .................................................... 14
6.2 Informative References ........................................ 15 7.1 Normative References .......................................... 14
7. Acknowledgements .............................................. 15 7.2 Informative References ........................................ 15
8. Authors' Addresses ............................................ 15 8. Authors' Addresses ............................................ 15
9. Full Copyright Statement ...................................... 16 9. Full Copyright Statement ...................................... 16
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].
2. Overview 2. Overview
This document describes an SNMP MIB module for managing the line This document describes an SNMP MIB module for managing the Line
code dependent (Physical Medium Dependent) Layer of SCM VDSL Lines. Code Dependent, Physical Medium Dependent (PMD) Layer of SCM VDSL
These definitions are based upon the specifications for VDSL as Lines. These definitions are based upon the specifications for VDSL
defined in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011, as defined in T1E1, European Telecommunications Standards Institute
T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. Additionally the (ETSI), and International Telecommunication Union (ITU) documentation
protocol-dependent (and line-code dependent) management framework [T1E1311, T1E1011, T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971].
for VDSL lines specified by DSLF has been taken into consideration Additionally the protocol-dependent (and line-code dependent)
management framework for VDSL lines specified by the Digital
Subscriber Line Forum (DSLF) has been taken into consideration
[DSLFTR057] and [DSLFWT096]. [DSLFTR057] and [DSLFWT096].
The MIB module is located in the MIB tree under MIB 2 transmission, The MIB module is located in the MIB tree under the vdslMIB, which
as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section in turn is found under MIB 2 transmission. The reader is referred to
of this document. RFC 3728 [RFC3728] for further discussion of this subject.
2.1 Relationship of this MIB Module to other MIB Modules 2.1 Relationship of this MIB Module to other MIB Modules
The relationship of the VDSL Line MIB to other MIBS and in particular The relationship of the VDSL Line MIB module to other MIB modules
to the IF-MIB, as presented in RFC 2863 [RFC2863], is discussed in and in particular to the IF-MIB, as presented in RFC 2863 [RFC2863],
the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section outlines the is discussed in the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section
relationship of this VDSL Line Extension MIB to the VDSL-LINE-MIB, outlines the relationship of this VDSL Line Extension MIB to the
RFC 3728 [RFC3728]. VDSL-LINE-MIB, RFC 3728 [RFC3728].
2.2 Conventions used in the MIB Module 2.2 Conventions used in the MIB Module
2.2.1 Naming Conventions 2.2.1 Naming Conventions
A. Vtuc -- (VTUC) transceiver at near (Central) end of line A. Vtuc -- (VTUC) transceiver at near (Central) end of line
B. Vtur -- (VTUR) transceiver at Remote end of line B. Vtur -- (VTUR) transceiver at Remote end of line
C. Vtu -- One of either Vtuc or Vtur C. Vtu -- One of either Vtuc or Vtur
D. Curr -- Current D. Curr -- Current
F. Atn -- Attenuation F. Atn -- Attenuation
skipping to change at page 3, line 38 skipping to change at page 3, line 43
o vdslSCMGroup : o vdslSCMGroup :
This group supports MIB objects for defining configuration profiles This group supports MIB objects for defining configuration profiles
and for montioring individual bands of Single Carrier Modulation and for montioring individual bands of Single Carrier Modulation
(SCM) VDSL modems. It contains the following tables: (SCM) VDSL modems. It contains the following tables:
- vdslLineSCMConfProfileTxBandTable - vdslLineSCMConfProfileTxBandTable
- vdslSCMPhysBandTable - vdslSCMPhysBandTable
None, one or both objects in this group MAY be implemented for If the SCM VDSL Line Extension MIB is implemented then all of the
SCM VDSL lines. objects in this group MUST be implemented.
Figure 1, below, displays the relationship of the tables in the Figure 1, below, displays the relationship of the tables in the
vdslSCMGroup to the vdslGroup and to the ifEntry: vdslSCMGroup to the vdslGroup and to the ifEntry:
ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1)
vdslLineTableEntry (vdslLineCoding=SCM) vdslLineTableEntry (vdslLineCoding=SCM)
----> vdslPhysTableEntry 1:(0..2) ----> vdslPhysTableEntry 1:(0..2)
----> vdslSCMPhysBandTable 1:(0..6) ----> vdslSCMPhysBandTable 1:(0..5)
vdslLineConfProfileEntry(vdslLineConfProfileName) vdslLineConfProfileEntry(vdslLineConfProfileName)
----> vdslLineSCMConfProfileBandTable 1:(0..6) ----> vdslLineSCMConfProfileBandTable 1:(0..5)
Figure 1: Table Relationships Figure 1: Table Relationships
When the object vdslLineCoding is set to SCM, When the object vdslLineCoding is set to SCM,
vdslLineConfProfileName is used as the index to vdslLineConfProfileName is used as the index to
vdslLineSCMConfProfileBandTable. The existence of an entry in vdslLineSCMConfProfileBandTable. The existence of an entry in
any of the tables of the vdslSCMGroup is optional. None, some or any of the tables of the vdslSCMGroup is optional.
all of the vdslSCMGroup tables MAY be implemented for a particular
VDSL line entity using SCM line coding.
2.4 Persistence 2.4 Persistence
All read-create objects defined in this MIB module SHOULD be stored All read-create objects defined in this MIB module SHOULD be stored
persistently. Following is an exhaustive list of these persistent persistently. Following is an exhaustive list of these persistent
objects: objects:
vdslSCMConfProfileBandId vdslSCMConfProfileBandId
vdslSCMConfProfileBandUsage vdslSCMConfProfileBandUsage
vdslSCMConfProfileBandCenterFrequency vdslSCMConfProfileBandCenterFrequency
skipping to change at page 4, line 35 skipping to change at page 4, line 38
vdslSCMPhysBandUsage vdslSCMPhysBandUsage
vdslSCMPhysBandCurrPSDLevel vdslSCMPhysBandCurrPSDLevel
vdslSCMPhysBandCurrSymbolRate vdslSCMPhysBandCurrSymbolRate
vdslSCMPhysBandCurrConstellationSize vdslSCMPhysBandCurrConstellationSize
vdslSCMPhysBandCurrCenterFrequency vdslSCMPhysBandCurrCenterFrequency
vdslSCMPhysBandPerformanceBandId vdslSCMPhysBandPerformanceBandId
vdslSCMPhysBandPerformanceBandUsage vdslSCMPhysBandPerformanceBandUsage
vdslSCMPhysBandPerformanceBandSnrMgn vdslSCMPhysBandPerformanceBandSnrMgn
vdslSCMPhysBandPerformanceBandAtn vdslSCMPhysBandPerformanceBandAtn
It SHOULD also be noted that interface indices in this MIB are Note also that the interface indices in this MIB are maintained
maintained persistently. VACM data relating to these SHOULD be persistently. View-based Access Control Model (VACM) data
stored persistently as well [RFC2575]. relating to these SHOULD be stored persistently as well [RFC3415].
3. Conformance and Compliance 3. Conformance and Compliance
For SCM VDSL lines, the following group is optional: An SCM based VDSL agent does not have to implement this MIB to be
compliant with RFC 3728 [RFC3728]. If the SCM VDSL Line Extension
MIB is implemented then the following group is mandatory:
- vdslSCMGroup - vdslSCMGroup
4. Definitions 4. Definitions
VDSL-LINE-EXT-SCM-MIB DEFINITIONS ::= BEGIN VDSL-LINE-EXT-SCM-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Integer32, Integer32,
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] ifIndex FROM IF-MIB -- [RFC2863]
vdslMIB,
vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728] vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728]
vdslExtSCMMIB MODULE-IDENTITY vdslExtSCMMIB MODULE-IDENTITY
LAST-UPDATED "200403140000Z" -- March 14, 2004 LAST-UPDATED "200403300000Z" -- March 30, 2004
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
Sand Channel Systems Sand Channel Systems
Postal: P.O. Box 37324 Postal: P.O. Box 37324
Raleigh NC 27627-732 Raleigh NC 27627-732
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
Phone: +1 206 600 7022 Phone: +1 206 600 7022
skipping to change at page 5, line 43 skipping to change at page 5, line 48
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
"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 line the VDSL line. The VDSL-LINE-MIB configures and monitors the
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 and This MIB module is an optional extension of the VDSL-LINE-MIB
defines objects for configuration and monitoring of the line and defines objects for configuration and monitoring of the
code specific (LCS) elements (PMD layer) for VDSL lines using line code specific (LCS) elements (PMD layer) for VDSL lines
SCM coding. The objects in this extension MIB MUST NOT be used using SCM coding. The objects in this extension MIB MUST NOT
for VDSL lines using MCM line coding. be used for VDSL lines using Multiple Carrier Modulation (MCM)
line coding. If an object in this extension MIB is referenced
by a line which does not use SCM, it has no effect on the
operation of that line.
Naming Conventions: Naming Conventions:
Vtuc -- (VTUC) transceiver at near (Central) end of line Vtuc -- (VTUC) transceiver at near (Central) end of line
Vtur -- (VTUR) transceiver at Remote end of line Vtur -- (VTUR) transceiver at Remote end of line
Vtu -- One of either Vtuc or Vtur Vtu -- One of either Vtuc or Vtur
Curr -- Current Curr -- Current
Atn -- Attenuation Atn -- Attenuation
LCS -- Line Code Specific LCS -- Line Code Specific
Max -- Maximum Max -- Maximum
Mgn -- Margin Mgn -- Margin
PSD -- Power Spectral Density PSD -- Power Spectral Density
Rx -- Receive Rx -- Receive
Snr -- Signal to Noise Ratio Snr -- Signal to Noise Ratio
Tx -- Transmit Tx -- Transmit
Copyright (C) The Internet Society (2004). This version Copyright (C) The Internet Society (2004). This version
of this MIB module is part of RFC XXXX: see the RFC of this MIB module is part of RFC XXXX: see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
REVISION "200403140000Z" -- March 14, 2004 REVISION "200403300000Z" -- March 30, 2004
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
::= { vdslMIB XX } -- To be assigned by IANA ::= { vdslMIB XX } -- To be assigned by IANA
-- RFC Ed.: we suggest to put it under { vdslMIB 2 } because -- RFC Ed.: we suggest to put it under { vdslMIB 2 } because
-- vdslMIB 1 is the VDSL-LINE-MIB, vdslMIB 2 is this SCM -- vdslMIB 1 is the VDSL-LINE-MIB, vdslMIB 2 is this SCM
-- extension MIB, while vdslMIB 3 is the MCM extension MIB. -- extension MIB, while vdslMIB 3 is the MCM extension MIB.
vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslExtSCMMIB 1 } vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslExtSCMMIB 1 }
vdslLineExtSCMMibObjects OBJECT IDENTIFIER ::= vdslLineExtSCMMibObjects OBJECT IDENTIFIER ::=
{ vdslLineExtSCMMib 1 } { vdslLineExtSCMMib 1 }
skipping to change at page 6, line 41 skipping to change at page 6, line 49
-- --
vdslLineSCMConfProfileBandTable OBJECT-TYPE vdslLineSCMConfProfileBandTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineSCMConfProfileBandEntry SYNTAX SEQUENCE OF VdslLineSCMConfProfileBandEntry
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
of a single carrier modulation (SCM) VDSL line. of a single carrier modulation (SCM) VDSL line. For each
These entries are defined by a manager and can be used to profile which is associated with a VDSL line using SCM
configure the VDSL line." line coding, five entries in this table will exist, one for
each of the five bands. Bands which are not in use will be
marked as unused. These entries are defined by a manager
and can be used to configure the VDSL line. If an entry in
this table is referenced by a line which does not use SCM,
it has no effect on the operation of that line."
::= { vdslLineExtSCMMibObjects 1 } ::= { vdslLineExtSCMMibObjects 1 }
vdslLineSCMConfProfileBandEntry OBJECT-TYPE vdslLineSCMConfProfileBandEntry OBJECT-TYPE
SYNTAX VdslLineSCMConfProfileBandEntry SYNTAX VdslLineSCMConfProfileBandEntry
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 single carrier represents the configuration of a single carrier
modulation VDSL modem transmit band. modulation VDSL modem transmit band.
skipping to change at page 7, line 15 skipping to change at page 7, line 28
specific values, unless otherwise specified in this specific values, unless otherwise specified in this
document." document."
INDEX { vdslLineConfProfileName, INDEX { vdslLineConfProfileName,
vdslLineSCMConfProfileBandId } vdslLineSCMConfProfileBandId }
::= { vdslLineSCMConfProfileBandTable 1 } ::= { vdslLineSCMConfProfileBandTable 1 }
VdslLineSCMConfProfileBandEntry ::= VdslLineSCMConfProfileBandEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineSCMConfProfileBandId INTEGER, vdslLineSCMConfProfileBandId Unsigned32,
vdslLineSCMConfProfileBandUsage INTEGER, vdslLineSCMConfProfileBandUsage Unsigned32,
vdslLineSCMConfProfileBandCenterFrequency Unsigned32, vdslLineSCMConfProfileBandCenterFrequency Unsigned32,
vdslLineSCMConfProfileBandSymbolRate Unsigned32, vdslLineSCMConfProfileBandSymbolRate Unsigned32,
vdslLineSCMConfProfileBandConstellationSize Unsigned32, vdslLineSCMConfProfileBandConstellationSize Unsigned32,
vdslLineSCMConfProfileBandTransmitPSDLevel Unsigned32, vdslLineSCMConfProfileBandTransmitPSDLevel Unsigned32,
vdslLineSCMConfProfileBandRowStatus RowStatus vdslLineSCMConfProfileBandRowStatus RowStatus
} }
vdslLineSCMConfProfileBandId OBJECT-TYPE vdslLineSCMConfProfileBandId OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BandId for this entry, which specifies which band "The BandId for this entry, which specifies which band
is being referred to. Specified as an INTEGER, the five is being referred to. Specified as an Unsigned32, the five
possible values are: possible values are:
optionalBand(1), optionalBand(1),
1D(2), 1D(2),
1U(3), 1U(3),
2D(4), 2D(4),
2U(5)" 2U(5)"
::= { vdslLineSCMConfProfileBandEntry 1 } ::= { vdslLineSCMConfProfileBandEntry 1 }
vdslLineSCMConfProfileBandUsage OBJECT-TYPE vdslLineSCMConfProfileBandUsage OBJECT-TYPE
SYNTAX INTEGER SYNTAX unsigned32
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether this band is in use. "Indicates whether this band is in use.
Specified as an INTEGER, the two Specified as an Unsigned32, the two
possible values are: possible values are:
Unused(1), Unused(1),
InUse(2)" InUse(2)"
::= { vdslLineSCMConfProfileBandEntry 2 } ::= { vdslLineSCMConfProfileBandEntry 2 }
vdslLineSCMConfProfileBandCenterFrequency OBJECT-TYPE vdslLineSCMConfProfileBandCenterFrequency OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "Hz" UNITS "Hz"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the center frequency in Hz" "Specifies the center frequency in Hz"
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileBandEntry 3 } ::= { vdslLineSCMConfProfileBandEntry 3 }
skipping to change at page 9, line 22 skipping to change at page 9, line 30
-- SCM physical band -- SCM physical band
-- --
vdslLineSCMPhysBandTable OBJECT-TYPE vdslLineSCMPhysBandTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineSCMPhysBandEntry SYNTAX SEQUENCE OF VdslLineSCMPhysBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides one row for each SCM Vtu band. This "This table provides one row for each SCM Vtu band. This
table is read only as it reflects the current physical table is read only as it reflects the current physical
parameters of each band." parameters of each band. For each ifIndex which is
associated with a VDSL line using SCM line coding, five
entries in this table will exist, one for each of the
five bands. Bands which are not in use will be marked
as unused."
::= { vdslLineExtSCMMibObjects 2 } ::= { vdslLineExtSCMMibObjects 2 }
vdslLineSCMPhysBandEntry OBJECT-TYPE vdslLineSCMPhysBandEntry OBJECT-TYPE
SYNTAX VdslLineSCMPhysBandEntry SYNTAX VdslLineSCMPhysBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the vdslLineSCMPhysBandTable." "An entry in the vdslLineSCMPhysBandTable."
INDEX { ifIndex, INDEX { ifIndex,
vdslLineSCMPhysBandId } vdslLineSCMPhysBandId }
::= { vdslLineSCMPhysBandTable 1 } ::= { vdslLineSCMPhysBandTable 1 }
VdslLineSCMPhysBandEntry ::= VdslLineSCMPhysBandEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineSCMPhysBandId INTEGER, vdslLineSCMPhysBandId Unsigned32,
vdslLineSCMPhysBandUsage INTEGER, vdslLineSCMPhysBandUsage Unsigned32,
vdslLineSCMPhysBandCurrCenterFrequency Unsigned32, vdslLineSCMPhysBandCurrCenterFrequency Unsigned32,
vdslLineSCMPhysBandCurrSymbolRate Unsigned32, vdslLineSCMPhysBandCurrSymbolRate Unsigned32,
vdslLineSCMPhysBandCurrConstellationSize Unsigned32, vdslLineSCMPhysBandCurrConstellationSize Unsigned32,
vdslLineSCMPhysBandCurrPSDLevel Unsigned32, vdslLineSCMPhysBandCurrPSDLevel Unsigned32,
vdslLineSCMPhysBandCurrSnrMgn Integer32, vdslLineSCMPhysBandCurrSnrMgn Integer32,
vdslLineSCMPhysBandCurrAtn Unsigned32 vdslLineSCMPhysBandCurrAtn Unsigned32
} }
vdslLineSCMPhysBandId OBJECT-TYPE vdslLineSCMPhysBandId OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BandId for this entry, which specifies which band "The BandId for this entry, which specifies which band
is being referred to. Specified as an INTEGER, the five is being referred to. Specified as an Unsigned32, the five
possible values are: possible values are:
optionalBand(1), optionalBand(1),
1D(2), 1D(2),
1U(3), 1U(3),
2D(4), 2D(4),
2U(5)" 2U(5)"
::= { vdslLineSCMPhysBandEntry 1 } ::= { vdslLineSCMPhysBandEntry 1 }
vdslLineSCMPhysBandUsage OBJECT-TYPE vdslLineSCMPhysBandUsage OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether this band is in use. "Indicates whether this band is in use.
Specified as an INTEGER, the two Specified as an Unsigned32, the two
possible values are: possible values are:
Unused(1), Unused(1),
InUse(2)" InUse(2)"
::= { vdslLineSCMPhysBandEntry 2 } ::= { vdslLineSCMPhysBandEntry 2 }
vdslLineSCMPhysBandCurrCenterFrequency OBJECT-TYPE vdslLineSCMPhysBandCurrCenterFrequency OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "Hz" UNITS "Hz"
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 13, line 5 skipping to change at page 13, line 5
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration
information for a VDSL line based upon single carrier information for a VDSL line based upon single carrier
modulation modem." modulation modem."
::= { vdslLineExtSCMGroups 1 } ::= { vdslLineExtSCMGroups 1 }
END END
5. Security Considerations 5. Acknowledgments
There are a number of management objects defined in this MIB that This document contains many definitions taken from
have a MAX-ACCESS clause of read-create. Such draft-ietf-adslmib-vdsl-07.txt. As such any credit for the text
objects may be considered sensitive or vulnerable in some network found within should be full attributed to the authors of that
environments. The support for SET operations in a non-secure document.
environment without proper protection can have a negative effect on
network operations. 6. Security Considerations
There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-create. Such objects may be
considered sensitive or vulnerable in some network environments.
The support for SET operations in a non-secure environment without
proper protection can have a negative effect on network operations.
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
skipping to change at page 13, line 34 skipping to change at page 13, line 40
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 end-
users in either a positive or negative manner. For this reason, the users in either a positive or negative manner. For this reason, the
following tables should be considered to contain sensitive following tables should be considered to contain sensitive
information: information:
- vdslLineSCMConfProfileTxBandTable - vdslLineSCMConfProfileTxBandTable
- vdslSCMPhysBandTable - vdslSCMPhysBandTable
It is thus important to control even GET access to these objects and It is thus important to control even GET access to the objects within
possibly to even encrypt the values of these objects when sending these tables and possibly to even encrypt the values of these objects
them over the network via SNMP. Not all versions of SNMP provide when sending them over the network via SNMP. Not all versions of
features for such a secure environment. 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 It is RECOMMENDED that implementers consider the security features
as provided by the SNMPv3 framework (see [RFC3410], section 8), as 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 14, line 6 skipping to change at page 14, line 12
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.
6. References 7. References
6.1. Normative References 7.1. Normative References
[DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management", [DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management",
February 2003. February 2003.
[DSLFWT096] DSL Forum WT-096, "SCM Specific Managed Objects In [DSLFWT096] DSL Forum WT-096, "SCM Specific Managed Objects In
VDSL Network Elements". VDSL Network Elements".
[ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing [ETSI2701] ETSI TS 101 270-1 V1.2.1, "Transmission and Multiplexing
(TM); Access transmission systems on metallic access (TM); Access transmission systems on metallic access
cables; Very high speed Digital Subscriber Line (VDSL); cables; Very high speed Digital Subscriber Line (VDSL);
Part 1: Functional requirements", October 1999. Part 1: Functional requirements", October 1999.
[ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing [ETSI2702] ETSI TS 101 270-2 V1.1.1, "Transmission and Multiplexing
(TM); Access transmission systems on metallic access (TM); Access transmission systems on metallic access
cables; Very high speed Digital Subscriber Line (VDSL); cables; Very high speed Digital Subscriber Line (VDSL);
Part 1: Transceiver specification", February 2001. Part 1: Transceiver specification", February 2001.
[ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line [ITU9931] ITU-T G.993.1, "Very-high-speed digital subscriber line
foundation", November 2001. foundation", November 2001.
[ITU9971] ITU-T G.997.1 "Physical layer management for Digital [ITU9971] ITU-T G.997.1, "Physical layer management for Digital
Subscriber Line (DSL) Transceivers", July 1999. Subscriber Line (DSL) Transceivers", July 1999.
[RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC Performance History Based on 15 Minute Intervals", RFC
2493, January 1999. 3593, September 2003.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
skipping to change at page 15, line 5 skipping to change at page 15, line 13
Rose, M. and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual
Conventions for Additional High Capacity Data Types", Conventions for Additional High Capacity Data Types",
RFC 2856, June 2000. RFC 2856, June 2000.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", RFC 3411, Protocol (SNMP) Management Frameworks", RFC 3411,
December 2002. December 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, RFC Simple Network Management Protocol (SNMP)", STD 62, RFC
3418, December 2002. 3418, December 2002.
[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
skipping to change at page 15, line 31 skipping to change at page 15, line 39
February 2001. February 2001.
[T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2:
Technical Specification for a Single-Carrier Modulation Technical Specification for a Single-Carrier Modulation
(SCM) Transceiver", November 2001. (SCM) Transceiver", November 2001.
[T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3:
Technical Specification for a Multi-Carrier Modulation Technical Specification for a Multi-Carrier Modulation
(MCM) Transceiver", November 2000. (MCM) Transceiver", November 2000.
6.2. Informative References 7.2. Informative References
[RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999. Management Protocol (SNMP)", RFC 3415, December 2002.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
7. Acknowledgments
This document contains many definitions taken from
draft-ietf-adslmib-vdsl-07.txt. As such any credit for the text
found within should be full attributed to the authors of that
document.
8. Authors' Addresses 8. Authors' Addresses
Menachem Dodge Menachem Dodge
Infineon Technologies Savan Ltd. Infineon Technologies Savan Ltd.
6 Hagavish St. 6 Hagavish St.
Poleg Industrial Area, Poleg Industrial Area,
Netanya 42504, Netanya 42504,
Israel. Israel.
 End of changes. 

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