draft-ietf-adslmib-vdsl-ext-mcm-01.txt   draft-ietf-adslmib-vdsl-ext-mcm-02.txt 
Network Working Group M. Dodge Network Working Group M. Dodge
Category: Internet Draft Infineon Technologies Category: Internet Draft Infineon Technologies
Document: draft-ietf-adslmib-vdsl-ext-mcm-01.txt B. Ray B. Ray
PESA Switching Systems PESA Switching Systems
February 2004 March 2004
Definitions of Managed Object Extensions Definitions of Managed Object Extensions
for Very High Speed Digital Subscriber Lines (VDSL) Using for Very High Speed Digital Subscriber Lines (VDSL) Using
Multiple Carrier Modulation (MCM) Line Coding. Multiple Carrier Modulation (MCM) Line Coding
draft-ietf-adslmib-vdsl-ext-mcm-02.txt
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 45 skipping to change at page 1, line 47
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
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 CORE MIB RFC XXXX [RFCXXXX] which handles the 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 .......... 2
2.2 Conventions used in the MIB Module ............................ 3 2.2 Conventions used in the MIB Module ............................ 3
2.3 Structure ..................................................... 3 2.3 Structure ..................................................... 3
2.4 Persistence ................................................... 4 2.4 Persistence ................................................... 4
3. Conformance and Compliance .................................... 5 3. Conformance and Compliance .................................... 5
4. Definitions ................................................... 5 4. Definitions ................................................... 5
5. Intellectual Property ......................................... 19 5. Security Considerations ....................................... 17
6. Normative References .......................................... 19 6. References .................................................... 18
7. Informative References ........................................ 20 6.1 Normative References .......................................... 18
8. Security Considerations ....................................... 21 6.2 Informative References ........................................ 19
9. Acknowledgements .............................................. 21 7. Acknowledgements .............................................. 19
10. Authors' Addresses ............................................ 22 8. Authors' Addresses ............................................ 20
11. Full Copyright Statement ...................................... 22 9. Full Copyright Statement ...................................... 20
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).
skipping to change at page 2, line 47 skipping to change at page 2, line 47
2. Overview 2. Overview
This document describes an SNMP MIB module for managing the line This document describes an SNMP MIB module for managing the line
code dependent (Physical Medium Dependent) Layer of MCM VDSL Lines. code dependent (Physical Medium Dependent) Layer of MCM VDSL Lines.
These definitions are based upon the specifications for VDSL as These definitions are based upon the specifications for VDSL as
defined in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011, defined in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011,
T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. Additionally the T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. Additionally the
protocol-dependent (and line-code dependent) management framework protocol-dependent (and line-code dependent) management framework
for VDSL lines specified by DSLF has been taken into consideration for VDSL lines specified by DSLF has been taken into consideration
[DSLFXXXXXX]. [DSLFTR057].
The MIB module is located in the MIB tree under MIB 2 transmission, The MIB module is located in the MIB tree under MIB 2 transmission,
as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section
of this document. of this document.
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 to other MIBS and in particular
to the IF-MIB, as presented in RFC 2863 [RFC2863], is discussed in to the IF-MIB, as presented in RFC 2863 [RFC2863], is discussed in
the VDSL-LINE CORE MIB RFC XXXX [RFCXXXX]. This section outlines the the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section outlines the
relationship of this VDSL Line Extension MIB to the VDSL-LINE CORE relationship of this VDSL Line Extension MIB to the VDSL-LINE-MIB,
MIB RFC XXXX [RFCXXXX]. RFC 3728 [RFC3728].
2.2 Conventions used in the MIB Module 2.2 Conventions used in the MIB Module
2.2.1 Naming Conventions 2.2.1 Naming Conventions
A. Vtuc -- (VTUC) transceiver at near (Central) end of line A. Vtuc -- (VTUC) transceiver at near (Central) end of line
B. Vtur -- (VTUR) transceiver at Remote end of line B. Vtur -- (VTUR) transceiver at Remote end of line
C. Vtu -- One of either Vtuc or Vtur C. Vtu -- One of either Vtuc or Vtur
D. Curr -- Current D. Curr -- Current
E. Prev -- Previous E. LCS -- Line Code Specific
F. Atn -- Attenuation F. Max -- Maximum
G. ES -- Errored Second G. PSD -- Power Spectral Density
H. SES -- Severely Errored Second H. Rx -- Receive
I. UAS -- Unavailable Second I. Tx -- Transmit
J. LCS -- Line Code Specific
K. Lof -- Loss of Frame
L. Lol -- Loss of Link
M. Los -- Loss of Signal
N. Lpr -- Loss of Power
O. xxxs -- Sum of Seconds in which xxx has occurs (e.g., xxx=Lof,
Los, Lpr, Lol)
P. Max -- Maximum
Q. Mgn -- Margin
R. Min -- Minimum
S. Psd -- Power Spectral Density
T. Snr -- Signal to Noise Ratio
U. Tx -- Transmit
V. Blks -- Blocks
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 montioring individual bands of Multiple Carrier Modulation
(MCM) VDSL modems. It contains the following tables: (MCM) VDSL modems. It contains the following tables:
- vdslLineMCMConfProfileTable - vdslLineMCMConfProfileTable
- vdslLineMCMConfProfileTxBandTable - vdslLineMCMConfProfileTxBandTable
- vdslLineMCMConfProfileRxBandTable - vdslLineMCMConfProfileRxBandTable
- vdslLineMCMConfProfileTxPSDTable - vdslLineMCMConfProfileTxPSDTable
- vdslLineMCMConfProfileMaxTxPSDTable - vdslLineMCMConfProfileMaxTxPSDTable
- vdslLineMCMConfProfileMaxRxPSDTable - vdslLineMCMConfProfileMaxRxPSDTable
Either none, some or all of the objects in this group MAY be None, some or all of the objects in this group MAY be
implemented for MCM VDSL lines. implemented for MCM VDSL lines.
Figure 1, below, displays the relationship of the tables in the Figure 1, below, displays the relationship of the tables in the
vdslMCMGroup to the vdslGroup and to the ifEntry: vdslMCMGroup to the vdslGroup and to the ifEntry:
ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1)
vdslLineTableEntry (vdslLineCoding=MCM) vdslLineTableEntry (vdslLineCoding=MCM)
vdslLineConfProfileEntry(vdslLineConfProfileName) vdslLineConfProfileEntry(vdslLineConfProfileName)
----> vdslLineMCMConfProfileTable 1:(0..1) ----> vdslLineMCMConfProfileTable 1:(0..1)
----> vdslLineMCMConfProfileTxBandTable 1:(0..1) ----> vdslLineMCMConfProfileTxBandTable 1:(0..1)
----> vdslLineMCMConfProfileRxBandTable 1:(0..1) ----> vdslLineMCMConfProfileRxBandTable 1:(0..1)
----> vdslLineMCMConfProfileTxPSDTable 1:(0..1) ----> vdslLineMCMConfProfileTxPSDTable 1:(0..1)
----> vdslLineMCMConfProfileMaxTxPSDTable 1:(0..1) ----> vdslLineMCMConfProfileMaxTxPSDTable 1:(0..1)
----> vdslLineMCMConfProfileMaxRxPSDTable 1:(0..1) ----> vdslLineMCMConfProfileMaxRxPSDTable 1:(0..1)
Figure 1: Table Relationships Figure 1: Table Relationships
When the vdslLineCoding is set to MCM, the vdslLineConfProfileName When the object vdslLineCoding is set to MCM,
which is the index of the vdslLineConfProfileEntry is also used as vdslLineConfProfileName is used as the index to
the index to the vdslLineMCMConfProfileTxBandTable of the vdslLineMCMConfProfileTxBandTable. The existence of an entry in
vdslMCMGroup. The existence of an entry in any of the tables of any of the tables of the vdslMCMGroup is optional. None, some or
the vdslMCMGroup is optional. Either none, some or all of the all of the vdslMCMGroup tables MAY be implemented for a particular
vdslMCMGroup tables MAY be implemented for a particular VDSL line VDSL line entity using MCM line coding.
entity using MCM line coding.
2.4 Persistence 2.4 Persistence
All read-write and read-create objects defined in this MIB module All read-create objects defined in this MIB module SHOULD be stored
SHOULD be stored persistently. Following is an exhaustive list of persistently. Following is an exhaustive list of these persistent
these persistent objects: objects:
vdslMCMConfProfileTxWindowLength vdslMCMConfProfileTxWindowLength
vdslMCMConfProfileRowStatus vdslMCMConfProfileRowStatus
vdslMCMConfProfileTxBandNumber vdslMCMConfProfileTxBandNumber
vdslMCMConfProfileTxBandStart vdslMCMConfProfileTxBandStart
vdslMCMConfProfileTxBandStop vdslMCMConfProfileTxBandStop
vdslMCMConfProfileTxBandRowStatus vdslMCMConfProfileTxBandRowStatus
vdslMCMConfProfileRxBandStart vdslMCMConfProfileRxBandStart
vdslMCMConfProfileRxBandStop vdslMCMConfProfileRxBandStop
vdslMCMConfProfileRxBandRowStatus vdslMCMConfProfileRxBandRowStatus
skipping to change at page 5, line 10 skipping to change at page 5, line 10
It SHOULD also be noted that interface indices in this MIB are It SHOULD also be noted that interface indices in this MIB are
maintained persistently. VACM data relating to these SHOULD be maintained persistently. VACM data relating to these SHOULD be
stored persistently as well [RFC2575]. stored persistently as well [RFC2575].
3. Conformance and Compliance 3. Conformance and Compliance
For MCM VDSL lines, the following group is optional: For MCM VDSL lines, the following group is optional:
- 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,
Counter64, Unsigned32 FROM SNMPv2-SMI -- [RFC2578]
Gauge32, RowStatus FROM SNMPv2-TC -- [RFC2579]
Integer32,
Unsigned32,
NOTIFICATION-TYPE,
transmission FROM SNMPv2-SMI
TEXTUAL-CONVENTION,
RowStatus,
TruthValue FROM SNMPv2-TC
HCPerfValidIntervals,
HCPerfInvalidIntervals,
HCPerfTimeElapsed,
HCPerfIntervalThreshold,
HCPerfCurrentCount,
HCPerfIntervalCount FROM HC-PerfHist-TC-MIB
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
NOTIFICATION-GROUP FROM SNMPv2-CONF vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728]
ifIndex FROM IF-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-MIB
vdslLineConfProfileName FROM VDSL-LINE-MIB;
vdslExtMCMMIB MODULE-IDENTITY vdslExtMCMMIB MODULE-IDENTITY
LAST-UPDATED "200402120000Z" -- February 12, 2004 LAST-UPDATED "200403140000Z" -- March 14, 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-editor: Menachem Dodge
Co-editor: Menachem Dodge
Infineon Technologies Savan Ltd. Infineon Technologies Savan Ltd.
6 Hagavish St. 6 Hagavish St.
Postal: Poleg Industrial Area, Postal: Poleg Industrial Area,
Netanya 42504, Netanya 42504,
Israel. Israel.
Email: menachem.dodge@infineon.com Email: menachem.dodge@infineon.com
Phone: +972 9 892 4116 Phone: +972 9 892 4116
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
"The VDSL Line core MIB found in RFC XXXX 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 core 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 core 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
MCM coding. The objects in this extension MIB MUST NOT be used using MCM coding. The objects in this extension MIB MUST NOT
for VDSL lines using SCM line coding. be used for VDSL lines using SCM line coding.
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
Prev -- Previous
Atn -- Attenuation
ES -- Errored Second.
SES -- Severely Errored Second
UAS -- Unavailable Second
LCS -- Line Code Specific LCS -- Line Code Specific
Lof -- Loss of Frame
Lol -- Loss of Link
Los -- Loss of Signal
Lpr -- Loss of Power
xxxs -- Interval of Seconds in which xxx occurs
(e.g., xxx=Lof, Los, Lpr)
Max -- Maximum Max -- Maximum
Mgn -- Margin PSD -- Power Spectral Density
Min -- Minimum Rx -- Receive
Psd -- Power Spectral Density
Snr -- Signal to Noise Ratio
Tx -- Transmit Tx -- Transmit
Blks -- Blocks
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 "200402120000Z" -- February 12, 2004 REVISION "200403140000Z" -- March 14, 2004
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
::= { vdslMIB XX } -- To be assigned by IANA ::= { vdslMIB XX } -- To be assigned by IANA
-- RFC Ed.: we suggest to put it under { vdslMIB 3 } because -- RFC Ed.: we suggest to put it under { vdslMIB 3 } because
-- vdslMIB 1 is the VDSL core MIB, vdslMIB 2 is the SCM -- vdslMIB 1 is the VDSL core MIB, vdslMIB 2 is the SCM
-- extension MIB, while vdslMIB 3 is the MCM extension MIB. -- extension MIB, while vdslMIB 3 is the MCM extension MIB.
vdslLineExtMCMMib OBJECT IDENTIFIER ::= { vdslExtMCMMIB 1 } vdslLineExtMCMMib OBJECT IDENTIFIER ::= { vdslExtMCMMIB 1 }
vdslLineExtMCMMibObjects OBJECT IDENTIFIER ::= {vdslLineExtMCMMib 1} vdslLineExtMCMMibObjects OBJECT IDENTIFIER ::= {vdslLineExtMCMMib 1}
-- --
-- Multiple carrier modulation (MCM) configuration profile tables -- Multiple carrier modulation (MCM) configuration profile tables
-- --
vdslLineMCMConfProfileTable OBJECT-TYPE vdslLineMCMConfProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains additional information on "This table contains additional information on multiple
multiple carrier VDSL lines. One entry in this table carrier VDSL lines. One entry in this table reflects a
reflects a profile defined by a manager which can be used profile defined by a manager which can be used to
to configure the VDSL line. configure the VDSL line.
The entries in this table MUST NOT be used for single The entries in this table MUST NOT be used for single
carrier (SCM) VDSL lines." carrier (SCM) VDSL lines."
::= { vdslLineExtMCMMibObjects 1 } ::= { vdslLineExtMCMMibObjects 1 }
vdslLineMCMConfProfileEntry OBJECT-TYPE vdslLineMCMConfProfileEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileEntry SYNTAX VdslLineMCMConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a list of parameters that "Each entry consists of a list of parameters that
represents the configuration of a multiple carrier represents the configuration of a multiple carrier
modulation VDSL modem. modulation VDSL modem.
A default profile with an index of 'DEFVAL', will always A default profile with an index of 'DEFVAL', will always
skipping to change at page 19, line 5 skipping to change at page 17, line 15
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration
information for a VDSL line based upon multiple information for a VDSL line based upon multiple
carrier modulation modem." carrier modulation modem."
::= { vdslLineExtMCMGroup 1 } ::= { vdslLineExtMCMGroup 1 }
END END
5. Intellectual Property Notice 5. Security Considerations
The IETF takes no position regarding the validity or scope of any There are a number of management objects defined in this MIB module
intellectual property or other rights that might be claimed to with a MAX-ACCESS clause of read-create. Such objects may be
pertain to the implementation or use of the technology described in considered sensitive or vulnerable in some network environments.
this document or the extent to which any license under such rights The support for SET operations in a non-secure environment without
might or might not be available; neither does it represent that it proper protection can have a negative effect on network operations.
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances
of licenses to be made available, or the result of an attempt made
to obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification
can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any Some of the readable objects in this MIB module (i.e., objects with a
copyrights, patents or patent applications, or other proprietary MAX-ACCESS other than not-accessible) may be considered sensitive or
rights which may cover technology that may be required to practice vulnerable in some network environments.
this standard. Please address the information to the IETF Executive
Director.
6. Normative References VDSL layer connectivity from the Vtur will permit the subscriber to
manipulate both the VDSL link directly and the VDSL embedded
operations channel (EOC) for their own loop. For example, unchecked
or unfiltered fluctuations initiated by the subscriber could generate
sufficient notifications to potentially overwhelm either the
management interface to the network or the element manager.
Additionally, allowing write access to configuration data may allow
an end-user to increase their service levels or affect other end-
users in either a positive or negative manner. For this reason, the
following tables should be considered to contain 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.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
6. References
6.1. Normative References
[DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management", [DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management",
February 2003. February 2003.
[ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing
(TM); Access transmission systems on metallic access (TM); Access transmission systems on metallic access
cables; Very high speed Digital Subscriber Line (VDSL); cables; Very high speed Digital Subscriber Line (VDSL);
Part 1: Functional requirements", October 1999. Part 1: Functional requirements", October 1999.
[ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing
skipping to change at page 20, line 13 skipping to change at page 19, line 5
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 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, RFC Simple Network Management Protocol (SNMP)", STD 62, RFC
3418, December 2002. 3418, December 2002.
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC Performance History Based on 15 Minute Intervals", RFC
3593, September 2003. 3593, September 2003.
[RFCXXXX] Ray, B. and R. Abbi, "High Capacity Textual Conventions [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
for MIB Modules Using Performance History Based on Architecture for Describing Simple Network Management
15 Minute Intervals", RFC XXXX, YYYY 2003. Protocol (SNMP) Management Frameworks", RFC 3411,
December 2002.
[RFCXXXX] 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 XXXX, Very High Speed Digital Subscriber Lines (VDSL)", RFC
YYYY 2003. 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. Informative References 6.2. Informative References
[RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based [RFC2575] 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 2575, April 1999.
[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.
8. Security Considerations 7. Acknowledgments
There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.
VDSL layer connectivity from the Vtur will permit the subscriber
to manipulate both the VDSL link directly and the VDSL embedded
operations channel (EOC) for their own loop. For example, unchecked
or unfiltered fluctuations initiated by the subscriber could
generate sufficient notifications to potentially overwhelm either
the management interface to the network or the element manager.
For this reason, there are a number of managed objects in this MIB
that may contain sensitive information.
It is thus important to control even GET access to these objects 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.
Further, notifications generated by agents implementing this MIB
will contain the above threshold information.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) objects
which utilize the textual conventions defined in this MIB module.
It is RECOMMENDED that implementers consider the security features
as provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of a MIB module which utilizes the textual conventions
defined in this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
9. Acknowledgments
This document contains many definitions taken from This document contains many definitions taken from
draft-ietf-adslmib-vdsl-07.txt. As such, any credit for the text draft-ietf-adslmib-vdsl-07.txt. 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.
10. Authors' Addresses 8. Authors' Addresses
Menachem Dodge Menachem Dodge
Infineon Technologies Savan Ltd. Infineon Technologies Savan Ltd.
6 Hagavish St. 6 Hagavish St.
Poleg Industrial Area, Poleg Industrial Area,
Netanya 42504, Netanya 42504,
Israel. Israel
Phone: +972 9 892 4116 Phone: +972 9 892 4116
Fax: +972 9 865 8756 Fax: +972 9 865 8756
Email: menachem.dodge@infineon.com Email: menachem.dodge@infineon.com
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
11. Full Copyright Statement 9. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). This document is subject
This document and translations of it may be copied and furnished to to the rights, licenses and restrictions contained in BCP 78 and
others, and derivative works that comment on or otherwise explain it except as set forth therein, the authors retain all their rights.
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be This document and the information contained herein are provided on an
revoked by the Internet Society or its successors or assigns. "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
This document and the information contained herein is provided on an Intellectual Property
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING The IETF takes no position regarding the validity or scope of any
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION Intellectual Property Rights or other rights that might be claimed to
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF pertain to the implementation or use of the technology described in
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use
of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository
at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

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