draft-ietf-adslmib-adslext-11.txt   rfc3440.txt 
INTERNET-DRAFT ADSL Line Extension MIB Faye Ly Network Working Group F. Ly
Pedestal Networks Request for Comments: 3440 Pedestal Networks
Gregory Bathrick Category: Standards Track G. Bathrick
Nokia Nokia
September 12, 2002 December 2002
Definitions of Extension Managed Objects Definitions of Extension Managed Objects
for Asymmetric Digital Subscriber Lines for Asymmetric Digital Subscriber Lines
September 12, 2002
draft-ietf-adslmib-adslext-11.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC2026. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Internet-Drafts are working documents of the Internet Engineering Official Protocol Standards" (STD 1) for the standardization state
Task Force (IETF), its areas, and its working groups. Note that other and status of this protocol. Distribution of this memo is unlimited.
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/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes additional managed objects used for In particular, it describes additional managed objects used for
managing Asymmetric Digital Subscriber Line (ADSL) interfaces not managing Asymmetric Digital Subscriber Line (ADSL) interfaces not
covered by the ADSL Line MIB [RFC2662]. covered by the ADSL Line MIB (RFC 2662).
1. The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events
for the purpose of management. The first version of this
Structure of Management Information (SMI) is called SMIv1
and described in STD 16, RFC 1155 [RFC1155], STD 16,
RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version,
called SMIv2, is described in STD 58, RFC 2578 [RFC2578],
STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
o Message protocols for transferring management information. Table of Contents
The first version of the SNMP message protocol is called
SNMPv1 and described in STD 15, RFC 1157[RFC1157]. A second
version of the SNMP message protocol, which is not an Internet
standards track protocol, is called SNMPv2c and described in RFC
1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the
message protocol is called SNMPv3 and described in RFC 1906
[RFC1906], RFC2572 [RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The 1. The Internet-Standard Management Framework ................. 2
first set of protocol operations and associated PDU formats is 2. Introduction ............................................... 2
described in STD 15, RFC 1157 [RFC1157]. A second set of protocol 3. Relationship of ADSL LINE EXTENSION MIB with standard MIBs . 2
operations and associated PDU formats is described in RFC 1905 4. Conventions used in the MIB ................................ 2
[RFC1905]. 5. Conformance and Compliance ................................. 6
6. Definitions ................................................ 6
7. Acknowledgments ............................................31
8. References .................................................31
9. Security Considerations ....................................32
10. Intellectual Property Notice ...............................34
11. Authors' Addresses .........................................35
12. Full Copyright Statement ...................................36
o A set of fundamental applications described in RFC 2573 1. The Internet-Standard Management Framework
[RFC2573] and the view-based access control mechanism described in
RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework For a detailed overview of the documents that describe the current
can be found in RFC 2570 [RFC2570]. Internet-Standard Management Framework, please refer to section 7 of
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. Objects in the MIB are the Management Information Base or MIB. MIB objects are generally
defined using the mechanisms defined in the SMI. accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
This memo specifies a MIB module that is compliant to the SMIv2. A Structure of Management Information (SMI). This memo specifies a MIB
MIB conforming to the SMIv1 can be produced through the appropriate module that is compliant to the SMIv2, which is described in STD 58,
translations. The resulting translated MIB must be semantically RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
equivalent, except where objects or events are omitted because no [RFC2580].
translation is possible (use of Counter64). Some machine-readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
2. Introduction 2. Introduction
The purpose of this memo is to define a supplemental set of managed The purpose of this memo is to define a supplemental set of managed
objects that is not covered by ADSL Line MIB as defined in [RFC2662]. objects that is not covered by the ADSL Line MIB as defined in
This memo addresses the additional objects defined in ITU G.997.1 [RFC2662]. This memo addresses the additional objects defined in ITU
[ITU G.997.1]. G.997.1 [ITU G.997.1].
3. Relationship of ADSL Line Extension MIB with standard MIBs 3. Relationship of ADSL Line Extension MIB with standard MIBs
This section outlines the relationship of ADSL Line Extension MIB This section outlines the relationship of the ADSL Line Extension MIB
with other MIBs described in RFCs and in their various degrees with other MIBs described in RFCs and in their various degrees of
of standardization. In regards to these relationship, the ADSL Line standardization. In regards to these relationships, the ADSL Line
Extension MIB follows conventions as used by the ADSL Line MIB with Extension MIB follows conventions as used by the ADSL Line MIB with
one exception. The value of the RFC2863 object, ifOperstatus, one exception. The value of the RFC 2863 object, ifOperstatus, SHALL
SHALL be down(2) when the ADSL line interface is in power state L3 as be down(2) when the ADSL line interface is in power state L3, as
defined in ITU G.992.1 [ITU G.992.1], which means no power. Its value defined in ITU G.992.1 [ITU G.992.1], which means no power. Its
shall be up(1) if the ADSL line interface is in power state L0 (power on) value shall be up(1) if the ADSL line interface is in power state L0
[ITU G.992.1] or L1 (reduced power). Power Status L2 [ITU G.992.1] is (power on) [ITU G.992.1] or L1 (reduced power). Power Status L2 [ITU
not applicable. G.992.1] is not applicable.
4. Conventions used in the MIB 4. Conventions used in the MIB
4.1 Structure 4.1 Structure
The MIB is organized to follow the same structure of the ADSL Line The MIB is organized to follow the same structure of the ADSL Line
MIB [RFC2662]. MIB [RFC2662].
4.2 Additional Managed Objects 4.2 Additional Managed Objects
Objects specific to the management of ADSL G.Lite as defined in Objects specific to the management of ADSL G.Lite as defined in ITU
ITU G.992.2 [ITU G.992.2] are: G.992.2 [ITU G.992.2] are:
- ADSL Transceiver Unit - Central Office End (ATU-C) - ADSL Transceiver Unit - Central Office End (ATU-C)
Transmission System and Line Mode Transmission System and Line Mode
- Power Management - Power Management
- Counters for Fast Retrains and Failed Fast Retrains - Counters for Fast Retrains and Failed Fast Retrains
- Counters for Severe Error Second-line and Unavailable Second - Counters for Severe Error Second-line and Unavailable Second
- Alternative profile configuration for the Dual line mode interface - Alternative profile configuration for the Dual line mode
interface
Besides the management of G.Lite, another object has been added in Besides the management of G.Lite, another object has been added in
order to manage the ADSL line profile. The object is the line mode order to manage the ADSL line profile. The object is the line mode
configuration. configuration.
4.2.1 ATU-C ADSL Transmission System Parameters and Line Mode 4.2.1 ATU-C ADSL Transmission System Parameters and Line Mode
The adslLineConfigTable needs to be extended to cover control of the The adslLineConfigTable needs to be extended to cover control of the
ATU-C ADSL Transmission system. Three objects are defined to monitor ATU-C ADSL Transmission system. Three objects are defined to monitor
and configure the transmission mode as well as the actual line mode: and configure the transmission mode as well as the actual line mode:
skipping to change at page 4, line 41 skipping to change at page 4, line 30
G.992.2 POTS non-overlapped G.Lite G.992.2 POTS non-overlapped G.Lite
G.992.2 POTS overlapped G.Lite G.992.2 POTS overlapped G.Lite
G.992.2 with TCM-ISDN G.Lite G.992.2 with TCM-ISDN G.Lite
non-overlapped non-overlapped
G.992.2 with TCM-ISDN overlapped G.Lite G.992.2 with TCM-ISDN overlapped G.Lite
G.992.1 TCM-ISDN symmetric Full G.992.1 TCM-ISDN symmetric Full
Table 1: Transmission Mode and Line Mode Table 1: Transmission Mode and Line Mode
In case more than one bit is configured for an ADSL interface and In case more than one bit is configured for an ADSL interface and
both Full and G.Lite modes are selected, the interface is said to both Full and G.Lite modes are selected, the interface is said to be
be configured in the dual mode. Only one bit can be set in the Actual configured in the dual mode. Only one bit can be set in the Actual
object that reflects the actual mode of transmission as well as the object that reflects the actual mode of transmission as well as the
line mode. line mode.
4.2.2 Power Management 4.2.2 Power Management
There are three possible power states for each managed ADSL interface There are three possible power states for each managed ADSL interface
operating in the G.Lite mode. L0 is power on, L1 is power on but operating in the G.Lite mode. L0 is power on, L1 is power on but
reduced and L3 is power off. Power state cannot be configured by an reduced and L3 is power off. Power state cannot be configured by an
operator but it can be viewed via the ifOperStatus object for the operator but it can be viewed via the ifOperStatus object for the
managed ADSL interface. The value of the object ifOperStatus is managed ADSL interface. The value of the object ifOperStatus is set
set to down(2) if the ADSL interface is in power state L3 and is set to down(2) if the ADSL interface is in power state L3 and is set to
to up(1) if the ADSL line interface is in power state L0 or L1. up(1) if the ADSL line interface is in power state L0 or L1.
An ADSL line power state, if the interface is operating in the An ADSL line power state, if the interface is operating in the G.Lite
G.Lite mode, can also be monitored by the adslLineGlitePowerState mode, can also be monitored by the adslLineGlitePowerState object
object defined in the ADSL Line Extension table. The value of the defined in the ADSL Line Extension table. The value of the object
object enumerates the three power states attainable by the managed enumerates the three power states attainable by the managed
interface. interface.
4.2.3 Fast Retrain Parameters 4.2.3 Fast Retrain Parameters
Section 7.4.15 [ITU G.997.1] specifies fast retrain parameters. Fast Section 7.4.15 [ITU G.997.1] specifies fast retrain parameters. Fast
retrain parameters include two counters: fast retrain count and failed retrain parameters include two counters: fast retrain count and
fast retrain count. These two counters have been added to all failed fast retrain count. These two counters have been added to all
performance tables. performance tables.
4.2.4 Counters for Severely Errored Second-line and Unavailable 4.2.4 Counters for Severely Errored Second-line and Unavailable
Seconds-line Seconds-line
ITU G.997.1 sections 6.2.1.1.7 and 6.2.1.1.9 specify two counters that ITU G.997.1 sections 6.2.1.1.7 and 6.2.1.1.9 specify two counters
are not covered by the ADSL Line MIB [RFC2662]. These two counters that are not covered by the ADSL Line MIB [RFC2662]. These two
(severely errored seconds-line and unavailable seconds-line) are added counters (severely errored seconds-line and unavailable seconds-line)
to all the performance tables. are added to all the performance tables.
Unavailable seconds counts cumulative number of seconds in which the Unavailable seconds counts the cumulative number of seconds in which
interface was unavailable during the measured period. This counter the interface was unavailable during the measured period. This
does not include the seconds in which unavailability was caused solely counter does not include the seconds in which unavailability was
by fast retrains and failed fast retrains. Fast retrains and failed caused solely by fast retrains and failed fast retrains. Fast
fast retrains are considered to be part of the normal network operation retrains and failed fast retrains are considered to be part of the
and thus are not counted as unavailable errors. normal network operation and thus are not counted as unavailable
errors.
4.2.5 Counters, Interval Buckets and Thresholds 4.2.5 Counters, Interval Buckets and Thresholds
For physical-level events, there are counters, current 15-minute and For physical-level events, there are counters, current 15-minute and
one (up to 96) 15-minute history bucket(s) of "interval-counters", as one (up to 96) 15-minute history bucket(s) of "interval-counters", as
well as current and previous 1-day interval-counters. Threshold well as current and previous 1-day interval-counters. Threshold
notification can be configured for each physical-layer current notification can be configured for each physical-layer current 15-
15-minute bucket. minute bucket.
There is no requirement for an agent to ensure fixed relationship There is no requirement for an agent to ensure fixed relationship
between the start of a fifteen minute and any wall clock; however between the start of a fifteen minute and any wall clock; however
some implementations may align the fifteen-minute intervals with some implementations may align the fifteen-minute intervals with
quarter hours. Likewise, an implementation may choose to align one quarter hours. Likewise, an implementation may choose to align one
day intervals with start of a day. day intervals with start of a day.
Separate tables are provided for the 96 interval-counters. They are Separate tables are provided for the 96 interval-counters. They are
indexed by {ifIndex, AdslAtu*IntervalNumber}. indexed by {ifIndex, AdslAtu*IntervalNumber}.
Counters are not reset when an ATU-C or ATU-R is reinitialized, only Counters are not reset when an ATU-C or ATU-R is reinitialized, only
when the agent is reset or reinitialized (or under specific request when the agent is reset or reinitialized (or under specific request
outside the scope of this MIB). outside the scope of this MIB).
The 15-minute event counters are of type PerfCurrentCount and The 15-minute event counters are of the type PerfCurrentCount and
PerfIntervalCount. The 1-day event counters are of type PerfIntervalCount. The 1-day event counters are of the type
AdslPerfCurrDayCount and AdslPerfPrevDayCount. Both 15-minute and 1- AdslPerfCurrDayCount and AdslPerfPrevDayCount. Both 15-minute and 1-
day time elapsed counters are of type AdslPerfTimeElapsed. day time elapsed counters are of the type AdslPerfTimeElapsed.
4.2.6 Alternative profile configuration for the dual line mode 4.2.6 Alternative profile configuration for the dual line mode interface
interface
The object, adslLineConfProfileDualLite, is used only when the interface The object, adslLineConfProfileDualLite, is used only when the
(the ADSL line and, if applicable, channel) is configured as dual mode, interface (the ADSL line and, if applicable, channel) is configured
that is, the object adslLineTransAtucConfig is configured with one or as dual mode, that is, the object adslLineTransAtucConfig is
more full-rate modes and one or more G.Lite modes. configured with one or more full-rate modes and one or more G.Lite
modes.
The object adslLineConfProfile defined in ADSL-MIB [RFC2662] is used as The object adslLineConfProfile defined in ADSL-MIB [RFC2662] is used
the primary full-rate profile. The newly added object in this MIB as the primary full-rate profile. The newly added object in this MIB
module, adslLineConfProfileDualLite, is used to describe and configure module, adslLineConfProfileDualLite, is used to describe and
the G.Lite profile. Note that if one or more full-rate modes are configure the G.Lite profile. Note that if one or more full-rate
configured, or only G.Lite modes are configured, only the original modes are configured, or only G.Lite modes are configured, only the
full-rate profile is needed. The dual-mode profile object is only original full-rate profile is needed. The dual-mode profile object
needed when both full-rate and G.Lite profiles are needed. In this is only needed when both full-rate and G.Lite profiles are needed.
case, it will be set to the value of adslLineConfProfile when 'dynamic' In this case, it will be set to the value of adslLineConfProfile when
profiles are implemented. 'dynamic' profiles are implemented.
When 'static' profiles are implemented, however, similar to the case When 'static' profiles are implemented, however, similar to the case
of the object, adslLineConfProfileName [RFC2662], this object's value of the object, adslLineConfProfileName [RFC2662], this object's value
will need to algorithmically represent the line. In this case, the will need to algorithmically represent the line. In this case, the
value of the line's ifIndex plus a value indicating the line mode type value of the line's ifIndex plus a value indicating the line mode
(e.g., G.Lite, Full-rate) will be used. Therefore, the profile's name type (e.g., G.Lite, Full-rate) will be used. Therefore, the
is a string of the concatenation of ifIndex and one of the follow profile's name is a string of the concatenation of the ifIndex and
values: Full or Lite. This string will be fixed-length (i.e., 14) with one of the following values: Full or Lite. This string will be
leading zero(s). For example, the profile name for ifIndex that fixed-length (i.e., 14) with leading zero(s). For example, the
equals '15' and is a full rate line, it will be '0000000015Full'. profile name for ifIndex that equals '15' and is a full rate line
will be '0000000015Full'.
5. Conformance and Compliance 5. Conformance and Compliance
See the conformance and compliance statements within the information See the conformance and compliance statements within the information
module. module.
6. Definitions 6. Definitions
ADSL-LINE-EXT-MIB DEFINITIONS ::= BEGIN ADSL-LINE-EXT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Counter32, Counter32,
Integer32, Integer32,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE FROM SNMPv2-SMI OBJECT-TYPE FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF
TEXTUAL-CONVENTION FROM SNMPv2-TC TEXTUAL-CONVENTION FROM SNMPv2-TC
PerfCurrentCount, PerfCurrentCount,
skipping to change at page 7, line 30 skipping to change at page 7, line 20
adslAturIntervalEntry, adslAturIntervalEntry,
adslAturPerfDataEntry, adslAturPerfDataEntry,
adslAtucIntervalEntry, adslAtucIntervalEntry,
adslAtucPerfDataEntry, adslAtucPerfDataEntry,
adslLineEntry, adslLineEntry,
adslMIB FROM ADSL-LINE-MIB adslMIB FROM ADSL-LINE-MIB
; ;
adslExtMIB MODULE-IDENTITY adslExtMIB MODULE-IDENTITY
LAST-UPDATED "200204231200Z" LAST-UPDATED "200212100000Z" -- 10 Dec 2002
ORGANIZATION "IETF ADSL MIB Working Group" ORGANIZATION "IETF ADSL MIB Working Group"
CONTACT-INFO CONTACT-INFO
" "
Faye Ly Faye Ly
Pedestal Networks Pedestal Networks
3045 Park Boulevard 6503 Dumbarton Circle,
Palo Alto, CA 94306 Fremont, CA 94555
Tel: +1 650-475-1274 Tel: +1 510-578-0158
Fax: +1 650-688-3119 Fax: +1 510-744-5152
E-Mail: faye@pedestalnetworks.com E-Mail: faye@pedestalnetworks.com
Gregory Bathrick Gregory Bathrick
NOKIA High Speed Access Nodes Nokia Networks
1310 Redwood Way, 2235 Mercury Way,
Petaluma, CA 94954 Fax: +1 707-535-7300
Tel: +1 707-793-7030
Fax: +1 707-792-0850
E-Mail: greg.bathrick@nokia.com E-Mail: greg.bathrick@nokia.com
IETF ADSL MIB Working Group
<XDSLMIB@LISTSERV.ECIRALEIGH.COM> General Discussion:adslmib@ietf.org
To Subscribe: https://www1.ietf.org/mailman/listinfo/adslmib
Archive: https://www1.ietf.org/mailman/listinfo/adslmib
" "
DESCRIPTION DESCRIPTION
"This MIB Module is a supplement to the ADSL-LINE-MIB "Copyright (C) The Internet Society (2002). This version of
this MIB module is part of RFC 3440; see the RFC itself for
full legal notices.
This MIB Module is a supplement to the ADSL-LINE-MIB
[RFC2662]." [RFC2662]."
REVISION "200204231200Z" REVISION "200212100000Z" -- 10 dec 2002
DESCRIPTION "Initial Version, published as RFC xxxx. This MIB DESCRIPTION "Initial Version, published as RFC 3440. This MIB
module supplements the ADSL-LINE-MIB [RFC2662]." module supplements the ADSL-LINE-MIB [RFC2662]."
::= { adslMIB 3 } ::= { adslMIB 3 }
adslExtMibObjects OBJECT IDENTIFIER ::= { adslExtMIB 1 } adslExtMibObjects OBJECT IDENTIFIER ::= { adslExtMIB 1 }
AdslTransmissionModeType ::= TEXTUAL-CONVENTION AdslTransmissionModeType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of ADSL line transmission modes, with one bit "A set of ADSL line transmission modes, with one bit
per mode. The notes (F) and (L) denote Full-Rate per mode. The notes (F) and (L) denote Full-Rate
skipping to change at page 10, line 24 skipping to change at page 10, line 20
SYNTAX AdslTransmissionModeType SYNTAX AdslTransmissionModeType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual transmission mode of the ATU-C. "The actual transmission mode of the ATU-C.
During ADSL line initialization, the ADSL During ADSL line initialization, the ADSL
Transceiver Unit - Remote terminal end (ATU-R) Transceiver Unit - Remote terminal end (ATU-R)
will determine the mode used for the link. will determine the mode used for the link.
This value will be limited a single transmission This value will be limited a single transmission
mode that is a subset of those modes enabled mode that is a subset of those modes enabled
by the ATU-C and denoted by adslLineTransAtucConfig. by the ATU-C and denoted by
After an initialization has occurred, its mode is adslLineTransAtucConfig. After an initialization
saved as the 'Current' mode and is persistence has occurred, its mode is saved as the 'Current'
should the link go down. This object returns 0 mode and is persistence should the link go
(i.e. BITS with no mode bit set) if the mode is down. This object returns 0 (i.e. BITS with no
not known." mode bit set) if the mode is not known."
REFERENCE "Section 7.3.2 ITU G.997.1 " REFERENCE "Section 7.3.2 ITU G.997.1 "
::= { adslLineExtEntry 3 } ::= { adslLineExtEntry 3 }
adslLineGlitePowerState OBJECT-TYPE adslLineGlitePowerState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(1), none(1),
l0(2), -- L0 Power on l0(2), -- L0 Power on
l1(3), -- L1 Power on but reduced l1(3), -- L1 Power on but reduced
l3(4) -- L3 Power off l3(4) -- L3 Power off
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object specifies the power "The value of this object specifies the power
state of this interface. L0 is power on, L1 is state of this interface. L0 is power on, L1 is
power on but reduced and L3 is power off. Power power on but reduced and L3 is power off. Power
state cannot be configured by an operator but it state cannot be configured by an operator but it
can be viewed via the ifOperStatus object for the can be viewed via the ifOperStatus object for the
managed ADSL interface. The value of the object managed ADSL interface. The value of the object
ifOperStatus is set to down(2) if the ADSL interface ifOperStatus is set to down(2) if the ADSL
is in power state L3 and is set to up(1) if the ADSL interface is in power state L3 and is set to up(1)
line interface is in power state L0 or L1. If the if the ADSL line interface is in power state L0 or
object adslLineTransAtucActual is set to a G.992.2 L1. If the object adslLineTransAtucActual is set to
(G.Lite)-type transmission mode, the value of a G.992.2 (G.Lite)-type transmission mode, the
this object will be one of the valid power value of this object will be one of the valid power
states: L0(2), L1(3), or L3(4). Otherwise, its states: L0(2), L1(3), or L3(4). Otherwise, its
value will be none(1)." value will be none(1)."
::= { adslLineExtEntry 4 } ::= { adslLineExtEntry 4 }
adslLineConfProfileDualLite OBJECT-TYPE adslLineConfProfileDualLite OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object extends the definition an ADSL line and "This object extends the definition an ADSL line and
associated channels (when applicable) for cases when associated channels (when applicable) for cases
it is configured in dual mode, and operating in a when it is configured in dual mode, and operating
G.Lite-type mode as denoted by in a G.Lite-type mode as denoted by
adslLineTransAtucActual. Dual mode exists when the adslLineTransAtucActual. Dual mode exists when the
object, adslLineTransAtucConfig, is configured with object, adslLineTransAtucConfig, is configured with
one or more full-rate modes and one or more G.Lite one or more full-rate modes and one or more G.Lite
modes simultaneously. modes simultaneously.
When 'dynamic' profiles are implemented, the value of When 'dynamic' profiles are implemented, the value
object is equal to the index of the applicable row in of object is equal to the index of the applicable
the ADSL Line Configuration Profile Table, row in the ADSL Line Configuration Profile Table,
AdslLineConfProfileTable defined in ADSL-MIB AdslLineConfProfileTable defined in ADSL-MIB
[RFC2662]. [RFC2662].
In the case when dual-mode has not been enabled, the In the case when dual-mode has not been enabled,
value of the object will be equal to the value of the the value of the object will be equal to the value
object adslLineConfProfile [RFC2662]. of the object adslLineConfProfile [RFC2662].
When `static' profiles are implemented, in much When `static' profiles are implemented, in much
like the case of the object, adslLineConfProfileName like the case of the object,
[RFC2662], this object's value will need to adslLineConfProfileName [RFC2662], this object's
algorithmically represent the characteristics of the value will need to algorithmically represent the
line. In this case, the value of the line's ifIndex characteristics of the line. In this case, the
plus a value indicating the line mode type value of the line's ifIndex plus a value indicating
(e.g., G.Lite, Full-rate) will be used. Therefore, the line mode type (e.g., G.Lite, Full-rate) will
the profile's name is a string concatenating the be used. Therefore, the profile's name is a string
ifIndex and one of the follow values: Full or Lite. concatenating the ifIndex and one of the follow
This string will be fixed-length (i.e., 14) with values: Full or Lite. This string will be
leading zero(s). For example, the profile name for fixed-length (i.e., 14) with leading zero(s). For
ifIndex that equals '15' and is a full rate line, it example, the profile name for ifIndex that equals
will be '0000000015Full'." '15' and is a full rate line, it will be
'0000000015Full'."
REFERENCE "Section 5.4 Profiles, RFC 2662" REFERENCE "Section 5.4 Profiles, RFC 2662"
::= { adslLineExtEntry 5 } ::= { adslLineExtEntry 5 }
adslAtucPerfDataExtTable OBJECT-TYPE adslAtucPerfDataExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslAtucPerfDataExtEntry SYNTAX SEQUENCE OF AdslAtucPerfDataExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table extends adslAtucPerfDataTable [RFC2662] "This table extends adslAtucPerfDataTable [RFC2662]
with additional ADSL physical line counter with additional ADSL physical line counter
information such as unavailable seconds-line and information such as unavailable seconds-line and
severely errored seconds-line." severely errored seconds-line."
::= { adslExtMibObjects 18 } ::= { adslExtMibObjects 18 }
skipping to change at page 14, line 17 skipping to change at page 14, line 15
REFERENCE "ITU G.997.1 Section 7.4.15.1 " REFERENCE "ITU G.997.1 Section 7.4.15.1 "
::= { adslAtucPerfDataExtEntry 5 } ::= { adslAtucPerfDataExtEntry 5 }
adslAtucPerfCurr15MinFailedFastR OBJECT-TYPE adslAtucPerfCurr15MinFailedFastR OBJECT-TYPE
SYNTAX PerfCurrentCount SYNTAX PerfCurrentCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For the current 15-minute interval, "For the current 15-minute interval,
adslAtucPerfCurr15MinFailedFastR reports the current adslAtucPerfCurr15MinFailedFastR reports the
number of seconds during which there have been current number of seconds during which there
failed fast retrains." have been failed fast retrains."
REFERENCE "ITU G.997.1 Section 7.4.15.2 " REFERENCE "ITU G.997.1 Section 7.4.15.2 "
::= { adslAtucPerfDataExtEntry 6 } ::= { adslAtucPerfDataExtEntry 6 }
adslAtucPerfCurr15MinSesL OBJECT-TYPE adslAtucPerfCurr15MinSesL OBJECT-TYPE
SYNTAX PerfCurrentCount SYNTAX PerfCurrentCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For the current 15-minute interval, "For the current 15-minute interval,
skipping to change at page 16, line 27 skipping to change at page 16, line 25
were fast retrains." were fast retrains."
REFERENCE "ITU G.997.1 Section 7.4.15.1 " REFERENCE "ITU G.997.1 Section 7.4.15.1 "
::= { adslAtucPerfDataExtEntry 13 } ::= { adslAtucPerfDataExtEntry 13 }
adslAtucPerfPrev1DayFailedFastR OBJECT-TYPE adslAtucPerfPrev1DayFailedFastR OBJECT-TYPE
SYNTAX AdslPerfPrevDayCount SYNTAX AdslPerfPrevDayCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For the previous day, adslAtucPerfPrev1DayFailedFastR "For the previous day,
reports the number of seconds during which there adslAtucPerfPrev1DayFailedFastR reports the number
were failed fast retrains." of seconds during which there were failed fast
retrains."
REFERENCE "ITU G.997.1 Section 7.4.15.2 " REFERENCE "ITU G.997.1 Section 7.4.15.2 "
::= { adslAtucPerfDataExtEntry 14 } ::= { adslAtucPerfDataExtEntry 14 }
adslAtucPerfPrev1DaySesL OBJECT-TYPE adslAtucPerfPrev1DaySesL OBJECT-TYPE
SYNTAX AdslPerfPrevDayCount SYNTAX AdslPerfPrevDayCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For the previous day, adslAtucPerfPrev1DaySesL "For the previous day, adslAtucPerfPrev1DaySesL
skipping to change at page 22, line 41 skipping to change at page 22, line 40
adslLineConfProfileTable from the ADSL-LINE-MIB adslLineConfProfileTable from the ADSL-LINE-MIB
[RFC2662] by adding the ability to configure the [RFC2662] by adding the ability to configure the
ADSL physical line mode." ADSL physical line mode."
::= { adslExtMibObjects 22 } ::= { adslExtMibObjects 22 }
adslConfProfileExtEntry OBJECT-TYPE adslConfProfileExtEntry OBJECT-TYPE
SYNTAX AdslConfProfileExtEntry SYNTAX AdslConfProfileExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry extends the adslLineConfProfileEntry defined "An entry extends the adslLineConfProfileEntry
in [RFC2662]. Each entry corresponds to an ADSL line defined in [RFC2662]. Each entry corresponds to an
profile." ADSL line profile."
AUGMENTS { adslLineConfProfileEntry } AUGMENTS { adslLineConfProfileEntry }
::= { adslConfProfileExtTable 1 } ::= { adslConfProfileExtTable 1 }
AdslConfProfileExtEntry ::= AdslConfProfileExtEntry ::=
SEQUENCE { SEQUENCE {
adslConfProfileLineType INTEGER adslConfProfileLineType INTEGER
} }
adslConfProfileLineType OBJECT-TYPE adslConfProfileLineType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noChannel (1), -- no channels exist noChannel (1), -- no channels exist
fastOnly (2), -- only fast channel exists fastOnly (2), -- only fast channel exists
interleavedOnly (3), -- only interleaved channel interleavedOnly (3), -- only interleaved channel
-- exist -- exist
fastOrInterleaved (4),-- either fast or interleaved fastOrInterleaved (4),-- either fast or interleaved
-- channels can exist, but -- channels can exist, but
-- only one at any time -- only one at any time
fastAndInterleaved (5)-- both the fast channel and fastAndInterleaved (5)-- both the fast channel and
skipping to change at page 23, line 44 skipping to change at page 23, line 43
Value is noChannel(1). Value is noChannel(1).
" "
DEFVAL { fastOnly } DEFVAL { fastOnly }
::= { adslConfProfileExtEntry 1 } ::= { adslConfProfileExtEntry 1 }
adslAlarmConfProfileExtTable OBJECT-TYPE adslAlarmConfProfileExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslAlarmConfProfileExtEntry SYNTAX SEQUENCE OF AdslAlarmConfProfileExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table extends the adslLineAlarmConfProfileTable "This table extends the
and provides threshold parameters for all the adslLineAlarmConfProfileTable and provides
counters defined in this MIB module." threshold parameters for all the counters defined
in this MIB module."
::= { adslExtMibObjects 23 } ::= { adslExtMibObjects 23 }
adslAlarmConfProfileExtEntry OBJECT-TYPE adslAlarmConfProfileExtEntry OBJECT-TYPE
SYNTAX AdslAlarmConfProfileExtEntry SYNTAX AdslAlarmConfProfileExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry extends the adslLineAlarmConfProfileTable "An entry extends the adslLineAlarmConfProfileTable
defined in [RFC2662]. Each entry corresponds to defined in [RFC2662]. Each entry corresponds to
an ADSL alarm profile." an ADSL alarm profile."
skipping to change at page 24, line 28 skipping to change at page 24, line 28
adslAturThreshold15MinUasL Integer32 adslAturThreshold15MinUasL Integer32
} }
adslAtucThreshold15MinFailedFastR OBJECT-TYPE adslAtucThreshold15MinFailedFastR OBJECT-TYPE
SYNTAX Integer32(0..900) SYNTAX Integer32(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The first time the value of the corresponding "The first time the value of the corresponding
instance of adslAtucPerfCurr15MinFailedFastR reaches instance of adslAtucPerfCurr15MinFailedFastR
or exceeds this value within a given 15-minute reaches or exceeds this value within a given
performance data collection period, an 15-minute performance data collection period,
adslAtucFailedFastRThreshTrap notification will an adslAtucFailedFastRThreshTrap notification
be generated. The value '0' will disable the will be generated. The value '0' will disable
notification. The default value of this object is the notification. The default value of this
'0'." object is '0'."
DEFVAL { 0 } DEFVAL { 0 }
::= { adslAlarmConfProfileExtEntry 1 } ::= { adslAlarmConfProfileExtEntry 1 }
adslAtucThreshold15MinSesL OBJECT-TYPE adslAtucThreshold15MinSesL OBJECT-TYPE
SYNTAX Integer32(0..900) SYNTAX Integer32(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The first time the value of the corresponding instance "The first time the value of the corresponding
of adslAtucPerf15MinSesL reaches or exceeds instance of adslAtucPerf15MinSesL reaches or
this value within a given 15-minute performance data exceeds this value within a given 15-minute
collection period, an adslAtucSesLThreshTrap performance data collection period, an
notification will be generated. The value '0' will adslAtucSesLThreshTrap notification will be
disable the notification. The default value of this generated. The value '0' will disable the
notification. The default value of this
object is '0'." object is '0'."
DEFVAL { 0 } DEFVAL { 0 }
::= { adslAlarmConfProfileExtEntry 2 } ::= { adslAlarmConfProfileExtEntry 2 }
adslAtucThreshold15MinUasL OBJECT-TYPE adslAtucThreshold15MinUasL OBJECT-TYPE
SYNTAX Integer32(0..900) SYNTAX Integer32(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The first time the value of the corresponding instance "The first time the value of the corresponding
of adslAtucPerf15MinUasL reaches or exceeds instance of adslAtucPerf15MinUasL reaches or
this value within a given 15-minute performance data exceeds this value within a given 15-minute
collection period, an adslAtucUasLThreshTrap performance data collection period, an
notification will be generated. The value '0' will adslAtucUasLThreshTrap notification will be
disable the notification. The default value of this generated. The value '0' will disable the
notification. The default value of this
object is '0'." object is '0'."
DEFVAL { 0 } DEFVAL { 0 }
::= { adslAlarmConfProfileExtEntry 3 } ::= { adslAlarmConfProfileExtEntry 3 }
adslAturThreshold15MinSesL OBJECT-TYPE adslAturThreshold15MinSesL OBJECT-TYPE
SYNTAX Integer32(0..900) SYNTAX Integer32(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The first time the value of the corresponding instance "The first time the value of the corresponding
of adslAturPerf15MinSesL reaches or exceeds instance of adslAturPerf15MinSesL reaches or
this value within a given 15-minute performance data exceeds this value within a given 15-minute
collection period, an adslAturSesLThreshTrap performance data collection period, an
notification will be generated. The value '0' will adslAturSesLThreshTrap notification will be
disable the notification. The default value of this generated. The value '0' will disable the
notification. The default value of this
object is '0'." object is '0'."
DEFVAL { 0 } DEFVAL { 0 }
::= { adslAlarmConfProfileExtEntry 4 } ::= { adslAlarmConfProfileExtEntry 4 }
adslAturThreshold15MinUasL OBJECT-TYPE adslAturThreshold15MinUasL OBJECT-TYPE
SYNTAX Integer32(0..900) SYNTAX Integer32(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The first time the value of the corresponding instance "The first time the value of the corresponding
of adslAturPerf15MinUasL reaches or exceeds instance of adslAturPerf15MinUasL reaches or
this value within a given 15-minute performance data exceeds this value within a given 15-minute
collection period, an adslAturUasLThreshTrap performance data collection period, an
notification will be generated. The value '0' will adslAturUasLThreshTrap notification will be
disable the notification. The default value of this generated. The value '0' will disable the
notification. The default value of this
object is '0'." object is '0'."
DEFVAL { 0 } DEFVAL { 0 }
::= { adslAlarmConfProfileExtEntry 5 } ::= { adslAlarmConfProfileExtEntry 5 }
-- definitions -- definitions
adslExtTraps OBJECT IDENTIFIER ::= { adslExtMibObjects 24 } adslExtTraps OBJECT IDENTIFIER ::= { adslExtMibObjects 24 }
adslExtAtucTraps OBJECT IDENTIFIER ::= { adslExtTraps 1 } adslExtAtucTraps OBJECT IDENTIFIER ::= { adslExtTraps 1 }
adslExtAtucTrapsPrefix OBJECT IDENTIFIER ::= { adslExtAtucTraps 0 } adslExtAtucTrapsPrefix OBJECT IDENTIFIER ::= { adslExtAtucTraps 0 }
skipping to change at page 26, line 33 skipping to change at page 26, line 39
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Severely errored seconds-line 15-minute threshold "Severely errored seconds-line 15-minute threshold
reached." reached."
::= { adslExtAtucTrapsPrefix 2 } ::= { adslExtAtucTrapsPrefix 2 }
adslAtucUasLThreshTrap NOTIFICATION-TYPE adslAtucUasLThreshTrap NOTIFICATION-TYPE
OBJECTS { adslAtucPerfCurr15MinUasL } OBJECTS { adslAtucPerfCurr15MinUasL }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Unavailable seconds-line 15-minute threshold reached." "Unavailable seconds-line 15-minute threshold
reached."
::= { adslExtAtucTrapsPrefix 3 } ::= { adslExtAtucTrapsPrefix 3 }
adslExtAturTraps OBJECT IDENTIFIER ::= { adslExtTraps 2 } adslExtAturTraps OBJECT IDENTIFIER ::= { adslExtTraps 2 }
adslExtAturTrapsPrefix OBJECT IDENTIFIER ::= { adslExtAturTraps 0 } adslExtAturTrapsPrefix OBJECT IDENTIFIER ::= { adslExtAturTraps 0 }
adslAturSesLThreshTrap NOTIFICATION-TYPE adslAturSesLThreshTrap NOTIFICATION-TYPE
OBJECTS { adslAturPerfCurr15MinSesL } OBJECTS { adslAturPerfCurr15MinSesL }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Severely errored seconds-line 15-minute threshold "Severely errored seconds-line 15-minute threshold
reached." reached."
::= { adslExtAturTrapsPrefix 1 } ::= { adslExtAturTrapsPrefix 1 }
adslAturUasLThreshTrap NOTIFICATION-TYPE adslAturUasLThreshTrap NOTIFICATION-TYPE
OBJECTS { adslAturPerfCurr15MinUasL } OBJECTS { adslAturPerfCurr15MinUasL }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Unavailable seconds-line 15-minute threshold reached." "Unavailable seconds-line 15-minute threshold
reached."
::= { adslExtAturTrapsPrefix 2 } ::= { adslExtAturTrapsPrefix 2 }
-- conformance information -- conformance information
adslExtConformance OBJECT IDENTIFIER ::= { adslExtMIB 2 } adslExtConformance OBJECT IDENTIFIER ::= { adslExtMIB 2 }
adslExtGroups OBJECT IDENTIFIER ::= { adslExtConformance 1 } adslExtGroups OBJECT IDENTIFIER ::= { adslExtConformance 1 }
adslExtCompliances OBJECT IDENTIFIER ::= { adslExtConformance 2 } adslExtCompliances OBJECT IDENTIFIER ::= { adslExtConformance 2 }
-- ATU-C agent compliance statements -- ATU-C agent compliance statements
skipping to change at page 31, line 4 skipping to change at page 31, line 12
adslAturUasLThreshTrap adslAturUasLThreshTrap
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of ADSL extension notifications." "The collection of ADSL extension notifications."
::= { adslExtGroups 6 } ::= { adslExtGroups 6 }
END END
7. Acknowledgments 7. Acknowledgments
This document is a product of the ADSL MIB Working Group. This document is a product of the ADSL MIB Working Group.
8. Normative References 8. References
[ANSI T1.413] American National Standards Institute, ANSI T1.413, 8.1 Normative References
Issue 2, "Standards Project for Interfaces Relating
to Carrier to Customer Connection of ADSL Equipment", [ANSI T1.413] American National Standards Institute, ANSI
1998. T1.413, Issue 2, "Standards Project for Interfaces
Relating to Carrier to Customer Connection of ADSL
Equipment", 1998.
[ETSI DTS/TM06006] European Telecommunications Standards Institute [ETSI DTS/TM06006] European Telecommunications Standards Institute
"ADSL European Specific Requirements", November "ADSL European Specific Requirements", November
2000. 2000.
[ITU G.992.1] ITU-T Telecommunication Standardization Sector, [ITU G.992.1] ITU-T Telecommunication Standardization Sector,
"Asymmetric digital subscriber line (ADSL) "Asymmetric digital subscriber line (ADSL)
transceivers", June 1999. transceivers", June 1999.
[ITU G.992.2] ITU-T Telecommunication Standardization Sector, [ITU G.992.2] ITU-T Telecommunication Standardization Sector,
"Splitterless asymmetric digital subscriber line "Splitterless asymmetric digital subscriber line
(ADSL) transceivers", June 1999. (ADSL) transceivers", June 1999.
[ITU G.997.1] ITU-T Telecommunication Standardization Sector, [ITU G.997.1] ITU-T Telecommunication Standardization Sector,
"Physical Layer Management of Digital Subscriber "Physical Layer Management of Digital Subscriber
Transceivers", June 1999. Transceivers", June 1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for
TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions",
STD 16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901,
January 1996.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2026] Bradner S., "The Internet Standards Process - [RFC2026] Bradner S., "The Internet Standards Process -
Revision 3", October 1996. Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2028] Hovey R., S. Bradner, "The Organizations Involved in
the IETF Standards Process", October 1996.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2028] Hovey R. and S. Bradner, "The Organizations
"Introduction to Version 3 of the Internet-standard Involved in the IETF Standards Process", BCP 11,
Network Management Framework", RFC 2570, April 1999. RFC 2028, October 1996.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC2493] Tesink, K., "Textual Conventions for MIB Modules
Architecture for Describing SNMP Management Frameworks", Using Performance History Based on 15 Minute
RFC 2571, April 1999. Intervals" RFC 2493, January 1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
"Message Processing and Dispatching for the Simple Case, J., Rose, M. and S. Waldbusser, "Structure
Network Management Protocol (SNMP)", RFC 2572, April 1999. of Management Information Version 2 (SMIv2)", STD
58, RFC 2578, April 1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Applications", RFC 2573, April 1999. Case, J., Rose, M. and S. Waldbusser, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April
1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
(USM) for version 3 of the Simple Network Management Case, J., Rose, M. and S. Waldbusser, "Conformance
Protocol (SNMPv3)", RFC 2574, April 1999. Statements for SMIv2", STD 58, RFC 2580, April
1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed
Access Control Model (VACM) for the Simple Network Objects for the ADSL Lines", RFC 2662, May 1999.
Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
Rose, M., and S. Waldbusser, "Structure of Management Group MIB", RFC 2863, June 2000.
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security
Rose, M., and S. Waldbusser, "Textual Conventions for Model (USM) for version 3 of the Simple Network
SMIv2", STD 58, RFC 2579, April 1999. Management Protocol (SNMPv3)", STD 62, RFC 3414,
December 2002.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-
Rose, M., and S. Waldbusser, "Conformance Statements for based Access Control Model (VACM) for the Simple
SMIv2", STD 58, RFC 2580, April 1999. Network Management Protocol (SNMP)", STD 62, RFC
3415, December 2002.
[RFC2662] Bathrick, G. and F. Ly "Definitions of Managed Objects for 8.2 Informative References
the ADSL Lines", May 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
MIB", RFC 2863, June 2000. "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
11. Security Considerations 9. Security Considerations
The following security matters should be considered when implementing The following security matters should be considered when implementing
this MIB. this MIB.
1) Blocking unauthorized access to the ADSL MIB via the element 1) Blocking unauthorized access to the ADSL MIB via the element
management system is outside the scope of this document. It should be management system is outside the scope of this document. It
noted that access to the MIB permits the unauthorized entity to should be noted that access to the MIB permits the unauthorized
modify the profiles (section 6.4) such that both subscriber service entity to modify the profiles (section 6.4) such that both
and network operations can be interfered with. Subscriber service can subscriber service and network operations can be interfered with.
be altered by modifying any of a number of service characteristics
such as rate partitioning and maximum transmission rates. Network
operations can be impacted by modification of notification thresholds
such as Signal-to-Noise Ratio (SNR) margins.
2) There are a number of managed objects in this MIB that may be Subscriber service can be altered by modifying any of a number of
considered to contain sensitive information. In particular, the service characteristics such as rate partitioning and maximum
certain objects may be considered sensitive in many environments, transmission rates. Network operations can be impacted by
since it would allow an intruder to obtain information about which modifying notification thresholds such as Signal-to-Noise Ratio
vendor's equipment is in use on the network. Therefore, it may be (SNR) margins.
important in some environments to control read access to these
objects and possibly to even encrypt the values of these object when
sending them over the network via SNMP. Not all versions of SNMP
provide features for such a secure environment.
SNMPv1 by itself is such an insecure environment. Even if the 2) SNMPv1 by itself is such an insecure environment. Even if the
network itself is secure (for example by using IPSec), even then, network itself is secure (for example by using IPSec), there is no
there is no control as to who on the secure network is allowed to control over who on the secure network is allowed to access and
access and GET (read) the objects in this MIB. It is recommended GET (read) the objects in this MIB. It is recommended that the
that the implementors consider the security features as provided by implementors consider the security features as provided by the
the SNMPv3 framework. Specifically, the use of the User-based SNMPv3 framework. Specifically, the use of the User-based
Security Model RFC 2574 [21] and the View-based Access Control Model Security Model STD 62, RFC 3414 [RFC3414] and the View-based
RFC 2575 [23] is recommended. Access Control Model STD 62, RFC 3415 [RFC3415] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to those objects only to those principals configured to give access to only those objects, and to those
(users) that have legitimate rights to access them. principals (users) that have legitimate rights to access them.
3) The profile mechanism presented in this document requires specific 3) The profile mechanism presented in this document requires specific
attention. The implementor of this MIB has a choice of implementing attention. The implementor of this MIB has a choice of
either 'static' or 'dynamic' profiles. This decision must be implementing either 'static' or 'dynamic' profiles. This decision
consistent with the implementation of RFC2662. must be consistent with the implementation of RFC 2662.
In the case of 'static' profiles, the elements of the profile are In the case of 'static' profiles, the elements of the profile are
read-write as opposed to read-create when 'dynamic' profiles are read-write, as opposed to read-create when 'dynamic' profiles are
implemented: implemented:
- adslConfProfileLineType, - adslConfProfileLineType,
- adslAtucThreshold15MinFailedFastR, - adslAtucThreshold15MinFailedFastR,
- adslAtucThreshold15MinSesL, - adslAtucThreshold15MinSesL,
- adslAtucThreshold15MinUasL, - adslAtucThreshold15MinUasL,
- adslAturThreshold15MinSesL, and - adslAturThreshold15MinSesL, and
- adslAturThreshold15MinUasL. - adslAturThreshold15MinUasL.
This decision also impacts the mechanics of the index, This decision also impacts the mechanics of the index,
adslLineConfProfileDualLite. When 'static' profiles are implemented, adslLineConfProfileDualLite. When 'static' profiles are
its value is algorithmically set by the system and its value is implemented, its value is algorithmically set by the system and
based on the ifIndex, hence not guaranteed across system reboots. its value is based on the ifIndex. Hence it is not guaranteed
Similar to the handling of adslLineConfProfile [RFC2662], the across system reboots. Similar to the handling of
implementor of this MIB must ensure that the profile object values adslLineConfProfile [RFC2662], the implementor of this MIB must
associated with these indices are maintained across system reboots. ensure that the profile object values associated with these
indices are maintained across system reboots.
In the case of dynamic profiles, this object is set by the SNMP In the case of dynamic profiles, this object is set by the SNMP
manager. The implementor of this MIB may want to provide view of the manager. The implementor of this MIB may want to provide a view
profile on a customer-by-customer standpoint, but should be cautious of the profile on a customer-by-customer standpoint, but should be
of the dynamic nature of these objects. cautious of the dynamic nature of these objects.
4) ADSL layer connectivity from the ATU-R will permit the subscriber 4) ADSL layer connectivity from the ATU-R will permit the
to manipulate both the ADSL link directly and the ADSL overhead subscriber to manipulate both the ADSL link directly and the ADSL
control channel(AOC)/embedded operations channel (EOC) overhead control channel(AOC)/embedded operations channel (EOC)
for their own loop. For example, unchecked or unfiltered for their own loop. For example, unchecked or unfiltered
fluctuations initiated by the subscriber could generate sufficient fluctuations initiated by the subscriber could generate sufficient
notifications to potentially overwhelm either the management notifications to potentially overwhelm either the management
interface to the network or the element manager. Other attacks interface to the network or the element manager. Other attacks
affecting the ATU-R portions of the MIB may also be possible. affecting the ATU-R portions of the MIB may also be possible.
12. Intellectual Property Notice 10. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11 [RFC2028]. standards-related documentation can be found in BCP-11 [RFC2028].
Copies of claims of rights made available for publication and any Copies of claims of rights made available for publication and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use attempt made to obtain a general license or permission for the use of
of such proprietary rights by implementors or users of this such proprietary rights by implementors or users of this
specification can be obtained from the IETF Secretariat. specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to practice rights that may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
13. Authors' Addresses 11. Authors' Addresses
Faye Ly Faye Ly
Pedestal Networks Pedestal Networks
3045 Park Boulevard 6503 Dumbarton Circle,
Palo Alto, CA 94306, USA Fremont, CA 94555
Phone: +1 650-475-1274 Phone: +1 510-578-0158
Fax: +1 650-688-3119 Fax: +1 510-744-5152
EMail: faye@pedestalnetworks.com EMail: faye@pedestalnetworks.com
Gregory Bathrick Gregory Bathrick
NOKIA High Speed Access Nodes Nokia Networks
1310 Redwood Way, 2235 Mercury Way,
Petaluma, CA 94954, USA Santa Rosa, CA 95405
Phone: +1 707-793-7030 Phone: +1 707-362-1125
Fax: +1 707-792-0850 Fax: +1 707-535-7300
EMail: greg.bathrick@nokia.com EMail: greg.bathrick@nokia.com
14. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
skipping to change at page 36, line 14 skipping to change at line 1640
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
Table of Contents
1. Status of this Memo ..................................... 1
2. Abstract ............................................... 1
3. The SNMP Network Management Framework ................... 1
4. Introduction ............................................ 2
5. Relationship of ADSL LINE EXTENSION MIB with standard MIBs. 3
6. Conventions used in the MIB ............................. 3
7. Conformance and Compliance .............................. 5
8. Definitions ............................................. 5
9. Acknowledgments ......................................... 25
10. References .............................................. 26
11. Security Considerations ................................. 27
12. Intellectual Property Notice .............................. 27
13. Authors' Addresses ...................................... 28
14. Full Copyright Statement ............................... 29
 End of changes. 

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