draft-ietf-adslmib-vdsl-ext-scm-06.txt   draft-ietf-adslmib-vdsl-ext-scm-07.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
October 2004 November 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-06.txt draft-ietf-adslmib-vdsl-ext-scm-07.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of 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 is aware have been or will be disclosed, and any of
which he or she becomes aware will be disclosed, in accordance with which he or she becomes aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
skipping to change at page 2, line 50 skipping to change at page 2, line 50
This document describes an SNMP MIB module for managing the Line This document describes an SNMP MIB module for managing the Line
Code Dependent, Physical Medium Dependent (PMD) Layer of 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]. [DSLFTR57] and [DSLFWT96].
The MIB module is located in the MIB tree under MIB-2 transmission. The MIB module is located in the MIB tree under MIB-2 transmission.
The key words "MUST", "MUST NOT", "RECOMMENDED", and "SHOULD" in this The key words "MUST", "MUST NOT", "RECOMMENDED", and "SHOULD" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2.1 Relationship of this MIB Module to other MIB Modules 2.1 Relationship of this MIB Module to other MIB Modules
The relationship of the VDSL Line MIB module to other MIB modules The relationship of the VDSL Line MIB module to other MIB modules
and 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],
skipping to change at page 3, line 37 skipping to change at page 3, line 37
T. Snr -- Signal to Noise Ratio T. Snr -- Signal to Noise Ratio
U. Tx -- Transmit U. Tx -- Transmit
2.3 Structure 2.3 Structure
The SCM VDSL Line Extension MIB contains the following MIB group: The SCM VDSL Line Extension MIB contains the following MIB group:
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 monitoring 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
If the SCM VDSL Line Extension MIB is implemented then all of the If the SCM VDSL Line Extension MIB is implemented then all of the
objects in this group MUST be implemented. 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:
skipping to change at page 5, line 7 skipping to change at page 5, line 7
- 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,
transmission,
Unsigned32 FROM SNMPv2-SMI -- [RFC2578] Unsigned32 FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION,
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 "200410130000Z" -- October 13, 2004 LAST-UPDATED "200411120000Z" -- November 12, 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 6, line 25 skipping to change at page 6, line 27
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 "200410130000Z" -- October 13, 2004 REVISION "200411120000Z" -- November 12, 2004
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XX with assigned number & remove this note -- RFC Ed.: replace XX with assigned number & remove this note
::= { transmission XX } -- To be assigned by IANA ::= { transmission XX } -- To be assigned by IANA
-- RFC Ed.: we suggest to put it under { transmission 227 } because
-- this is the first available number, transmission 228
-- would be used for 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 -- textual conventions used in this MIB
-- --
VdslSCMBandId ::= TEXTUAL-CONVENTION VdslSCMBandId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax for the VDSL SCM Band "This data type is used as the syntax for the VDSL SCM Band
Identity. Attributes with this syntax identify the SCM Band Identity. Attributes with this syntax identify the SCM Band
referred to. Specified as an INTEGER, the possible values referred to. Specified as an INTEGER, the possible values
skipping to change at page 7, line 10 skipping to change at page 7, line 10
secondDownstreamBand (4) -- second Downstream Band secondDownstreamBand (4) -- second Downstream Band
secondUpstreamBand (5) -- second Upstream Band secondUpstreamBand (5) -- second Upstream Band
thirdDownstreamBand (6) -- third Downstream Band thirdDownstreamBand (6) -- third Downstream Band
thirdUpstreamBand (7) -- third Upstream Band" thirdUpstreamBand (7) -- third Upstream Band"
SYNTAX INTEGER { optionalBand (1), SYNTAX INTEGER { optionalBand (1),
firstDownstreamBand (2), firstDownstreamBand (2),
firstUpstreamBand (3), firstUpstreamBand (3),
secondDownstreamBand (4), secondDownstreamBand (4),
secondUpstreamBand (5), secondUpstreamBand (5),
thirdDownstreamBand (6), thirdDownstreamBand (6),
thirdUpstreamBand (7) } thirdUpstreamBand
(7) }
VdslSCMBandUsage ::= TEXTUAL-CONVENTION VdslSCMBandUsage ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used to indicate whether the SCM Band "This data type is used to indicate whether the SCM Band
is in use or not. The two possible values are: is in use or not. The two possible values are:
unUsed (1), unUsed (1),
inUse (2)" inUse (2)"
SYNTAX INTEGER { SYNTAX INTEGER {
skipping to change at page 10, line 49 skipping to change at page 10, line 49
vdslLineSCMPhysBandId } vdslLineSCMPhysBandId }
::= { vdslLineSCMPhysBandTable 1 } ::= { vdslLineSCMPhysBandTable 1 }
VdslLineSCMPhysBandEntry ::= VdslLineSCMPhysBandEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineSCMPhysBandId VdslSCMBandId, vdslLineSCMPhysBandId VdslSCMBandId,
vdslLineSCMPhysBandUsage VdslSCMBandUsage, vdslLineSCMPhysBandUsage VdslSCMBandUsage,
vdslLineSCMPhysBandCurrCenterFrequency Unsigned32, vdslLineSCMPhysBandCurrCenterFrequency Unsigned32,
vdslLineSCMPhysBandCurrSymbolRate Unsigned32, vdslLineSCMPhysBandCurrSymbolRate Unsigned32,
vdslLin
vdslLineSCMPhysBandCurrConstellationSize Unsigned32, eSCMPhysBandCurrConstellationSize Unsigned32,
vdslLineSCMPhysBandCurrPSDLevel Unsigned32, vdslLineSCMPhysBandCurrPSDLevel Unsigned32,
vdslLineSCMPhysBandCurrSnrMgn Integer32, vdslLineSCMPhysBandCurrSnrMgn Integer32,
vdslLineSCMPhysBandCurrAtn Unsigned32 vdslLineSCMPhysBandCurrAtn Unsigned32
} }
vdslLineSCMPhysBandId OBJECT-TYPE vdslLineSCMPhysBandId OBJECT-TYPE
SYNTAX VdslSCMBandId SYNTAX VdslSCMBandId
MAX-ACCESS read-only MAX-ACCESS not-accessible
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
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 }
skipping to change at page 12, line 27 skipping to change at page 12, line 27
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transmit power spectral density for the "The transmit power spectral density for the
VDSL modem." VDSL modem."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMPhysBandEntry 6 } ::= { vdslLineSCMPhysBandEntry 6 }
vdslLineSCMPhysBandCurrSnrMgn OBJECT-TYPE vdslLineSCMPhysBandCurrSnrMgn OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.25 dBm" UNITS "0.25 dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Noise margin as seen by this Vtu and band with respect "Noise margin as seen by this Vtu and band with respect
to its received signal in 0.25 dB." to its received signal in 0.25 dB."
::= { vdslLineSCMPhysBandEntry 7 } ::= { vdslLineSCMPhysBandEntry 7 }
vdslLineSCMPhysBandCurrAtn OBJECT-TYPE vdslLineSCMPhysBandCurrAtn OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
UNITS "0.25 dBm" UNITS "0.25 dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Measured difference in the total power transmitted by "Measured difference in the total power transmitted by
the peer Vtu on this band and the total power received the peer Vtu on this band and the total power received
by this Vtu on this band in 0.25 dB." by this Vtu on this band in 0.25 dB."
::= { vdslLineSCMPhysBandEntry 8 } ::= { vdslLineSCMPhysBandEntry 8 }
-- conformance information -- conformance information
vdslLineExtSCMConformance OBJECT IDENTIFIER ::= vdslLineExtSCMConformance OBJECT IDENTIFIER ::=
skipping to change at page 13, line 24 skipping to change at page 13, line 24
vdslLineExtSCMGroup vdslLineExtSCMGroup
} }
::= { vdslLineExtSCMCompliances 1 } ::= { vdslLineExtSCMCompliances 1 }
-- units of conformance -- units of conformance
vdslLineExtSCMGroup OBJECT-GROUP vdslLineExtSCMGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
vdslLineSCMConfProfileBandId,
vdslLineSCMConfProfileBandUsage, vdslLineSCMConfProfileBandUsage,
vdslLineSCMConfProfileBandTransmitPSDLevel, vdslLineSCMConfProfileBandTransmitPSDLevel,
vdslLineSCMConfProfileBandSymbolRate, vdslLineSCMConfProfileBandSymbolRate,
vdslLineSCMConfProfileBandConstellationSize, vdslLineSCMConfProfileBandConstellationSize,
vdslLineSCMConfProfileBandCenterFrequency, vdslLineSCMConfProfileBandCenterFrequency,
vdslLineSCMConfProfileBandRowStatus, vdslLineSCMConfProfileBandRowStatus,
vdslLineSCMPhysBandId,
vdslLineSCMPhysBandUsage, vdslLineSCMPhysBandUsage,
vdslLineSCMPhysBandCurrPSDLevel, vdslLineSCMPhysBandCurrPSDLevel,
vdslLineSCMPhysBandCurrSymbolRate, vdslLineSCMPhysBandCurrSymbolRate,
vdslLineSCMPhysBandCurrConstellationSize, vdslLineSCMPhysBandCurrConstellationSize,
vdslLineSCMPhysBandCurrCenterFrequency, vdslLineSCMPhysBandCurrCenterFrequency,
vdslLineSCMPhysBandCurrSnrMgn, vdslLineSCMPhysBandCurrSnrMgn,
vdslLineSCMPhysBandCurrAtn vdslLineSCMPhysBandCurrAtn
} }
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. Acknowledgments 5. Acknowledgments
skipping to change at page 13, line 52 skipping to change at page 13, line 51
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. Acknowledgments 5. Acknowledgments
This document contains many definitions taken from This document contains many definitions taken from an earlier
draft-ietf-adslmib-vdsl-07.txt. As such any credit for the text draft of the VDSL MIB [RFC3728]. As such any credit for the text
found within should be full attributed to the authors of that found within should be fully attributed to the authors of that
document. document.
6. Security Considerations 6. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-create. Such objects may be with a MAX-ACCESS clause of read-create. Such objects may be
considered sensitive or vulnerable in some network environments. considered sensitive or vulnerable in some network environments.
The support for SET operations in a non-secure environment without The support for SET operations in a non-secure environment without
proper protection can have a negative effect on network operations. proper protection can have a negative effect on network operations.
These are the tables and objects and their sensitivity/vulnerability:
Some of the readable objects in this MIB module (i.e., objects with a vdslLineSCMConfProfileBandTable
MAX-ACCESS other than not-accessible) may be considered sensitive or vdslLineSCMConfProfileBandUsage,
vulnerable in some network environments. vdslLineSCMConfProfileBandTransmitPSDLevel,
vdslLineSCMConfProfileBandSymbolRate,
vdslLineSCMConfProfileBandConstellationSize,
vdslLineSCMConfProfileBandCenterFrequency,
vdslLineSCMConfProfileBandRowStatus
VDSL layer connectivity from the Vtur will permit the subscriber to VDSL layer connectivity from the Vtur will permit the subscriber to
manipulate both the VDSL link directly and the VDSL embedded manipulate both the VDSL link directly and the VDSL embedded
operations channel (EOC) for their own loop. For example, unchecked operations channel (EOC) for their own loop. For example, unchecked
or unfiltered fluctuations initiated by the subscriber could generate or unfiltered fluctuations initiated by the subscriber could generate
sufficient notifications to potentially overwhelm either the sufficient notifications to potentially overwhelm either the
management interface to the network or the element manager. management interface to the network or the element manager.
Additionally, allowing write access to configuration data may allow Additionally, allowing write access to configuration data may allow
an end-user to increase their service levels or affect other an end-user to increase their service levels or affect other
end-users in either a positive or negative manner. For this reason, end-users in either a positive or negative manner. For this reason,
the following tables should be considered to contain sensitive the tables and objects listed above should be considered to contain
information: sensitive information.
- vdslLineSCMConfProfileTxBandTable Some of the readable objects in this MIB module (i.e., objects with a
- vdslSCMPhysBandTable MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending th
em over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
It is thus important to control even GET access to the objects within vdslLineSCMPhysBandUsage,
these tables and possibly to even encrypt the values of these objects vdslLineSCMPhysBandCurrPSDLevel,
when sending them over the network via SNMP. Not all versions of vdslLineSCMPhysBandCurrSymbolRate,
SNMP provide features for such a secure environment. vdslLineSCMPhysBandCurrConstellationSize,
vdslLineSCMPhysBandCurrCenterFrequency,
vdslLineSCMPhysBandCurrSnrMgn,
vdslLineSCMPhysBandCurrAtn
Read access of the physical band parameters may provide knowledge
to an end-user that would allow malicious behavior, for example
the application of an intentional interference on one or all of
the physical bands in use.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features 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
authentication and privacy). authentication and privacy).
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 is properly configured to give access to
defined in this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
7. IANA Considerations 7. IANA Considerations
The IANA is kindly requested to assign the value of the The IANA is kindly requested to assign the value of the
MODULE-IDENTITY. The authors suggest transmission 98, see section 4. MODULE-IDENTITY. The authors suggest transmission 227,
see section 4.
8. References 8. References
8.1. Normative References 8.1. Normative References
[DSLFTR57] DSL Forum TR-057, "VDSL Network Element Management", [DSLFTR57] DSL Forum TR-057, "VDSL Network Element Management",
February 2003. February 2003.
[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".
skipping to change at page 15, line 50 skipping to change at page 15, line 51
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.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
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
Conventions for Additional High Capacity Data Types",
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.
[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:
 End of changes. 

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