draft-ietf-adslmib-adsl2-07.txt   draft-ietf-adslmib-adsl2-08.txt 
Network Working Group M. Morgenstern Network Working Group M. Morgenstern
Internet-Draft M. Dodge Internet-Draft M. Dodge
Expires: October 27, 2006 ECI Telecom Ltd. Expires: December 13, 2006 ECI Telecom Ltd.
S. Baillie S. Baillie
U. Bonollo U. Bonollo
NEC Australia NEC Australia
April 25, 2006 June 11, 2006
Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2
(ADSL2) (ADSL2)
draft-ietf-adslmib-adsl2-07.txt draft-ietf-adslmib-adsl2-08.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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
skipping to change at page 1, line 38 skipping to change at page 1, line 38
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
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.
This Internet-Draft will expire on October 27, 2006. This Internet-Draft will expire on December 13, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document defines a Management Information Base (MIB) module for This document defines a Management Information Base (MIB) module for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes objects used for managing parameters of the particular, it describes objects used for managing parameters of the
"Asymmetric Digital Subscriber Line" family of interface types, "Asymmetric Digital Subscriber Line" family of interface types,
especially including ADSL, ADSL2, and ADSL2+. especially including ADSL, ADSL2, and ADSL2+.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . 3 1. The Internet-Standard Management Framework . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Relationship to other MIBs . . . . . . . . . . . . . . . 4 2.1. Relationship to other MIBs . . . . . . . . . . . . . . . 4
2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 6 2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 6
2.3. Conventions Used in the MIB Module . . . . . . . . . . . 6 2.3. Conventions Used in the MIB Module . . . . . . . . . . . 6
2.4. Structure . . . . . . . . . . . . . . . . . . . . . . . . 13 2.4. Structure . . . . . . . . . . . . . . . . . . . . . . . . 12
2.5. Persistence . . . . . . . . . . . . . . . . . . . . . . . 15 2.5. Persistence . . . . . . . . . . . . . . . . . . . . . . . 15
2.6. Line Topology . . . . . . . . . . . . . . . . . . . . . . 18 2.6. Line Topology . . . . . . . . . . . . . . . . . . . . . . 17
2.7. Counters, Interval Buckets, and Thresholds . . . . . . . 18 2.7. Counters, Interval Buckets, and Thresholds . . . . . . . 18
2.8. Profiles . . . . . . . . . . . . . . . . . . . . . . . . 20 2.8. Profiles . . . . . . . . . . . . . . . . . . . . . . . . 20
2.9. Notifications . . . . . . . . . . . . . . . . . . . . . . 24 2.9. Notifications . . . . . . . . . . . . . . . . . . . . . . 23
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 25 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 25
4. Implementation Analysis . . . . . . . . . . . . . . . . . . . 153 4. Implementation Analysis . . . . . . . . . . . . . . . . . . . 154
5. Security Considerations . . . . . . . . . . . . . . . . . . . 154 5. Security Considerations . . . . . . . . . . . . . . . . . . . 155
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 160 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 162
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 161 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 163
7.1. Normative References . . . . . . . . . . . . . . . . . . 161 7.1. Normative References . . . . . . . . . . . . . . . . . . 163
7.2. Informative References . . . . . . . . . . . . . . . . . 162 7.2. Informative References . . . . . . . . . . . . . . . . . 164
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 164 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 165
Intellectual Property and Copyright Statements . . . . . . . . . 165 Intellectual Property and Copyright Statements . . . . . . . . . 166
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 4, line 12 skipping to change at page 4, line 12
as G.997.1. That is, a MIB attribute whose REFERENCE section as G.997.1. That is, a MIB attribute whose REFERENCE section
provides a paragraph number in ITU-T G.997.1 is actually originated provides a paragraph number in ITU-T G.997.1 is actually originated
from either G.997.1 [G.997.1] or one of its amendment documents. from either G.997.1 [G.997.1] or one of its amendment documents.
Note that future revision of ITU-T G.997.1 standard will refer also Note that future revision of ITU-T G.997.1 standard will refer also
to next generation of VDSL technology, known as VDSL2, per ITU-T to next generation of VDSL technology, known as VDSL2, per ITU-T
G.993.2 [G.993.2]. However, managing VDSL2 lines is currently beyond G.993.2 [G.993.2]. However, managing VDSL2 lines is currently beyond
the scope of the MIB this document specifies. the scope of the MIB this document specifies.
The MIB module is located in the MIB tree under MIB 2 transmission, The MIB module is located in the MIB tree under MIB 2 transmission,
as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of as discussed in the IANA Considerations section of this document.
this document.
2.1. Relationship to other MIBs 2.1. Relationship to other MIBs
This section outlines the relationship of this MIB module with other This section outlines the relationship of this MIB module with other
MIB modules described in RFCs. Specifically, IF-MIB as presented in MIB modules described in RFCs. Specifically, IF-MIB as presented in
RFC 2863 [RFC2863] is discussed. RFC 2863 [RFC2863] is discussed.
2.1.1. General IF-MIB Integration (RFC 2863) 2.1.1. General IF-MIB Integration (RFC 2863)
The ADSL2 Line MIB specifies the detailed attributes of a data The ADSL2 Line MIB specifies the detailed attributes of a data
skipping to change at page 8, line 19 skipping to change at page 8, line 19
noPeerAtu (4) - Peer ATU not detected noPeerAtu (4) - Peer ATU not detected
otherCause (5) - Other initialization failure reason otherCause (5) - Other initialization failure reason
o Adsl2OperationModes: o Adsl2OperationModes:
Attributes with this syntax uniquely identify an ADSL mode, which Attributes with this syntax uniquely identify an ADSL mode, which
is a category associated with each transmission mode defined for is a category associated with each transmission mode defined for
the ADSL/ADSL2 or ADSL2+ link. Part of the line configuration the ADSL/ADSL2 or ADSL2+ link. Part of the line configuration
profile depends on the ADSL Mode: profile depends on the ADSL Mode:
defMode (1), - The default/generic PSD configuration. Specified as an enumeration construct, there are currently a few
The default configuration will be used dozen transmission modes in the list.
when no other matching mode specific
configuration can be found.
adsl (2), - ADSL (POTS or ISDN)
adsl2Pots (3), - ADSL2 (ISDN)
adsl2Isdn (4), - ADSL2 (ISDN)
adsl2PlusPots (5), - ADSL2+ (POTS)
adsl2PlusIsdn (6), - ADSL2+ (ISDN)
adsl2ReachExtended (7)- Reach Extended ADSL2
o Adsl2PowerMngState: o Adsl2PowerMngState:
Attributes with this syntax uniquely identify each power Attributes with this syntax uniquely identify each power
management state defined for the ADSL/ADSL2 or ADSL2+ link: management state defined for the ADSL/ADSL2 or ADSL2+ link:
l0(1) - L0 - Full power management state l0(1) - L0 - Full power management state
l1(2) - L1 - Low power management state (for G.992.2) l1(2) - L1 - Low power management state (for G.992.2)
l2(3) - L2 - Low power management state (for G.992.3, l2(3) - L2 - Low power management state (for G.992.3,
G.992.4, and G.992.5) G.992.4, and G.992.5)
skipping to change at page 24, line 9 skipping to change at page 23, line 49
the adsl2ChannelStatusTable, and adsl2PMChCurrTable tables for the adsl2ChannelStatusTable, and adsl2PMChCurrTable tables for
that line. that line.
o When the number of bearer channels for a DSL line changes to a o When the number of bearer channels for a DSL line changes to a
lower number, the SNMP agent will automatically destroy rows in lower number, the SNMP agent will automatically destroy rows in
the adsl2ChannelStatusTable, the adsl2ChannelStatusTable,
adsl2PMChCurrTable,adsl2PMChHist15MinTable and adsl2PMChCurrTable,adsl2PMChHist15MinTable and
adsl2PMChHist1DTable tables for that line. adsl2PMChHist1DTable tables for that line.
2.9. Notifications 2.9. Notifications
The ability to generate the SNMP notifications coldStart/WarmStart The ability to generate the SNMP notifications coldStart/warmStart
(per [RFC3418]), which are per agent (e.g., per Digital Subscriber (per [RFC3418]), which are per agent (e.g., per Digital Subscriber
Line Access Multiplexer, or DSLAM, in such a device), and linkUp/ Line Access Multiplexer, or DSLAM, in such a device), and linkUp/
linkDown (per [RFC2863]), which are per interface (i.e., ADSL/ADSL2 linkDown (per [RFC2863]), which are per interface (i.e., ADSL/ADSL2
or ADSL2+ line) is required. or ADSL2+ line) is REQUIRED.
A linkDown notification MAY be generated whenever any of ES, SES, CRC A linkDown notification MAY be generated whenever any of ES, SES, CRC
Anomaly, LOS, LOF, or UAS event occurs. The corresponding linkUp Anomaly, LOS, LOF, or UAS event occurs. The corresponding linkUp
notification MAY be sent when all link failure conditions are notification MAY be sent when all link failure conditions are
cleared. cleared.
The notifications defined in this MIB module are for status change The notifications defined in this MIB module are for status change
(e.g., initialization failure) and for the threshold crossings (e.g., initialization failure) and for the threshold crossings
associated with the following events: Full initialization failures, associated with the following events: Full initialization failures,
short initialization failures, ES, SES, FEC Seconds, LOS Seconds, short initialization failures, ES, SES, FEC Seconds, LOS Seconds,
skipping to change at page 25, line 34 skipping to change at page 25, line 25
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
transmission transmission
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
adsl2TCMIB MODULE-IDENTITY adsl2TCMIB MODULE-IDENTITY
LAST-UPDATED "200604250000Z" - April 25, 2006 LAST-UPDATED "200606110000Z" -- June 11, 2006
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 26, line 45 skipping to change at page 26, line 37
DESCRIPTION DESCRIPTION
"This MIB Module provides Textual Conventions to be "This MIB Module provides Textual Conventions to be
used by the ADSL2-LINE-MIB module for the purpose of used by the ADSL2-LINE-MIB module for the purpose of
managing ADSL, ADSL2 and ADSL2+ lines. managing ADSL, ADSL2 and ADSL2+ lines.
Copyright (C) The Internet Society (2006). This version of Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC XXXX: see the RFC itself for this MIB module is part of RFC XXXX: see the RFC itself for
full legal notices." full legal notices."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
REVISION "200604250000Z" -- April 25, 2006 REVISION "200606110000Z" -- June 11, 2006
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 xxx 2} -- adsl2MIB 2 ::= { transmission xxx 2} -- adsl2MIB 2
-- IANA, the xxx here must be the same as the one assigned -- IANA, the xxx here must be the same as the one assigned
-- to the adsl2MIB below. -- to the adsl2MIB below.
-- RFC Ed.: Please fill in xxx once assigned by IANA. -- RFC Ed.: Please fill in xxx once assigned by IANA.
------------------------------------------------ ------------------------------------------------
-- Textual Conventions -- -- Textual Conventions --
------------------------------------------------ ------------------------------------------------
skipping to change at page 28, line 49 skipping to change at page 28, line 41
Bit 46 : G.992.5 Annex I All-Digital non-overlapped (F) Bit 46 : G.992.5 Annex I All-Digital non-overlapped (F)
Bit 47 : G.992.5 Annex I All-Digital overlapped (F) Bit 47 : G.992.5 Annex I All-Digital overlapped (F)
Bit 48 : G.992.5 Annex J All-Digital non-overlapped (F) Bit 48 : G.992.5 Annex J All-Digital non-overlapped (F)
Bit 49 : G.992.5 Annex J All-Digital overlapped (F) Bit 49 : G.992.5 Annex J All-Digital overlapped (F)
Bit 50 : G.992.5 Annex M POTS non-overlapped (F) Bit 50 : G.992.5 Annex M POTS non-overlapped (F)
Bit 51 : G.992.5 Annex M POTS overlapped (F) Bit 51 : G.992.5 Annex M POTS overlapped (F)
Bit 52-55: Reserved" Bit 52-55: Reserved"
SYNTAX BITS { SYNTAX BITS {
ansit1413(0), ansit1413(0),
etsi(1), etsi(1),
q9921PotsNonOverlapped(2), g9921PotsNonOverlapped(2),
q9921PotsOverlapped(3), g9921PotsOverlapped(3),
q9921IsdnNonOverlapped(4), g9921IsdnNonOverlapped(4),
q9921isdnOverlapped(5), g9921isdnOverlapped(5),
q9921tcmIsdnNonOverlapped(6), g9921tcmIsdnNonOverlapped(6),
q9921tcmIsdnOverlapped(7), g9921tcmIsdnOverlapped(7),
q9922potsNonOverlapeed(8), g9922potsNonOverlapeed(8),
q9922potsOverlapped(9), g9922potsOverlapped(9),
q9922tcmIsdnNonOverlapped(10), g9922tcmIsdnNonOverlapped(10),
q9922tcmIsdnOverlapped(11), g9922tcmIsdnOverlapped(11),
q9921tcmIsdnSymmetric(12), g9921tcmIsdnSymmetric(12),
reserved1(13), reserved1(13),
reserved2(14), reserved2(14),
reserved3(15), reserved3(15),
reserved4(16), reserved4(16),
reserved5(17), reserved5(17),
q9923PotsNonOverlapped(18), g9923PotsNonOverlapped(18),
q9923PotsOverlapped(19), g9923PotsOverlapped(19),
q9923IsdnNonOverlapped(20), g9923IsdnNonOverlapped(20),
q9923isdnOverlapped(21), g9923isdnOverlapped(21),
reserved6(22), reserved6(22),
reserved7(23), reserved7(23),
q9924potsNonOverlapeed(24), g9924potsNonOverlapeed(24),
q9924potsOverlapped(25), g9924potsOverlapped(25),
reserved8(26), reserved8(26),
reserved9(27), reserved9(27),
q9923AnnexIAllDigNonOverlapped(28), g9923AnnexIAllDigNonOverlapped(28),
q9923AnnexIAllDigOverlapped(29), g9923AnnexIAllDigOverlapped(29),
q9923AnnexJAllDigNonOverlapped(30), g9923AnnexJAllDigNonOverlapped(30),
q9923AnnexJAllDigOverlapped(31), g9923AnnexJAllDigOverlapped(31),
q9924AnnexIAllDigNonOverlapped(32), g9924AnnexIAllDigNonOverlapped(32),
q9924AnnexIAllDigOverlapped(33), g9924AnnexIAllDigOverlapped(33),
q9923AnnexLMode1NonOverlapped(34), g9923AnnexLMode1NonOverlapped(34),
q9923AnnexLMode2NonOverlapped(35), g9923AnnexLMode2NonOverlapped(35),
q9923AnnexLMode3Overlapped(36), g9923AnnexLMode3Overlapped(36),
q9923AnnexLMode4Overlapped(37), g9923AnnexLMode4Overlapped(37),
q9923AnnexMPotsNonOverlapped(38), g9923AnnexMPotsNonOverlapped(38),
q9923AnnexMPotsOverlapped(39), g9923AnnexMPotsOverlapped(39),
q9925PotsNonOverlapped(40), g9925PotsNonOverlapped(40),
q9925PotsOverlapped(41), g9925PotsOverlapped(41),
q9925IsdnNonOverlapped(42), g9925IsdnNonOverlapped(42),
q9925isdnOverlapped(43), g9925isdnOverlapped(43),
reserved10(44), reserved10(44),
reserved11(45), reserved11(45),
q9925AnnexIAllDigNonOverlapped(46), g9925AnnexIAllDigNonOverlapped(46),
q9925AnnexIAllDigOverlapped(47), g9925AnnexIAllDigOverlapped(47),
q9925AnnexJAllDigNonOverlapped(48), g9925AnnexJAllDigNonOverlapped(48),
q9925AnnexJAllDigOverlapped(49), g9925AnnexJAllDigOverlapped(49),
q9925AnnexMPotsNonOverlapped(50), g9925AnnexMPotsNonOverlapped(50),
q9925AnnexMPotsOverlapped(51), g9925AnnexMPotsOverlapped(51),
reserved12(52), reserved12(52),
reserved13(53), reserved13(53),
reserved14(54), reserved14(54),
reserved15(55) reserved15(55)
} }
Adsl2RaMode ::= TEXTUAL-CONVENTION Adsl2RaMode ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the rate adaptation behavior for the line. "Specifies the rate adaptation behavior for the line.
skipping to change at page 31, line 4 skipping to change at page 30, line 43
paragraph 7.5.1.3" paragraph 7.5.1.3"
SYNTAX INTEGER { SYNTAX INTEGER {
noFail(0), noFail(0),
configError(1), configError(1),
configNotFeasible(2), configNotFeasible(2),
commFail(3), commFail(3),
noPeerAtu(4), noPeerAtu(4),
otherCause(5) otherCause(5)
} }
Adsl2OperationModes ::= TEXTUAL-CONVENTION Adsl2OperationModes ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ADSL2 management model specified includes an ADSL Mode "The ADSL2 management model specified includes an ADSL Mode
attribute which identifies an instance of ADSL Mode-Specific attribute which identifies an instance of ADSL Mode-Specific
PSD Configuration object in the ADSL Line Profile. The PSD Configuration object in the ADSL Line Profile. The
following classes of ADSL operating mode are defined. " following classes of ADSL operating mode are defined.
The notes (F) and (L) denote Full-Rate and Lite/splitterless
respectively:
+-------+--------------------------------------------------+
| Value | ADSL operation mode description |
+-------+--------------------------------------------------+
1 - The default/generic PSD configuration. Default
configuration will be used when no other matching
mode specific configuration can be found.
2 - ADSL family. The attributes included in the Mode-
Specific PSD Configuration are irrelevant for
ITU-T G.992.1 and G.992.2 ADSL modes. Hence, it
is possible to map those modes to this generic
class.
3-7 - Unused. Reserved for future ITU-T specification.
8 - G.992.3 POTS non-overlapped (F)
9 - G.992.3 POTS overlapped (F)
10 - G.992.3 ISDN non-overlapped (F)
11 - G.992.3 ISDN overlapped (F)
12-13 - Unused. Reserved for future ITU-T specification.
14 - G.992.4 POTS non-overlapped (L)
15 - G.992.4 POTS overlapped (L)
16-17 - Unused. Reserved for future ITU-T specification.
18 - G.992.3 Annex I All-Digital non-overlapped (F)
19 - G.992.3 Annex I All-Digital overlapped (F)
20 - G.992.3 Annex J All-Digital non-overlapped (F)
21 - G.992.3 Annex J All-Digital overlapped (F)
22 - G.992.4 Annex I All-Digital non-overlapped (L)
23 - G.992.4 Annex I All-Digital overlapped (L)
24 - G.992.3 Annex L POTS non-overlapped, mode 1,
wide U/S (F)
25 - G.992.3 Annex L POTS non-overlapped, mode 2,
narrow U/S(F)
26 - G.992.3 Annex L POTS overlapped, mode 3,
wide U/S (F)
27 - G.992.3 Annex L POTS overlapped, mode 4,
narrow U/S (F)
28 - G.992.3 Annex M POTS non-overlapped (F)
29 - G.992.3 Annex M POTS overlapped (F)
30 - G.992.5 POTS non-overlapped (F)
31 - G.992.5 POTS overlapped (F)
32 - G.992.5 ISDN non-overlapped (F)
33 - G.992.5 ISDN overlapped (F)
34-35 - Unused. Reserved for future ITU-T specification.
36 - G.992.5 Annex I All-Digital non-overlapped (F)
37 - G.992.5 Annex I All-Digital overlapped (F)
38 - G.992.5 Annex J All-Digital non-overlapped (F)
39 - G.992.5 Annex J All-Digital overlapped (F)
40 - G.992.5 Annex M POTS non-overlapped (F)
41 - G.992.5 Annex M POTS overlapped (F)
"
SYNTAX INTEGER { SYNTAX INTEGER {
defMode (1), defMode (1),
adsl (2), adsl (2),
adsl2Pots (3), g9923PotsNonOverlapped(8),
adsl2Isdn (4), g9923PotsOverlapped(9),
adsl2PlusPots (5), g9923IsdnNonOverlapped(10),
adsl2PlusIsdn (6), g9923isdnOverlapped(11),
adsl2ReachExtended (7) g9924potsNonOverlapeed(14),
g9924potsOverlapped(15),
g9923AnnexIAllDigNonOverlapped(18),
g9923AnnexIAllDigOverlapped(19),
g9923AnnexJAllDigNonOverlapped(20),
g9923AnnexJAllDigOverlapped(21),
g9924AnnexIAllDigNonOverlapped(22),
g9924AnnexIAllDigOverlapped(23),
g9923AnnexLMode1NonOverlapped(24),
g9923AnnexLMode2NonOverlapped(25),
g9923AnnexLMode3Overlapped(26),
g9923AnnexLMode4Overlapped(27),
g9923AnnexMPotsNonOverlapped(28),
g9923AnnexMPotsOverlapped(29),
g9925PotsNonOverlapped(30),
g9925PotsOverlapped(31),
g9925IsdnNonOverlapped(32),
g9925isdnOverlapped(33),
g9925AnnexIAllDigNonOverlapped(36),
g9925AnnexIAllDigOverlapped(37),
g9925AnnexJAllDigNonOverlapped(38),
g9925AnnexJAllDigOverlapped(39),
g9925AnnexMPotsNonOverlapped(40),
g9925AnnexMPotsOverlapped(41)
} }
Adsl2PowerMngState ::= TEXTUAL-CONVENTION Adsl2PowerMngState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Attributes with this syntax uniquely identify each power "Attributes with this syntax uniquely identify each power
management state defined for the ADSL/ADSL2 or ADSL2+ link. management state defined for the ADSL/ADSL2 or ADSL2+ link.
The possible values are: The possible values are:
l0(1) - L0 - Full power management state l0(1) - L0 - Full power management state
l1(2) - L1 - Low power management state (for G.992.2) l1(2) - L1 - Low power management state (for G.992.2)
skipping to change at page 40, line 31 skipping to change at page 41, line 49
Adsl2ChAtmStatus, Adsl2ChAtmStatus,
Adsl2ChPtmStatus Adsl2ChPtmStatus
FROM ADSL2-LINE-TC-MIB -- [This document] FROM ADSL2-LINE-TC-MIB -- [This document]
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
adsl2MIB MODULE-IDENTITY adsl2MIB MODULE-IDENTITY
LAST-UPDATED "200604250000Z" - April 25, 2006 LAST-UPDATED "200606110000Z" -- June 11, 2006
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 42, line 22 skipping to change at page 43, line 41
The MIB module is located in the MIB tree under MIB 2 The MIB module is located in the MIB tree under MIB 2
transmission, as discussed in the MIB-2 Integration (RFC 2863 transmission, as discussed in the MIB-2 Integration (RFC 2863
[RFC2863]) section of this document. [RFC2863]) section of this document.
Copyright (C) The Internet Society (2006). This version of Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC XXXX: see the RFC itself for this MIB module is part of RFC XXXX: see the RFC itself for
full legal notices." full legal notices."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
REVISION "200604250000Z" -- April 25, 2006 REVISION "200606110000Z" -- June 11, 2006
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
::= { transmission xxx } ::= { transmission xxx }
-- IANA, we suggest to put it under { transmission 230 } because -- IANA, we suggest to put it under { transmission 230 } because
-- this is the first available number. -- this is the first available number.
-- RFC Ed.: Please fill in xxx once assigned by IANA. -- RFC Ed.: Please fill in xxx once assigned by IANA.
adsl2 OBJECT IDENTIFIER ::= { adsl2MIB 1 } adsl2 OBJECT IDENTIFIER ::= { adsl2MIB 1 }
------------------------------------------------ ------------------------------------------------
adsl2Line OBJECT IDENTIFIER ::= { adsl2 1 } adsl2Line OBJECT IDENTIFIER ::= { adsl2 1 }
skipping to change at page 46, line 38 skipping to change at page 48, line 11
enabled through the adsl2LConfProfAtuTransSysEna object enabled through the adsl2LConfProfAtuTransSysEna object
in the line configuration profile being used for the in the line configuration profile being used for the
ADSL line, and where the selection of the actual ADSL line, and where the selection of the actual
operation-mode depends not only on the common operation-mode depends not only on the common
capabilities of both ATUs (as exchanged in G.994.1), but capabilities of both ATUs (as exchanged in G.994.1), but
also on achievable data rates under given loop also on achievable data rates under given loop
conditions. conditions.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE "ITU-T G.997.1, paragraph 7.3.1.1.10" REFERENCE "ITU-T G.997.1 (amendment 1), 7.3.1.1.10"
DEFVAL { false } DEFVAL { false }
::= { adsl2LineEntry 6 } ::= { adsl2LineEntry 6 }
adsl2LineStatusAtuTransSys OBJECT-TYPE adsl2LineStatusAtuTransSys OBJECT-TYPE
SYNTAX Adsl2TransmissionModeType SYNTAX Adsl2TransmissionModeType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ATU Transmission System (ATS) in use. "The ATU Transmission System (ATS) in use.
It is coded in a bit-map representation with one bit set to It is coded in a bit-map representation with one bit set to
skipping to change at page 66, line 14 skipping to change at page 67, line 34
"Actual Aggregate Transmit Power from the ATU (ATU-R on "Actual Aggregate Transmit Power from the ATU (ATU-R on
downstream direction and ATU-C on upstream direction), at the downstream direction and ATU-C on upstream direction), at the
instant of measurement. It ranges from -310 to 310 units of instant of measurement. It ranges from -310 to 310 units of
0.1 dB (Physical values are -31 to 31 dBm). A value of all 0.1 dB (Physical values are -31 to 31 dBm). A value of all
1's indicates the measurement is out of range to be 1's indicates the measurement is out of range to be
represented. represented.
This object reflects the value of the parameter following the This object reflects the value of the parameter following the
most recent DELT performed on the associated line. Once most recent DELT performed on the associated line. Once
the DELT process is over, the parameter no longer changes the DELT process is over, the parameter no longer changes
until the row is deleted or a new DELT process is initiated. " until the row is deleted or a new DELT process is initiated. "
REFERENCE "ITU-T G.997.1, paragraph 7.5.1.14 (ACTPSDds) REFERENCE "ITU-T G.997.1, paragraph 7.5.1.16 (ACTATPds)
and paragraph 7.5.1.15 (ACTPSDus)" and paragraph 7.5.1.17 (ACTATPus)"
::= { adsl2SCStatusEntry 18 } ::= { adsl2SCStatusEntry 18 }
adsl2SCStatusRowStatus OBJECT-TYPE adsl2SCStatusRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Row Status. The manager may create and delete rows "Row Status. The manager may create and delete rows
of this table. Please see the description of of this table. Please see the description of
adsl2SCStatusTable above for more details." adsl2SCStatusTable above for more details."
skipping to change at page 77, line 8 skipping to change at page 78, line 27
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Sub-carriers mask. A bitmap of 512 bits that allows masking "Sub-carriers mask. A bitmap of 512 bits that allows masking
up to 512 downstream sub-carriers, depending on NSCds. If bit up to 512 downstream sub-carriers, depending on NSCds. If bit
i (0 <= i < NSCds) is set to '1', the respective i (0 <= i < NSCds) is set to '1', the respective
downstream sub-carrier i is masked, and if set to '0', the downstream sub-carrier i is masked, and if set to '0', the
respective sub-carrier is unmasked. Note that there should respective sub-carrier is unmasked. Note that there should
always be unmasked sub-carriers (i.e., the object cannot be always be unmasked sub-carriers (i.e., the object cannot be
all 1's). Also note that if NSCds < 512, all bits all 1's). Also note that if NSCds < 512, all bits
i (NSCds i <= 512) should be set to '1'." i (NSCds < i <= 512) should be set to '1'."
REFERENCE "ITU-T G.997.1, paragraph 7.3.1.2.6" REFERENCE "ITU-T G.997.1, paragraph 7.3.1.2.6"
::= { adsl2LineConfProfEntry 2 } ::= { adsl2LineConfProfEntry 2 }
adsl2LConfProfScMaskUs OBJECT-TYPE adsl2LConfProfScMaskUs OBJECT-TYPE
SYNTAX Adsl2ScMaskUs SYNTAX Adsl2ScMaskUs
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Sub-carriers mask. A bitmap of 64 bits that allows masking "Sub-carriers mask. A bitmap of 64 bits that allows masking
up to 64 downstream sub-carriers, depending on NSCds. If up to 64 downstream sub-carriers, depending on NSCds. If
skipping to change at page 90, line 44 skipping to change at page 92, line 16
adsl2LConfProfPsdMaskSelectUs OBJECT-TYPE adsl2LConfProfPsdMaskSelectUs OBJECT-TYPE
SYNTAX Unsigned32(1..9) SYNTAX Unsigned32(1..9)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The selected upstream PSD mask. This parameter is used only "The selected upstream PSD mask. This parameter is used only
for annexes J and M of G.992.3 and G.992.5, and the same for annexes J and M of G.992.3 and G.992.5, and the same
selection is used for all relevant enabled bits in selection is used for all relevant enabled bits in
adsl2LConfProfAtuTransSysEna. " adsl2LConfProfAtuTransSysEna. "
REFERENCE "ITU-T G.997.1 (amendment 1), 7.3.1.10" REFERENCE "ITU-T G.997.1 (amendment 1), 7.3.1.2.10"
DEFVAL { 1 } DEFVAL { 1 }
::= { adsl2LineConfProfModeSpecEntry 9 } ::= { adsl2LineConfProfModeSpecEntry 9 }
adsl2LConfProfModeSpecRowStatus OBJECT-TYPE adsl2LConfProfModeSpecRowStatus OBJECT-TYPE
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 to modify or "This object is used to create a new row or to modify or
skipping to change at page 153, line 30 skipping to change at page 154, line 47
DESCRIPTION DESCRIPTION
"This group supports notifications of thresholds crossing "This group supports notifications of thresholds crossing
associated with ADSL2 lines." associated with ADSL2 lines."
::= { adsl2Groups 32 } ::= { adsl2Groups 32 }
END END
4. Implementation Analysis 4. Implementation Analysis
A management application intended to manage ADSL links (e.g., A management application intended to manage ADSL links (e.g.,
G.992.1) with this MIB module MUST be modified to adapt itself to G.992.1) with this MIB module must be modified to adapt itself to
certain differences between RFC 2662 [RFC2662] and this MIB module, certain differences between RFC 2662 [RFC2662] and this MIB module,
including the following aspects: including the following aspects:
o Though the configuration templates/profiles allow referring to 1-4 o Though the configuration templates/profiles allow referring to 1-4
bearer channels, ADSL links are limited to 2 channels at most bearer channels, ADSL links are limited to 2 channels at most
o Though the channel configuration profile allows higher data rates, o Though the channel configuration profile allows higher data rates,
ADSL links are limited to downstream/upstream data rate as assumed ADSL links are limited to downstream/upstream data rate as assumed
in RFC 2662 [RFC2662] in RFC 2662 [RFC2662]
o The Impulse Noise Protection (INP) configuration parameters are o The Impulse Noise Protection (INP) configuration parameters are
given by minimum protection and maximum delay parameters. given by minimum protection and maximum delay parameters.
skipping to change at page 161, line 4 skipping to change at page 162, line 27
authentication and privacy). authentication and privacy).
It is RECOMMENDED to deploy SNMPv3 and to enable cryptographic It is RECOMMENDED to deploy SNMPv3 and to enable cryptographic
security. It is then a customer/operator responsibility to ensure security. It is then a customer/operator responsibility to ensure
that the SNMP entity giving access to an instance of this MIB module that the SNMP entity giving access to an instance of this MIB module
is properly configured to give access only to those objects whose is properly configured to give access only to those objects whose
principals (users) have legitimate rights to indeed GET or SET principals (users) have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
6. Acknowledgments 6. Acknowledgments
The authors are deeply grateful to the authors of the HDSL2 LINE MIB The authors are deeply grateful to the authors of the HDSL2 LINE MIB
(RFC 4319), Clay Sikes and Bob Ray, for contributing to accelerating (RFC 4319), Clay Sikes and Bob Ray, for contributing to accelerating
the work on this document. The structure of this document as well as the work on this document. The structure of this document as well as
several paragraphs originate in their document. several paragraphs originate in their document.
Special thanks to Bert Wijnen for his meticuluos review of this text.
Other contributions and advice were received from the following: Other contributions and advice were received from the following:
Randy Presuhn (Mindspring)
Chen Jian (Huawei)
Bert Wijnen (Lucent) Bert Wijnen (Lucent)
Bob Ray (Pesa)
Chen Jian (Huawei)
Clay Sikes (Zhone) Clay Sikes (Zhone)
Mauro Molinari (Marconi)
Narendranath Nair (Wipro)
Randy Presuhn (Mindspring)
Veena Naidu (Wipro)
7. References 7. References
7.1. Normative References 7.1. Normative References
[G.992.1] "Asymmetric digital subscriber line (ADSL) transceivers", [G.992.1] "Asymmetric digital subscriber line (ADSL) transceivers",
ITU-T G.992.1, 1999. ITU-T G.992.1, 1999.
[G.992.2] "Splitterless asymmetric digital subscriber line (ADSL) [G.992.2] "Splitterless asymmetric digital subscriber line (ADSL)
transceivers", ITU-T G.992.2, 1999. transceivers", ITU-T G.992.2, 1999.
 End of changes. 34 change blocks. 
86 lines changed or deleted 158 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/