draft-ietf-adslmib-vdsl-ext-scm-03.txt   draft-ietf-adslmib-vdsl-ext-scm-04.txt 
Network Working Group M. Dodge Network Working Group M. Dodge
Category: Internet Draft Infineon Technologies Category: Internet Draft Infineon Technologies
B. Ray B. Ray
PESA Switching Systems PESA Switching Systems
March 2004 May 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-03.txt draft-ietf-adslmib-vdsl-ext-scm-04.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 2, line 20 skipping to change at page 2, line 20
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 ....................................... 13
7. References .................................................... 14 7. References .................................................... 14
7.1 Normative References .......................................... 14 7.1 Normative References .......................................... 14
7.2 Informative References ........................................ 15 7.2 Informative References ........................................ 15
8. Authors' Addresses ............................................ 15 Authors' Addresses ............................................ 15
9. Full Copyright Statement ...................................... 16 Full Copyright Statement ...................................... 16
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 3, line 5 skipping to change at page 2, line 55
[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 the vdslMIB, which
in turn is found under MIB 2 transmission. The reader is referred to in turn is found under MIB 2 transmission. The reader is referred to
RFC 3728 [RFC3728] for further discussion of this subject. RFC 3728 [RFC3728] for further discussion of this subject.
The key words "MUST", "MUST NOT", "RECOMMENDED", and "SHOULD" in this
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
VDSL-LINE-MIB, RFC 3728 [RFC3728]. VDSL-LINE-MIB, RFC 3728 [RFC3728].
2.2 Conventions used in the MIB Module 2.2 Conventions used in the MIB Module
skipping to change at page 4, line 20 skipping to change at page 4, line 20
vdslLineConfProfileName is used as the index to vdslLineConfProfileName is used as the index to
vdslLineSCMConfProfileBandTable. The existence of an entry in vdslLineSCMConfProfileBandTable. The existence of an entry in
any of the tables of the vdslSCMGroup is optional. any of the tables of the vdslSCMGroup is optional.
2.4 Persistence 2.4 Persistence
All read-create objects defined in this MIB module SHOULD be stored All read-create objects defined in this MIB module SHOULD be stored
persistently. Following is an exhaustive list of these persistent persistently. Following is an exhaustive list of these persistent
objects: objects:
vdslSCMConfProfileBandId vdslLineSCMConfProfileBandId
vdslSCMConfProfileBandUsage vdslLineSCMConfProfileBandUsage
vdslSCMConfProfileBandCenterFrequency vdslLineSCMConfProfileBandCenterFrequency
vdslSCMConfProfileBandSymbolRate vdslLineSCMConfProfileBandSymbolRate
vdslSCMConfProfileBandConstellationSize vdslLineSCMConfProfileBandConstellationSize
vdslSCMConfProfileBandTransmitPSDLevel vdslLineSCMConfProfileBandTransmitPSDLevel
vdslSCMConfProfileBandRowStatus vdslLineSCMConfProfileBandRowStatus
vdslSCMPhysBandId vdslLineSCMPhysBandId
vdslSCMPhysBandUsage vdslLineSCMPhysBandUsage
vdslSCMPhysBandCurrPSDLevel vdslLineSCMPhysBandCurrPSDLevel
vdslSCMPhysBandCurrSymbolRate vdslLineSCMPhysBandCurrSymbolRate
vdslSCMPhysBandCurrConstellationSize vdslLineSCMPhysBandCurrConstellationSize
vdslSCMPhysBandCurrCenterFrequency vdslLineSCMPhysBandCurrCenterFrequency
vdslSCMPhysBandPerformanceBandId vdslLineSCMPhysBandPerformanceBandId
vdslSCMPhysBandPerformanceBandUsage vdslLineSCMPhysBandPerformanceBandUsage
vdslSCMPhysBandPerformanceBandSnrMgn vdslLineSCMPhysBandPerformanceBandSnrMgn
vdslSCMPhysBandPerformanceBandAtn vdslLineSCMPhysBandPerformanceBandAtn
Note also that the interface indices in this MIB are maintained Note also that the interface indices in this MIB are maintained
persistently. View-based Access Control Model (VACM) data persistently. View-based Access Control Model (VACM) data
relating to these SHOULD be stored persistently as well [RFC3415]. relating to these SHOULD be stored persistently as well [RFC3415].
3. Conformance and Compliance 3. Conformance and Compliance
An SCM based VDSL agent does not have to implement this MIB to be An SCM based VDSL agent does not have to implement this MIB to be
compliant with RFC 3728 [RFC3728]. If the SCM VDSL Line Extension compliant with RFC 3728 [RFC3728]. If the SCM VDSL Line Extension
MIB is implemented then the following group is mandatory: MIB is implemented then the following group is mandatory:
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 "200403300000Z" -- March 30, 2004 LAST-UPDATED "200405300000Z" -- May 30, 2004
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
Sand Channel Systems Sand Channel Systems
Postal: P.O. Box 37324 Postal: P.O. Box 37324
Raleigh NC 27627-732 Raleigh NC 27627-732
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
Phone: +1 206 600 7022 Phone: +1 206 600 7022
skipping to change at page 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 "200403300000Z" -- March 30, 2004 REVISION "200405300000Z" -- May 30, 2004
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
::= { vdslMIB XX } -- To be assigned by IANA ::= { vdslMIB XX } -- To be assigned by IANA
-- RFC Ed.: we suggest to put it under { vdslMIB 2 } because -- RFC Ed.: we suggest to put it under { vdslMIB 2 } because
-- vdslMIB 1 is the VDSL-LINE-MIB, vdslMIB 2 is this SCM -- vdslMIB 1 is the VDSL-LINE-MIB, vdslMIB 2 is this SCM
-- extension MIB, while vdslMIB 3 is the MCM extension MIB. -- extension MIB, while vdslMIB 3 is the MCM extension MIB.
vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslExtSCMMIB 1 } vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslExtSCMMIB 1 }
vdslLineExtSCMMibObjects OBJECT IDENTIFIER ::= vdslLineExtSCMMibObjects OBJECT IDENTIFIER ::=
{ vdslLineExtSCMMib 1 } { vdslLineExtSCMMib 1 }
skipping to change at page 7, line 38 skipping to change at page 7, line 38
vdslLineSCMConfProfileBandId Unsigned32, vdslLineSCMConfProfileBandId Unsigned32,
vdslLineSCMConfProfileBandUsage Unsigned32, vdslLineSCMConfProfileBandUsage Unsigned32,
vdslLineSCMConfProfileBandCenterFrequency Unsigned32, vdslLineSCMConfProfileBandCenterFrequency Unsigned32,
vdslLineSCMConfProfileBandSymbolRate Unsigned32, vdslLineSCMConfProfileBandSymbolRate Unsigned32,
vdslLineSCMConfProfileBandConstellationSize Unsigned32, vdslLineSCMConfProfileBandConstellationSize Unsigned32,
vdslLineSCMConfProfileBandTransmitPSDLevel Unsigned32, vdslLineSCMConfProfileBandTransmitPSDLevel Unsigned32,
vdslLineSCMConfProfileBandRowStatus RowStatus vdslLineSCMConfProfileBandRowStatus RowStatus
} }
vdslLineSCMConfProfileBandId OBJECT-TYPE vdslLineSCMConfProfileBandId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 { optionalBand(1),
firstDownstreamBand(2),
firstUpstreamBand(3),
secondDownstreamBand(4),
secondUpstreamBand(5),
thirdDownstreamBand(6),
thirdUpstreamBand(7)}
MAX-ACCESS read-create 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 Unsigned32, the five
possible values are: possible values are:
optionalBand(1), optionalBand(1), firstDownstreamBand(2),
1D(2), firstUpstreamBand(3), secondDownstreamBand(4),
1U(3), secondUpstreamBand(5), thirdDownstreamBand(6),
2D(4), thirdUpstreamBand(7)"
2U(5)"
::= { vdslLineSCMConfProfileBandEntry 1 } ::= { vdslLineSCMConfProfileBandEntry 1 }
vdslLineSCMConfProfileBandUsage OBJECT-TYPE vdslLineSCMConfProfileBandUsage OBJECT-TYPE
SYNTAX unsigned32 SYNTAX unsigned32
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 Unsigned32, the two
possible values are: possible values are:
Unused(1), Unused(1),
InUse(2)" InUse(2)"
skipping to change at page 10, line 10 skipping to change at page 10, line 11
vdslLineSCMPhysBandUsage Unsigned32, vdslLineSCMPhysBandUsage Unsigned32,
vdslLineSCMPhysBandCurrCenterFrequency Unsigned32, vdslLineSCMPhysBandCurrCenterFrequency Unsigned32,
vdslLineSCMPhysBandCurrSymbolRate Unsigned32, vdslLineSCMPhysBandCurrSymbolRate Unsigned32,
vdslLineSCMPhysBandCurrConstellationSize Unsigned32, vdslLineSCMPhysBandCurrConstellationSize Unsigned32,
vdslLineSCMPhysBandCurrPSDLevel Unsigned32, vdslLineSCMPhysBandCurrPSDLevel Unsigned32,
vdslLineSCMPhysBandCurrSnrMgn Integer32, vdslLineSCMPhysBandCurrSnrMgn Integer32,
vdslLineSCMPhysBandCurrAtn Unsigned32 vdslLineSCMPhysBandCurrAtn Unsigned32
} }
vdslLineSCMPhysBandId OBJECT-TYPE vdslLineSCMPhysBandId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 { optionalBand(1),
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 five is being referred to. Specified as an Unsigned32, the
possible values are: five possible values are:
optionalBand(1), optionalBand(1), firstDownstreamBand(2),
1D(2), firstUpstreamBand(3), secondDownstreamBand(4),
1U(3), secondUpstreamBand(5), thirdDownstreamBand(6),
2D(4), thirdUpstreamBand(7)"
2U(5)"
::= { vdslLineSCMPhysBandEntry 1 } ::= { vdslLineSCMPhysBandEntry 1 }
vdslLineSCMPhysBandUsage OBJECT-TYPE vdslLineSCMPhysBandUsage OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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:
skipping to change at page 15, line 49 skipping to change at page 15, line 49
7.2. Informative References 7.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 Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
8. 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
skipping to change at page 16, line 20 skipping to change at page 16, line 20
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
9. 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 on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
 End of changes. 

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