draft-ietf-adslmib-vdsl-ext-scm-05.txt   draft-ietf-adslmib-vdsl-ext-scm-06.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
June 2004 October 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-05.txt draft-ietf-adslmib-vdsl-ext-scm-06.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 39 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 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, 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 .................................... 4 3. Conformance and Compliance .................................... 4
4. Definitions ................................................... 4 4. Definitions ................................................... 4
5. Acknowledgements .............................................. 13 5. Acknowledgements .............................................. 13
6. Security Considerations ....................................... 13 6. Security Considerations ....................................... 14
7. References .................................................... 14 7. IANA Considerations ........................................... 15
7.1 Normative References .......................................... 14 8. References .................................................... 15
7.2 Informative References ........................................ 15 8.1 Normative References .......................................... 15
Authors' Addresses ............................................ 15 8.2 Informative References ........................................ 16
Full Copyright Statement ...................................... 16 Authors' Addresses ............................................ 16
Full Copyright Statement ...................................... 17
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 51 skipping to change at page 2, line 52
Code Dependent, Physical Medium Dependent (PMD) Layer of SCM VDSL Code Dependent, Physical Medium Dependent (PMD) Layer of SCM 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] and [DSLFWT096]. [DSLFTR057] and [DSLFWT096].
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 The key words "MUST", "MUST NOT", "RECOMMENDED", and "SHOULD" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2.1 Relationship of this MIB Module to other MIB Modules 2.1 Relationship of this MIB Module to other MIB Modules
The relationship of the VDSL Line MIB module to other MIB modules The relationship of the VDSL Line MIB module to other MIB modules
and 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
skipping to change at page 5, line 16 skipping to change at page 5, line 16
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, vdslMIB,
vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728] vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728]
vdslExtSCMMIB MODULE-IDENTITY vdslExtSCMMIB MODULE-IDENTITY
LAST-UPDATED "200406130000Z" -- June 13, 2004 LAST-UPDATED "200410130000Z" -- October 13, 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: mbdodge@ieee.org
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
" "
skipping to change at page 6, line 25 skipping to change at page 6, line 25
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 "200406130000Z" -- June 13, 2004 REVISION "200410130000Z" -- October 13, 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 98 } because
-- transmission 97 is the VDSL-LINE-MIB, transmission 98
-- would be this SCM MIB and transmission 99 the MCM MIB.
vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslExtSCMMIB 1 } vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslExtSCMMIB 1 }
vdslLineExtSCMMibObjects OBJECT IDENTIFIER ::= vdslLineExtSCMMibObjects OBJECT IDENTIFIER ::=
{ vdslLineExtSCMMib 1 } { vdslLineExtSCMMib 1 }
-- --
-- textual conventions used in this MIB
--
VdslSCMBandId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used as the syntax for the VDSL SCM Band
Identity. Attributes with this syntax identify the SCM Band
referred to. Specified as an INTEGER, the possible values
are:
optionalBand (1) -- the optional Band range [25kHz - 138kHz]
firstDownstreamBand (2) -- first Downstream Band
firstUpstreamBand (3) -- first Upstream Band
secondDownstreamBand (4) -- second Downstream Band
secondUpstreamBand (5) -- second Upstream Band
thirdDownstreamBand (6) -- third Downstream Band
thirdUpstreamBand (7) -- third Upstream Band"
SYNTAX INTEGER { optionalBand (1),
firstDownstreamBand (2),
firstUpstreamBand (3),
secondDownstreamBand (4),
secondUpstreamBand (5),
thirdDownstreamBand (6),
thirdUpstreamBand (7) }
VdslSCMBandUsage ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used to indicate whether the SCM Band
is in use or not. The two possible values are:
unUsed (1),
inUse (2)"
SYNTAX INTEGER {
unUsed (1),
inUse (2) }
--
-- Single carrier modulation (SCM) configuration profile tables -- Single carrier modulation (SCM) configuration profile tables
-- --
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
skipping to change at page 7, line 19 skipping to change at page 8, line 8
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.
A default profile with an index of 'DEFVAL', will A default profile with an index of 'DEFVAL', will
always exist and its parameters will be set to vendor always exist and its parameters will be set to vendor
specific values, unless otherwise specified in this specific values, unless otherwise specified in this
document." document.
All read-create objects defined in this MIB module SHOULD be
stored persistently."
INDEX { vdslLineConfProfileName, INDEX { vdslLineConfProfileName,
vdslLineSCMConfProfileBandId } vdslLineSCMConfProfileBandId }
::= { vdslLineSCMConfProfileBandTable 1 } ::= { vdslLineSCMConfProfileBandTable 1 }
VdslLineSCMConfProfileBandEntry ::= VdslLineSCMConfProfileBandEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineSCMConfProfileBandId Unsigned32, vdslLineSCMConfProfileBandId VdslSCMBandId,
vdslLineSCMConfProfileBandUsage Unsigned32, vdslLineSCMConfProfileBandUsage VdslSCMBandUsage,
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 Unsigned32 { optionalBand (1), SYNTAX VdslSCMBandId
firstDownstreamBand (2), MAX-ACCESS not-accessible
firstUpstreamBand (3),
secondDownstreamBand (4),
secondUpstreamBand (5),
thirdDownstreamBand (6),
thirdUpstreamBand (7) }
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 Unsigned32, the five is being referred to. Specified as an INTEGER, the
possible values are: possible values are:
optionalBand (1), firstDownstreamBand (2), optionalBand (1), firstDownstreamBand (2),
firstUpstreamBand (3), secondDownstreamBand (4), firstUpstreamBand (3), secondDownstreamBand (4),
secondUpstreamBand (5), thirdDownstreamBand (6), secondUpstreamBand (5), thirdDownstreamBand (6),
thirdUpstreamBand (7)" thirdUpstreamBand (7)"
::= { vdslLineSCMConfProfileBandEntry 1 } ::= { vdslLineSCMConfProfileBandEntry 1 }
vdslLineSCMConfProfileBandUsage OBJECT-TYPE vdslLineSCMConfProfileBandUsage OBJECT-TYPE
SYNTAX unsigned32 SYNTAX VdslSCMBandUsage
MAX-ACCESS read-create 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 Unsigned32, the two Specified as an INTEGER, the 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 15 skipping to change at page 10, line 5
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."
::= { vdslLineSCMConfProfileBandEntry 7 } ::= { vdslLineSCMConfProfileBandEntry 7 }
-- --
-- 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
skipping to change at page 9, line 52 skipping to change at page 10, line 45
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 Unsigned32, vdslLineSCMPhysBandId VdslSCMBandId,
vdslLineSCMPhysBandUsage Unsigned32, vdslLineSCMPhysBandUsage VdslSCMBandUsage,
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 Unsigned32 { optionalBand (1), SYNTAX VdslSCMBandId
firstDownstreamBand (2),
firstUpstreamBand (3),
secondDownstreamBand (4),
secondUpstreamBand (5),
thirdDownstreamBand (6),
thirdUpstreamBand (7) }
MAX-ACCESS read-only 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 Unsigned32, the is being referred to. Specified as an Unsigned32, the
five possible values are: possible values are:
optionalBand (1), firstDownstreamBand (2), optionalBand (1), firstDownstreamBand (2),
firstUpstreamBand (3), secondDownstreamBand (4), firstUpstreamBand (3), secondDownstreamBand (4),
secondUpstreamBand (5), thirdDownstreamBand (6), secondUpstreamBand (5), thirdDownstreamBand (6),
thirdUpstreamBand (7)" thirdUpstreamBand (7)"
::= { vdslLineSCMPhysBandEntry 1 } ::= { vdslLineSCMPhysBandEntry 1 }
vdslLineSCMPhysBandUsage OBJECT-TYPE vdslLineSCMPhysBandUsage OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX VdslSCMBandUsage
MAX-ACCESS read-only 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 Unsigned32, 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 }
skipping to change at page 13, line 32 skipping to change at page 14, line 25
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 following tables should be considered to contain sensitive
information: information:
- vdslLineSCMConfProfileTxBandTable - vdslLineSCMConfProfileTxBandTable
- vdslSCMPhysBandTable - vdslSCMPhysBandTable
It is thus important to control even GET access to the objects within 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 these tables and possibly to even encrypt the values of these objects
when sending them over the network via SNMP. Not all versions of when sending them over the network via SNMP. Not all versions of
SNMP provide features for such a secure environment. SNMP provide features for such a secure environment.
skipping to change at page 14, line 12 skipping to change at page 15, line 5
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 98, see section 4.
7.1. Normative References 8. References
8.1. Normative References
[DSLFTR57] DSL Forum TR-057, "VDSL Network Element Management", [DSLFTR57] DSL Forum TR-057, "VDSL Network Element Management",
February 2003. February 2003.
[DSLFWT96] DSL Forum WT-096, "SCM Specific Managed Objects In [DSLFWT96] 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);
skipping to change at page 14, line 38 skipping to change at page 15, line 35
(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.
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC
3593, September 2003.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 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
skipping to change at page 15, line 13 skipping to change at page 16, line 5
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
Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", RFC 3411,
December 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, RFC
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
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 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.
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. 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: mbdodge@ieee.org
Bob Ray Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
330-A Wynn Drive 330-A Wynn Drive
Huntsville, AL 35805 Huntsville, AL 35805
USA USA
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Fax: +1 256 726 9271 Fax: +1 256 726 9271
EMail: rray@pesa.com EMail: rray@pesa.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78 and to the rights, licenses and restrictions contained in BCP 78 and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
skipping to change at page 17, line 4 skipping to change at page 17, line 40
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at
ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

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