Network Working Group M. Dodge
Category: Internet Draft Infineon Technologies
B. Ray
PESA Switching Systems
March 2004
Definitions of Managed Object Extensions
for Very High Speed Digital Subscriber Lines (VDSL) Using
Single Carrier Modulation (SCM) Line Coding
draft-ietf-adslmib-vdsl-ext-scm-02.txt
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at:
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at:
http://www.ietf.org/shadow.html.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract
This document defines a portion of the Management Information Base
(MIB) module for use with network management protocols in the
Internet community. In particular, it describes objects used for
managing the Line Code Specific parameters of Very High Speed
Digital Subscriber Line (VDSL) interfaces using Single Carrier
Modulation (SCM) Line Coding. It is an optional extension to the
VDSL-LINE-MIB, RFC 3728 [RFC3728], which handles line code
independent objects.
Expires September 14, 2004 [Page 1]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
Table of Contents
1. The Internet-Standard Management Framework .................... 2
2. Overview ...................................................... 2
2.1 Relationship of this MIB Module to other MIB Modules . 2
2.2 Conventions used in the MIB Module ............................ 3
2.3 Structure ..................................................... 3
2.4 Persistence ................................................... 4
3. Conformance and Compliance .................................... 4
4. Definitions ................................................... 4
5. Security Considerations ....................................... 13
6. References .................................................... 14
6.1 Normative References .......................................... 14
6.2 Informative References ........................................ 15
7. Acknowledgements .............................................. 15
8. Authors' Addresses ............................................ 15
9. Full Copyright Statement ...................................... 16
1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a
MIB module that is compliant to the SMIv2, which is described in STD
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
2580 [RFC2580].
2. Overview
This document describes an SNMP MIB module for managing the line
code dependent (Physical Medium Dependent) Layer of SCM VDSL Lines.
These definitions are based upon the specifications for VDSL as
defined in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011,
T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. Additionally the
protocol-dependent (and line-code dependent) management framework
for VDSL lines specified by DSLF has been taken into consideration
[DSLFTR057] and [DSLFWT096].
The MIB module is located in the MIB tree under MIB 2 transmission,
as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section
of this document.
2.1 Relationship of this MIB Module to other MIB Modules
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
Expires September 14, 2004 [Page 2]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section outlines the
relationship of this VDSL Line Extension MIB to the VDSL-LINE-MIB,
RFC 3728 [RFC3728].
2.2 Conventions used in the MIB Module
2.2.1 Naming Conventions
A. Vtuc -- (VTUC) transceiver at near (Central) end of line
B. Vtur -- (VTUR) transceiver at Remote end of line
C. Vtu -- One of either Vtuc or Vtur
D. Curr -- Current
F. Atn -- Attenuation
J. LCS -- Line Code Specific
K. Max -- Maximum
Q. Mgn -- Margin
S. PSD -- Power Spectral Density
T. Rx -- Receive
T. Snr -- Signal to Noise Ratio
U. Tx -- Transmit
2.3 Structure
The SCM VDSL Line Extension MIB contains the following MIB group:
o vdslSCMGroup :
This group supports MIB objects for defining configuration profiles
and for montioring individual bands of Single Carrier Modulation
(SCM) VDSL modems. It contains the following tables:
- vdslLineSCMConfProfileTxBandTable
- vdslSCMPhysBandTable
None, one or both objects in this group MAY be implemented for
SCM VDSL lines.
Figure 1, below, displays the relationship of the tables in the
vdslSCMGroup to the vdslGroup and to the ifEntry:
ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1)
vdslLineTableEntry (vdslLineCoding=SCM)
----> vdslPhysTableEntry 1:(0..2)
----> vdslSCMPhysBandTable 1:(0..6)
vdslLineConfProfileEntry(vdslLineConfProfileName)
----> vdslLineSCMConfProfileBandTable 1:(0..6)
Figure 1: Table Relationships
Expires September 14, 2004 [Page 3]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
When the object vdslLineCoding is set to SCM,
vdslLineConfProfileName is used as the index to
vdslLineSCMConfProfileBandTable. The existence of an entry in
any of the tables of the vdslSCMGroup is optional. None, some or
all of the vdslSCMGroup tables MAY be implemented for a particular
VDSL line entity using SCM line coding.
2.4 Persistence
All read-create objects defined in this MIB module SHOULD be stored
persistently. Following is an exhaustive list of these persistent
objects:
vdslSCMConfProfileBandId
vdslSCMConfProfileBandUsage
vdslSCMConfProfileBandCenterFrequency
vdslSCMConfProfileBandSymbolRate
vdslSCMConfProfileBandConstellationSize
vdslSCMConfProfileBandTransmitPSDLevel
vdslSCMConfProfileBandRowStatus
vdslSCMPhysBandId
vdslSCMPhysBandUsage
vdslSCMPhysBandCurrPSDLevel
vdslSCMPhysBandCurrSymbolRate
vdslSCMPhysBandCurrConstellationSize
vdslSCMPhysBandCurrCenterFrequency
vdslSCMPhysBandPerformanceBandId
vdslSCMPhysBandPerformanceBandUsage
vdslSCMPhysBandPerformanceBandSnrMgn
vdslSCMPhysBandPerformanceBandAtn
It SHOULD also be noted that interface indices in this MIB are
maintained persistently. VACM data relating to these SHOULD be
stored persistently as well [RFC2575].
3. Conformance and Compliance
For SCM VDSL lines, the following group is optional:
- vdslSCMGroup
4. Definitions
VDSL-LINE-EXT-SCM-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
Integer32,
Unsigned32 FROM SNMPv2-SMI -- [RFC2578]
Expires September 14, 2004 [Page 4]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
RowStatus FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE,
OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
ifIndex FROM IF-MIB -- [RFC2863]
vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728]
vdslExtSCMMIB MODULE-IDENTITY
LAST-UPDATED "200403140000Z" -- March 14, 2004
ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed
Sand Channel Systems
Postal: P.O. Box 37324
Raleigh NC 27627-732
Email: sneedmike@hotmail.com
Phone: +1 206 600 7022
co-editor: Menachem Dodge
Infineon Technologies Savan Ltd.
6 Hagavish St.
Postal: Poleg Industrial Area,
Netanya 42504,
Israel.
Email: menachem.dodge@infineon.com
Phone: +972 9 892 4116
Co-editor: Bob Ray
PESA Switching Systems, Inc.
Postal: 330-A Wynn Drive
Huntsville, AL 35805
USA
Email: rray@pesa.com
Phone: +1 256 726 9200 ext. 142
"
DESCRIPTION
"The VDSL-LINE-MIB found in RFC 3728 defines objects for
the management of a pair of VDSL transceivers at each end of
the VDSL line. The VDSL-LINE-MIB configures and monitors the line
code independent parameters (TC layer) of the VDSL line.
This MIB module is an optional extension of the VDSL-LINE-MIB and
defines objects for configuration and monitoring of the line
code specific (LCS) elements (PMD layer) for VDSL lines using
SCM coding. The objects in this extension MIB MUST NOT be used
for VDSL lines using MCM line coding.
Naming Conventions:
Vtuc -- (VTUC) transceiver at near (Central) end of line
Vtur -- (VTUR) transceiver at Remote end of line
Vtu -- One of either Vtuc or Vtur
Curr -- Current
Expires September 14, 2004 [Page 5]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
Atn -- Attenuation
LCS -- Line Code Specific
Max -- Maximum
Mgn -- Margin
PSD -- Power Spectral Density
Rx -- Receive
Snr -- Signal to Noise Ratio
Tx -- Transmit
Copyright (C) The Internet Society (2004). This version
of this MIB module is part of RFC XXXX: see the RFC
itself for full legal notices."
-- RFC Ed.: replace XXXX with assigned number & remove this note
REVISION "200403140000Z" -- March 14, 2004
DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with assigned number & remove this note
::= { vdslMIB XX } -- To be assigned by IANA
-- RFC Ed.: we suggest to put it under { vdslMIB 2 } because
-- vdslMIB 1 is the VDSL-LINE-MIB, vdslMIB 2 is this SCM
-- extension MIB, while vdslMIB 3 is the MCM extension MIB.
vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslExtSCMMIB 1 }
vdslLineExtSCMMibObjects OBJECT IDENTIFIER ::=
{ vdslLineExtSCMMib 1 }
--
-- Single carrier modulation (SCM) configuration profile tables
--
vdslLineSCMConfProfileBandTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineSCMConfProfileBandEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains transmit band descriptor configuration
information for a VDSL line. Each entry in this table
reflects the configuration for one of possibly many bands
of a single carrier modulation (SCM) VDSL line.
These entries are defined by a manager and can be used to
configure the VDSL line."
::= { vdslLineExtSCMMibObjects 1 }
vdslLineSCMConfProfileBandEntry OBJECT-TYPE
SYNTAX VdslLineSCMConfProfileBandEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry consists of a list of parameters that
represents the configuration of a single carrier
modulation VDSL modem transmit band.
A default profile with an index of 'DEFVAL', will
Expires September 14, 2004 [Page 6]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
always exist and its parameters will be set to vendor
specific values, unless otherwise specified in this
document."
INDEX { vdslLineConfProfileName,
vdslLineSCMConfProfileBandId }
::= { vdslLineSCMConfProfileBandTable 1 }
VdslLineSCMConfProfileBandEntry ::=
SEQUENCE
{
vdslLineSCMConfProfileBandId INTEGER,
vdslLineSCMConfProfileBandUsage INTEGER,
vdslLineSCMConfProfileBandCenterFrequency Unsigned32,
vdslLineSCMConfProfileBandSymbolRate Unsigned32,
vdslLineSCMConfProfileBandConstellationSize Unsigned32,
vdslLineSCMConfProfileBandTransmitPSDLevel Unsigned32,
vdslLineSCMConfProfileBandRowStatus RowStatus
}
vdslLineSCMConfProfileBandId OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The BandId for this entry, which specifies which band
is being referred to. Specified as an INTEGER, the five
possible values are:
optionalBand(1),
1D(2),
1U(3),
2D(4),
2U(5)"
::= { vdslLineSCMConfProfileBandEntry 1 }
vdslLineSCMConfProfileBandUsage OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Indicates whether this band is in use.
Specified as an INTEGER, the two
possible values are:
Unused(1),
InUse(2)"
::= { vdslLineSCMConfProfileBandEntry 2 }
Expires September 14, 2004 [Page 7]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
vdslLineSCMConfProfileBandCenterFrequency OBJECT-TYPE
SYNTAX Unsigned32
UNITS "Hz"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the center frequency in Hz"
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileBandEntry 3 }
vdslLineSCMConfProfileBandSymbolRate OBJECT-TYPE
SYNTAX Unsigned32
UNITS "baud"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The requested symbol rate in baud."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileBandEntry 4 }
vdslLineSCMConfProfileBandConstellationSize OBJECT-TYPE
SYNTAX Unsigned32 (0..16)
UNITS "log2"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the constellation size."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileBandEntry 5 }
vdslLineSCMConfProfileBandTransmitPSDLevel OBJECT-TYPE
SYNTAX Unsigned32
UNITS "-0.25 dBm/Hz"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The requested transmit power spectral density for the VDSL
modem. The Actual value in -0.25 dBm/Hz."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileBandEntry 6 }
vdslLineSCMConfProfileBandRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to create a new row or modify or
delete an existing row in this table.
A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile.
Expires September 14, 2004 [Page 8]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced
from all associated lines."
::= { vdslLineSCMConfProfileBandEntry 7 }
--
-- SCM physical band
--
vdslLineSCMPhysBandTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineSCMPhysBandEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provides one row for each SCM Vtu band. This
table is read only as it reflects the current physical
parameters of each band."
::= { vdslLineExtSCMMibObjects 2 }
vdslLineSCMPhysBandEntry OBJECT-TYPE
SYNTAX VdslLineSCMPhysBandEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the vdslLineSCMPhysBandTable."
INDEX { ifIndex,
vdslLineSCMPhysBandId }
::= { vdslLineSCMPhysBandTable 1 }
VdslLineSCMPhysBandEntry ::=
SEQUENCE
{
vdslLineSCMPhysBandId INTEGER,
vdslLineSCMPhysBandUsage INTEGER,
vdslLineSCMPhysBandCurrCenterFrequency Unsigned32,
vdslLineSCMPhysBandCurrSymbolRate Unsigned32,
vdslLineSCMPhysBandCurrConstellationSize Unsigned32,
vdslLineSCMPhysBandCurrPSDLevel Unsigned32,
vdslLineSCMPhysBandCurrSnrMgn Integer32,
vdslLineSCMPhysBandCurrAtn Unsigned32
}
Expires September 14, 2004 [Page 9]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
vdslLineSCMPhysBandId OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The BandId for this entry, which specifies which band
is being referred to. Specified as an INTEGER, the five
possible values are:
optionalBand(1),
1D(2),
1U(3),
2D(4),
2U(5)"
::= { vdslLineSCMPhysBandEntry 1 }
vdslLineSCMPhysBandUsage OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Indicates whether this band is in use.
Specified as an INTEGER, the two
possible values are:
Unused(1),
InUse(2)"
::= { vdslLineSCMPhysBandEntry 2 }
vdslLineSCMPhysBandCurrCenterFrequency OBJECT-TYPE
SYNTAX Unsigned32
UNITS "Hz"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current center frequency in Hz for this band."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMPhysBandEntry 3 }
vdslLineSCMPhysBandCurrSymbolRate OBJECT-TYPE
SYNTAX Unsigned32
UNITS "baud"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current value of the symbol rate in baud for this
band."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMPhysBandEntry 4 }
Expires September 14, 2004 [Page 10]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
vdslLineSCMPhysBandCurrConstellationSize OBJECT-TYPE
SYNTAX Unsigned32 (0..16)
UNITS "log2"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current constellation size on this band."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMPhysBandEntry 5 }
vdslLineSCMPhysBandCurrPSDLevel OBJECT-TYPE
SYNTAX Unsigned32
UNITS "- 0.25 dBm/Hz"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The transmit power spectral density for the
VDSL modem."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMPhysBandEntry 6 }
vdslLineSCMPhysBandCurrSnrMgn OBJECT-TYPE
SYNTAX Integer32
UNITS "0.25 dBm"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Noise margin as seen by this Vtu and band with respect
to its received signal in 0.25 dB."
::= { vdslLineSCMPhysBandEntry 7 }
vdslLineSCMPhysBandCurrAtn OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
UNITS "0.25 dBm"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Measured difference in the total power transmitted by
the peer Vtu on this band and the total power received
by this Vtu on this band in 0.25 dB."
::= { vdslLineSCMPhysBandEntry 8 }
-- conformance information
vdslLineExtSCMConformance OBJECT IDENTIFIER ::=
{ vdslLineExtSCMMib 2 }
vdslLineExtSCMGroups OBJECT IDENTIFIER ::=
{ vdslLineExtSCMConformance 1 }
vdslLineExtSCMCompliances OBJECT IDENTIFIER ::=
{ vdslLineExtSCMConformance 2 }
Expires September 14, 2004 [Page 11]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
vdslLineExtSCMMibCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which
manage VDSL interfaces."
MODULE -- this module
MANDATORY-GROUPS
{
vdslLineExtSCMGroup
}
::= { vdslLineExtSCMCompliances 1 }
-- units of conformance
vdslLineExtSCMGroup OBJECT-GROUP
OBJECTS
{
vdslLineSCMConfProfileBandId,
vdslLineSCMConfProfileBandUsage,
vdslLineSCMConfProfileBandTransmitPSDLevel,
vdslLineSCMConfProfileBandSymbolRate,
vdslLineSCMConfProfileBandConstellationSize,
vdslLineSCMConfProfileBandCenterFrequency,
vdslLineSCMConfProfileBandRowStatus,
vdslLineSCMPhysBandId,
vdslLineSCMPhysBandUsage,
vdslLineSCMPhysBandCurrPSDLevel,
vdslLineSCMPhysBandCurrSymbolRate,
vdslLineSCMPhysBandCurrConstellationSize,
vdslLineSCMPhysBandCurrCenterFrequency,
vdslLineSCMPhysBandCurrSnrMgn,
vdslLineSCMPhysBandCurrAtn
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration
information for a VDSL line based upon single carrier
modulation modem."
::= { vdslLineExtSCMGroups 1 }
END
Expires September 14, 2004 [Page 12]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
5. Security Considerations
There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments.
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:
- vdslLineSCMConfProfileTxBandTable
- vdslSCMPhysBandTable
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.
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 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
Expires September 14, 2004 [Page 13]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
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",
February 2003.
[DSLFWT096] DSL Forum WT-096, "SCM Specific Managed Objects In
VDSL Network Elements".
[ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing
(TM); Access transmission systems on metallic access
cables; Very high speed Digital Subscriber Line (VDSL);
Part 1: Functional requirements", October 1999.
[ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing
(TM); Access transmission systems on metallic access
cables; Very high speed Digital Subscriber Line (VDSL);
Part 1: Transceiver specification", February 2001.
[ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line
foundation", November 2001.
[ITU9971] ITU-T G.997.1 "Physical layer management for Digital
Subscriber Line (DSL) Transceivers", July 1999.
[RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC
2493, January 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance 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 Group
MIB", RFC 2863, June 2000.
Expires September 14, 2004 [Page 14]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
[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
Very High Speed Digital Subscriber Lines (VDSL)", RFC
3728, February 2004.
[T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital
Subscriber Line (VDSL) Metallic Interface, Part 1:
Functional Requirements and Common Specification",
February 2001.
[T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2:
Technical Specification for a Single-Carrier Modulation
(SCM) Transceiver", November 2001.
[T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3:
Technical Specification for a Multi-Carrier Modulation
(MCM) Transceiver", November 2000.
6.2. Informative References
[RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
7. Acknowledgments
This document contains many definitions taken from
draft-ietf-adslmib-vdsl-07.txt. As such any credit for the text
found within should be full attributed to the authors of that
document.
8. Authors' Addresses
Menachem Dodge
Infineon Technologies Savan Ltd.
6 Hagavish St.
Poleg Industrial Area,
Expires September 14, 2004 [Page 15]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
Netanya 42504,
Israel.
Phone: +972 9 892 4116
Fax: +972 9 865 8756
Email: menachem.dodge@infineon.com
Bob Ray
PESA Switching Systems, Inc.
330-A Wynn Drive
Huntsville, AL 35805
USA
Phone: +1 256 726 9200 ext. 142
Fax: +1 256 726 9271
EMail: rray@pesa.com
9. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78 and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"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.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
Expires September 14, 2004 [Page 16]
INTERNET-DRAFT VDSL-LINE-EXT-SCM-MIB March 2004
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.
Expires September 14, 2004 [Page 17]
