draft-ietf-adslmib-adslext-08.txt   draft-ietf-adslmib-adslext-09.txt 
INTERNET-DRAFT ADSL Line Extension MIB Faye Ly INTERNET-DRAFT ADSL Line Extension MIB Faye Ly
Salira Optical Systems Pedestal Networks
Gregory Bathrick Gregory Bathrick
Nokia Nokia
August 1, 2001 April 23, 2002
Definitions of Extension Managed Objects Definitions of Extension Managed Objects
for ADSL Lines for ADSL Lines
August 1, 2001 April 23, 2002
draft-ietf-adslmib-adslext-08.txt draft-ietf-adslmib-adslext-09.txt
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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
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 (2000). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
2. Abstract 2. 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 [RFC2662].
3. The SNMP Network Management Framework 3. The SNMP Network Management Framework
skipping to change at line 47 skipping to change at page 2, line 4
2. Abstract 2. 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 [RFC2662].
3. The SNMP Network Management Framework 3. The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: An overall architecture, described in RFC 2571 components:
[RFC2571]. Mechanisms for describing and naming objects and events
for the purpose of management. The first version of this Structure o An overall architecture, described in RFC 2571 [RFC2571].
of Management Information (SMI) is called SMIv1 and described in STD
16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 o Mechanisms for describing and naming objects and events
[RFC1215]. The second version, called SMIv2, is described in STD 58, for the purpose of management. The first version of this
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 Structure of Management Information (SMI) is called SMIv1
[RFC2580]. Message protocols for transferring management and described in STD 16, RFC 1155 [RFC1155], STD 16,
information. The first version of the SNMP message protocol is RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version,
called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second 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.
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 version of the SNMP message protocol, which is not an Internet
standards track protocol, is called SNMPv2c and described in RFC 1901 standards track protocol, is called SNMPv2c and described in RFC
[RFC1901] and RFC 1906 [RFC1906]. The third version of the message 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the
protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC message protocol is called SNMPv3 and described in RFC 1906
2572 [RFC2572] and RFC 2574 [RFC2574]. Protocol operations for [RFC1906], RFC2572 [RFC2572] and RFC 2574 [RFC2574].
accessing management information. The first set of protocol
operations and associated PDU formats is described in STD 15, RFC o Protocol operations for accessing management information. The
1157 [RFC1157]. A second set of protocol operations and associated first set of protocol operations and associated PDU formats is
PDU formats is described in RFC 1905 [RFC1905]. A set of fundamental described in STD 15, RFC 1157 [RFC1157]. A second set of protocol
applications described in RFC 2573 [RFC2573] and the view-based operations and associated PDU formats is described in RFC 1905
access control mechanism described in RFC 2575 [RFC2575]. [RFC1905].
o A set of fundamental applications described in RFC 2573
[RFC2573] and the view-based access control mechanism described in
RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [RFC2570]. can be found in RFC 2570 [RFC2570].
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. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
skipping to change at line 93 skipping to change at page 3, line 10
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
4. Introduction 4. 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 ADSL Line MIB as defined in [RFC2662].
This memo addresses the additional objects defined in ITU G.997.1 This memo addresses the additional objects defined in ITU G.997.1
[ITU G.997.1]. These additional objects specifically address the [ITU G.997.1].
management
5. Relationship of ADSL Line Extension MIB with standard MIBs 5. 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 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 standardization. In regards to these relationship, the ADSL Line of standardization. In regards to these relationship, the ADSL Line
Extension MIB follows conventions as used by the ADSL Line MIB with few Extension MIB follows conventions as used by the ADSL Line MIB with
Exceptions as listed below. one exception. The value of the RFC2863 object, ifOperstatus,
SHALL be down(2) when the ADSL line interface is in power state L3 as
5.1 ifOperStatus defined in ITU G.992.1 [ITU G.992.1], which means no power. Its value
shall be up(1) if the ADSL line interface is in power state L0 (power on)
The value of RFC 1213 object, ifOperstatus, shall be down(2) when the [ITU G.992.1] or L1 (reduced power). Power Status L2 [ITU G.992.1] is
ADSL line interface is in power state L3 as defined in ITU G.992.1 not applicable.
[ITU G.992.1], which means no power. Its value shall be up(1) if the
ADSL line interface is in power state L0 (power on) [ITU G.992.1]
or L1 (reduced power). Power Status L2 [ITU G.992.1] is not applicable.
6. Conventions used in the MIB 6. Conventions used in the MIB
6.1 Structure 6.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].
6.2 Additional Managed Objects 6.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 G.992.2 [ITU G.992.2] are: ITU 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 order Besides the management of G.Lite, another object has been added in
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.
6.2.1 ATU-C ADSL Transmission System Parameters and Line Mode 6.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:
- Capability - Capability
- Configuration - Configuration
skipping to change at line 223 skipping to change at page 5, line 40
interface was unavailable during the measured period. This counter interface was unavailable during the measured period. This counter
does not include the seconds in which unavailability was caused solely does not include the seconds in which unavailability was caused solely
by fast retrains and failed fast retrains. Fast retrains and failed by fast retrains and failed fast retrains. Fast retrains and failed
fast retrains are considered to be part of the normal network operation fast retrains are considered to be part of the normal network operation
and thus are not counted as unavailable errors. and thus are not counted as unavailable errors.
6.2.5 Counters, Interval Buckets and Thresholds 6.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. Each well as current and previous 1-day interval-counters. Threshold
physical-layer current 15-minute event bucket has threshold trap. notification can be configured for each physical-layer current
15-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}.
skipping to change at line 249 skipping to change at page 6, line 19
The 15-minute event counters are of type PerfCurrentCount and The 15-minute event counters are of type PerfCurrentCount and
PerfIntervalCount. The 1-day event counters are of type PerfIntervalCount. The 1-day event counters are of 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 type AdslPerfTimeElapsed.
6.2.6 Alternative profile configuration for the dual line mode 6.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 interface
(the ADSL line and, if applicable, channel) is configured as dual mode, (the ADSL line and, if applicable, channel) is configured as dual mode,
that is, the object adslLineTransAtucConfig is configured with one or more that is, the object adslLineTransAtucConfig is configured with one or
full-rate modes and one or more G.Lite modes. 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 as
the primary full-rate profile. The newly added object in this MIB 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 configure
the G.Lite profile. Note that if one or more full-rate modes are the G.Lite profile. Note that if one or more full-rate modes are
configured, or only G.Lite modes are configured, only the original configured, or only G.Lite modes are configured, only the original
full-rate profile is needed. The dual-mode profile object is only full-rate profile is needed. The dual-mode profile object is only
needed when both full-rate and G.Lite profiles are needed. In this case, needed when both full-rate and G.Lite profiles are needed. In this
it will be set to the value of adslLineConfProfile. case, it will be set to the value of adslLineConfProfile when 'dynamic'
profiles are implemented.
When 'static' profiles are implemented, in much like the case of the When 'static' profiles are implemented, however, similar to the case
object, adslLineConfProfileName [RFC2662], this object's value will of the object, adslLineConfProfileName [RFC2662], this object's value
need to algorithmically represent the line. In this case, the value will need to algorithmically represent the line. In this case, the
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 type
(e.g., G.Lite, Full-rate) will be used. Therefore, the profile's name (e.g., G.Lite, Full-rate) will be used. Therefore, the profile's name
is a string of the concatenation is a string of the concatenation of ifIndex and one of the follow
of ifIndex and one of the follow values: Full or Lite. This string will values: Full or Lite. This string will be fixed-length (i.e., 14) with
be fixed-length (i.e., 14) with leading zero(s). For example, the leading zero(s). For example, the profile name for ifIndex that
profile name for ifIndex that equals '15' and is a full rate line, equals '15' and is a full rate line, it will be '0000000015Full'.
it will be '0000000015Full'.
7. Conformance and Compliance 7. Conformance and Compliance
See the conformance and compliance statements within the information See the conformance and compliance statements within the information
module. module.
8. Definitions 8. Definitions
ADSL-LINE-EXT-MIB DEFINITIONS ::= BEGIN ADSL-LINE-EXT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Counter32, Counter32,
Unsigned32, Integer32,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
MODULE-IDENTITY, Gauge32, 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,
PerfIntervalCount FROM PerfHist-TC-MIB PerfIntervalCount FROM PerfHist-TC-MIB
AdslPerfCurrDayCount, AdslPerfCurrDayCount,
AdslPerfPrevDayCount FROM ADSL-TC-MIB AdslPerfPrevDayCount FROM ADSL-TC-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB
adslLineAlarmConfProfileEntry, adslLineAlarmConfProfileEntry,
skipping to change at line 307 skipping to change at page 7, line 30
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 "200104090000Z" LAST-UPDATED "200204231200Z"
ORGANIZATION "IETF ADSL MIB Working Group" ORGANIZATION "IETF ADSL MIB Working Group"
CONTACT-INFO CONTACT-INFO
" "
Faye Ly Faye Ly
Salira Optical Systems Pedestal Networks
2698 Orchard Parkway 3045 Park Boulevard
San Jose, CA 95134 Palo Alto, CA 94306
Tel: +1 408-382-0088 Tel: +1 650-475-1274
Fax: +1 408-382-1688 Fax: +1 650-688-3119
E-Mail: faye@salira.com E-Mail: faye@pedestalnetworks.com
Gregory Bathrick Gregory Bathrick
NOKIA High Speed Access Nodes NOKIA High Speed Access Nodes
1310 Redwood Way, 1310 Redwood Way,
Petaluma, CA 94954 Petaluma, CA 94954
Tel: +1 707-793-7030 Tel: +1 707-793-7030
Fax: +1 707-792-0850 Fax: +1 707-792-0850
E-Mail: greg.bathrick@nokia.com E-Mail: greg.bathrick@nokia.com
IETF ADSL MIB Working Group IETF ADSL MIB Working Group
<XDSLMIB@LISTSERV.ECIRALEIGH.COM> <XDSLMIB@LISTSERV.ECIRALEIGH.COM>
" "
DESCRIPTION DESCRIPTION
"This MIB Module is a supplement to the ADSL-LINE-MIB "This MIB Module is a supplement to the ADSL-LINE-MIB
[RFC2662]." [RFC2662]."
REVISION "0108011200Z" -- YY Month YYYY REVISION "200204231200Z"
DESCRIPTION "Initial Version, published as RFC xxxx. This MIB DESCRIPTION "Initial Version, published as RFC xxxx. This MIB
module is supplement to 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
and G.Lite respectively: and G.Lite respectively:
skipping to change at line 377 skipping to change at page 9, line 4
q9921IsdnNonOverlapped(4), q9921IsdnNonOverlapped(4),
q9921isdnOverlapped(5), q9921isdnOverlapped(5),
q9921tcmIsdnNonOverlapped(6), q9921tcmIsdnNonOverlapped(6),
q9921tcmIsdnOverlapped(7), q9921tcmIsdnOverlapped(7),
q9922potsNonOverlapeed(8), q9922potsNonOverlapeed(8),
q9922potsOverlapped(9), q9922potsOverlapped(9),
q9922tcmIsdnNonOverlapped(10), q9922tcmIsdnNonOverlapped(10),
q9922tcmIsdnOverlapped(11), q9922tcmIsdnOverlapped(11),
q9921tcmIsdnSymmetric(12) q9921tcmIsdnSymmetric(12)
} }
adslLineExtTable OBJECT-TYPE adslLineExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslLineExtEntry SYNTAX SEQUENCE OF AdslLineExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table is an extension of RFC2662. It "This table is an extension of RFC2662. It
contains ADSL line configuration and contains ADSL line configuration and
monitoring information. This includes the ADSL monitoring information. This includes the ADSL
line's capabilities and actual ADSL transmission line's capabilities and actual ADSL transmission
bbbbbbsystem." system."
::= { adslExtMibObjects 17 } ::= { adslExtMibObjects 17 }
adslLineExtEntry OBJECT-TYPE adslLineExtEntry OBJECT-TYPE
SYNTAX AdslLineExtEntry SYNTAX AdslLineExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry extends the adslLineEntry defined in "An entry extends the adslLineEntry defined in
[RFC2662]. Each entry corresponds to an ADSL [RFC2662]. Each entry corresponds to an ADSL
line." line."
skipping to change at line 466 skipping to change at page 10, line 44
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. If the object state of this interface. L0 is power on, L1 is
adslLineTransAtucActual is set to a G.992.2 power on but 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
managed ADSL interface. The value of the object
ifOperStatus is set to down(2) if the ADSL interface
is in power state L3 and is set to up(1) if the ADSL
line interface is in power state L0 or L1. If the
object adslLineTransAtucActual is set to a G.992.2
(G.Lite)-type transmission mode, the value of (G.Lite)-type transmission mode, the value of
this object will be one of the valid power 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 when
it is configured in dual mode, and operating in a it is configured in dual mode, and operating in a
G.Lite-type mode as denoted by adslLineTransAtucActual. G.Lite-type mode as denoted by
Dual mode exists when the object, adslLineTransAtucConfig, adslLineTransAtucActual. Dual mode exists when the
is configured with one or more full-rate modes and one or object, adslLineTransAtucConfig, is configured with
more G.Lite modes simultaneously. one or more full-rate modes and one or more G.Lite
modes simultaneously.
When 'dynamic' profiles are implemented, the value of When 'dynamic' profiles are implemented, the value of
object is equal to the index of the applicable row in the object is equal to the index of the applicable row in
ADSL Line Configuration Profile Table, the ADSL Line Configuration Profile Table,
AdslLineConfProfileTable defined in ADSL-MIB [RFC2662]. AdslLineConfProfileTable defined in ADSL-MIB
[RFC2662].
In the case when dual-mode has not been enabled, the In the case when dual-mode has not been enabled, the
value of the object will be equal to the value of the value of the object will be equal to the value of the
object adslLineConfProfile [RFC2662]. 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, adslLineConfProfileName
[RFC2662], this object's value will need to [RFC2662], this object's value will need to
algorithmically represent the characteristics of the algorithmically represent the characteristics of the
line. In this case, the value of the line's ifIndex line. In this case, the value of the line's ifIndex
plus a value indicating the line mode type plus a value indicating the line mode type
(e.g., G.Lite, Full-rate) will be used. Therefore, (e.g., G.Lite, Full-rate) will be used. Therefore,
the profile's name is a string concatenating the the profile's name is a string concatenating the
ifIndex and one of the follow values: Full or Lite. This ifIndex and one of the follow values: Full or Lite.
string will be fixed-length (i.e., 14) with leading This string will be fixed-length (i.e., 14) with
zero(s). For example, the profile name for leading zero(s). For example, the profile name for
ifIndex that equals '15' and is a full rate ifIndex that equals '15' and is a full rate line, it
line, it will be '0000000015Full'." 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
skipping to change at line 1073 skipping to change at page 23, line 36
exist. exist.
fastOrInterleaved(4), when either fast or fastOrInterleaved(4), when either fast or
interleaved channels can exist, but only one interleaved channels can exist, but only one
at any time. at any time.
fastAndInterleaved(5), when both the fast channel fastAndInterleaved(5), when both the fast channel
and the interleaved channel exist. and the interleaved channel exist.
In the case when no value has been set, the default In the case when no value has been set, the default
Value is noChannel(1). Value is noChannel(1).
" "
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 adslLineAlarmConfProfileTable
and provides threshold parameters for all the and provides threshold parameters for all the
counters defined in this MIB module." counters defined in this MIB module."
skipping to change at line 1098 skipping to change at page 24, line 14
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."
AUGMENTS { adslLineAlarmConfProfileEntry } AUGMENTS { adslLineAlarmConfProfileEntry }
::= { adslAlarmConfProfileExtTable 1 } ::= { adslAlarmConfProfileExtTable 1 }
AdslAlarmConfProfileExtEntry ::= AdslAlarmConfProfileExtEntry ::=
SEQUENCE { SEQUENCE {
adslAtucThreshold15MinFailedFastR INTEGER, adslAtucThreshold15MinFailedFastR Integer32,
adslAtucThreshold15MinSesL INTEGER, adslAtucThreshold15MinSesL Integer32,
adslAtucThreshold15MinUasL INTEGER, adslAtucThreshold15MinUasL Integer32,
adslAturThreshold15MinSesL INTEGER, adslAturThreshold15MinSesL Integer32,
adslAturThreshold15MinUasL INTEGER adslAturThreshold15MinUasL Integer32
} }
adslAtucThreshold15MinFailedFastR OBJECT-TYPE adslAtucThreshold15MinFailedFastR OBJECT-TYPE
SYNTAX INTEGER(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 reaches
or exceeds this value within a given 15-minute or exceeds this value within a given 15-minute
performance data collection period, an performance data collection period, an
adslAtucFailedFastRThreshTrap notifications will adslAtucFailedFastRThreshTrap notification will
be generated. The value '0' will disable the trap. be generated. The value '0' will disable the
The default value of this object is '0'." notification. The default value of this object is
'0'."
DEFVAL { 0 }
::= { adslAlarmConfProfileExtEntry 1 } ::= { adslAlarmConfProfileExtEntry 1 }
adslAtucThreshold15MinSesL OBJECT-TYPE adslAtucThreshold15MinSesL OBJECT-TYPE
SYNTAX INTEGER(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 instance
of adslAtucPerf15MinSesL reaches or exceeds of adslAtucPerf15MinSesL reaches or exceeds
this value within a given 15-minute performance data this value within a given 15-minute performance data
collection period, an adslAtucSesLThreshTrap collection period, an adslAtucSesLThreshTrap
notifications will be generated. The value '0' will notification will be generated. The value '0' will
disable the trap. The default value of this object is disable the notification. The default value of this
'0'." object is '0'."
DEFVAL { 0 }
::= { adslAlarmConfProfileExtEntry 2 } ::= { adslAlarmConfProfileExtEntry 2 }
adslAtucThreshold15MinUasL OBJECT-TYPE adslAtucThreshold15MinUasL OBJECT-TYPE
SYNTAX INTEGER(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 instance
of adslAtucPerf15MinUasL reaches or exceeds of adslAtucPerf15MinUasL reaches or exceeds
this value within a given 15-minute performance data this value within a given 15-minute performance data
collection period, an adslAtucUasLThreshTrap collection period, an adslAtucUasLThreshTrap
notifications will be generated. The value '0' will notification will be generated. The value '0' will
disable the trap. The default value of this object is disable the notification. The default value of this
'0'." object is '0'."
DEFVAL { 0 }
::= { adslAlarmConfProfileExtEntry 3 } ::= { adslAlarmConfProfileExtEntry 3 }
adslAturThreshold15MinSesL OBJECT-TYPE adslAturThreshold15MinSesL OBJECT-TYPE
SYNTAX INTEGER(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 instance
of adslAturPerf15MinSesL reaches or exceeds of adslAturPerf15MinSesL reaches or exceeds
this value within a given 15-minute performance data this value within a given 15-minute performance data
collection period, an adslAturSesLThreshTrap collection period, an adslAturSesLThreshTrap
notifications will be generated. The value '0' will notification will be generated. The value '0' will
disable the trap. The default value of this object is disable the notification. The default value of this
'0'." object is '0'."
DEFVAL { 0 }
::= { adslAlarmConfProfileExtEntry 4 } ::= { adslAlarmConfProfileExtEntry 4 }
adslAturThreshold15MinUasL OBJECT-TYPE adslAturThreshold15MinUasL OBJECT-TYPE
SYNTAX INTEGER(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 instance
of adslAturPerf15MinUasL reaches or exceeds of adslAturPerf15MinUasL reaches or exceeds
this value within a given 15-minute performance data this value within a given 15-minute performance data
collection period, an adslAturUasLThreshTrap collection period, an adslAturUasLThreshTrap
notifications will be generated. The value '0' will notification will be generated. The value '0' will
disable the trap. The default value of this object is disable the notification. The default value of this
'0'." object is '0'."
DEFVAL { 0 }
::= { adslAlarmConfProfileExtEntry 5 } ::= { adslAlarmConfProfileExtEntry 5 }
-- trap 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 }
adslAtucFailedFastRThreshTrap NOTIFICATION-TYPE adslAtucFailedFastRThreshTrap NOTIFICATION-TYPE
OBJECTS { adslAtucPerfCurr15MinFailedFastR } OBJECTS { adslAtucPerfCurr15MinFailedFastR }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Failed Fast Retrains 15-minute threshold reached." "Failed Fast Retrains 15-minute threshold reached."
::= { adslExtAtucTraps 0 1 } ::= { adslExtAtucTrapsPrefix 1 }
adslAtucSesLThreshTrap NOTIFICATION-TYPE adslAtucSesLThreshTrap NOTIFICATION-TYPE
OBJECTS { adslAtucPerfCurr15MinSesL } OBJECTS { adslAtucPerfCurr15MinSesL }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Severely errored seconds-line 15-minute threshold "Severely errored seconds-line 15-minute threshold
reached." reached."
::= { adslExtAtucTraps 0 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."
::= { adslExtAtucTraps 0 3 } ::= { adslExtAtucTrapsPrefix 3 }
adslExtAturTraps OBJECT IDENTIFIER ::= { adslExtTraps 2 } adslExtAturTraps OBJECT IDENTIFIER ::= { adslExtTraps 2 }
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."
::= { adslExtAturTraps 0 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."
::= { adslExtAturTraps 0 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 line 1260 skipping to change at page 27, line 43
"This group is optional. Implementations which "This group is optional. Implementations which
require continuous ATU-C physical event counters require continuous ATU-C physical event counters
should implement this group." should implement this group."
GROUP adslExtAturPhysPerfCounterGroup GROUP adslExtAturPhysPerfCounterGroup
DESCRIPTION DESCRIPTION
"This group is optional. Implementations which "This group is optional. Implementations which
require continuous ATU-R physical event counters require continuous ATU-R physical event counters
should implement this group." should implement this group."
GROUP adslExtNotificationsGroup
DESCRIPTION
"This group is optional. Implementations which
support TCA (Threshold Crossing Alert) should
implement this group."
OBJECT adslAtucThreshold15MinFailedFastR OBJECT adslAtucThreshold15MinFailedFastR
MIN-ACCESS read-write MIN-ACCESS read-write
DESCRIPTION DESCRIPTION
"Read-write access is applicable only when "Read-write access is applicable only when
static profiles as defined in ADSL Line MIB static profiles as defined in ADSL Line MIB
[RFC2662] are implemented." [RFC2662] are implemented."
OBJECT adslAtucThreshold15MinSesL OBJECT adslAtucThreshold15MinSesL
MIN-ACCESS read-write MIN-ACCESS read-write
DESCRIPTION DESCRIPTION
skipping to change at line 1298 skipping to change at page 28, line 40
OBJECT adslAturThreshold15MinUasL OBJECT adslAturThreshold15MinUasL
MIN-ACCESS read-write MIN-ACCESS read-write
DESCRIPTION DESCRIPTION
"Read-write access is applicable only when "Read-write access is applicable only when
static profiles as defined in ADSL Line MIB static profiles as defined in ADSL Line MIB
[RFC2662] are implemented." [RFC2662] are implemented."
OBJECT adslLineConfProfileDualLite OBJECT adslLineConfProfileDualLite
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Read-write access is applicable only when "Read-only access is applicable only when
static profiles as defined in ADSL Line MIB static profiles as defined in ADSL Line MIB
[RFC2662] are implemented." [RFC2662] are implemented."
::= { adslExtCompliances 1 } ::= { adslExtCompliances 1 }
-- units of conformance -- units of conformance
adslExtLineGroup OBJECT-GROUP adslExtLineGroup OBJECT-GROUP
OBJECTS { OBJECTS {
adslLineConfProfileDualLite, adslLineConfProfileDualLite,
adslLineTransAtucCap, adslLineTransAtucCap,
skipping to change at line 1406 skipping to change at page 31, line 4
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
9. Acknowledgments 9. Acknowledgments
This document is a product of the ADSL MIB Working Group. This document is a product of the ADSL MIB Working Group.
10. References 10. Normative References
[ANSI T1.413] American National Standards Institute, ANSI T1.413, [ANSI T1.413] American National Standards Institute, ANSI T1.413,
Issue 2, "Standards Project for Interfaces Relating Issue 2, "Standards Project for Interfaces Relating
to Carrier to Customer Connection of ADSL Equipment", to Carrier to Customer Connection of ADSL Equipment",
1998. 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.
skipping to change at line 1432 skipping to change at page 31, line 29
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 [RFC1155] Rose, M., and K. McCloghrie, "Structure and
of Management Information for TCP/IP-based Internets", STD Identification of Management Information for
16, RFC 1155, May 1990. 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, [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
RFC 1212, March 1991. "Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1213] McCloghrie, K. and M. Rose, "Management Information Base for [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions",
Network Management of TCP/IP-based internets - MIB-II", STD 16, RFC 1212, March 1991.
STD 17, RFC 1213, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with the [RFC1215] M. Rose, "A Convention for Defining Traps for use with
SNMP", RFC 1215, March 1991. the SNMP", RFC 1215, March 1991.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January "Introduction to Community-based SNMPv2", RFC 1901,
1996. January 1996.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple Network "Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996. Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network "Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996. Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2026] Bradner S., "The Internet Standards Process - Revision 3", [RFC2026] Bradner S., "The Internet Standards Process -
October 1996. Revision 3", October 1996.
[RFC2028] Hovey R., S. Bradner, "The Organizations Involved in the [RFC2028] Hovey R., S. Bradner, "The Organizations Involved in
IETF Standards Process", October 1996. the IETF Standards Process", October 1996.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network "Introduction to Version 3 of the Internet-standard
Management Framework", RFC 2570, April 1999. Network Management Framework", RFC 2570, April 1999.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
for Describing SNMP Management Frameworks", RFC 2571, April Architecture for Describing SNMP Management Frameworks",
1999. RFC 2571, April 1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
Processing and Dispatching for the Simple Network Management "Message Processing and Dispatching for the Simple
Protocol (SNMP)", RFC 2572, April 1999. Network Management Protocol (SNMP)", RFC 2572, April 1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
RFC 2573, April 1999. Applications", RFC 2573, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999. Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999. Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
skipping to change at line 1503 skipping to change at page 32, line 49
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2662] Bathrick G., F. Ly "Definitions of Managed Objects for the [RFC2662] Bathrick, G. and F. Ly "Definitions of Managed Objects for
ADSL Lines", May 1999. the ADSL Lines", May 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
RFC 2863, June 2000. MIB", RFC 2863, June 2000.
11. Security Considerations 11. Security Considerations
The following security matters should be considered when implementing
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 should be
noted that access to the MIB permits the unauthorized entity to noted that access to the MIB permits the unauthorized entity to
modify the profiles (section 6.4) such that both subscriber service and modify the profiles (section 6.4) such that both subscriber service
network operations can be interfered with. Subscriber service can be and network operations can be interfered with. Subscriber service can
altered by modifying any of a number of service characteristics such be altered by modifying any of a number of service characteristics
as rate partitioning and maximum transmission rates. Network such as rate partitioning and maximum transmission rates. Network
operations can be impacted by modification of trap thresholds such as operations can be impacted by modification of notification thresholds
Signal-to-Noise Ratio (SNR) margins. such as Signal-to-Noise Ratio (SNR) margins.
2) There are a number of managed objects in this MIB that may be 2) There are a number of managed objects in this MIB that may be
considered to contain sensitive information. In particular, the considered to contain sensitive information. In particular, the
certain objects may be considered sensitive in many environments, certain objects may be considered sensitive in many environments,
since it would allow an intruder to obtain information about which since it would allow an intruder to obtain information about which
vendor's equipment is in use on the network. Therefore, it may be vendor's equipment is in use on the network. Therefore, it may be
important in some environments to control read access to these important in some environments to control read access to these
objects and possibly to even encrypt the values of these object when objects and possibly to even encrypt the values of these object when
sending them over the network via SNMP. Not all versions of SNMP sending them over the network via SNMP. Not all versions of SNMP
provide features for such a secure environment. provide features for such a secure environment.
SNMPv1 by itself is such an insecure environment. Even if the 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), even then,
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
skipping to change at line 1546 skipping to change at page 33, line 47
that the implementors consider the security features as provided by that the implementors consider the security features as provided by
the SNMPv3 framework. Specifically, the use of the User-based the SNMPv3 framework. Specifically, the use of the User-based
Security Model RFC 2574 [21] and the View-based Access Control Model Security Model RFC 2574 [21] and the View-based Access Control Model
RFC 2575 [23] is recommended. RFC 2575 [23] 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 those objects only to those principals
(users) that have legitimate rights to access them. (users) that have legitimate rights to access them.
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 implementing
either 'static' or 'dynamic' profiles. In the case of 'static' either 'static' or 'dynamic' profiles. This decision must be
profiles, the elements of the profile are read-write as opposed to consistent with the implementation of RFC2662.
read-create when 'dynamic' profiles are implemented:
adslConfProfileLineType, adslAtucThreshold15MinFailedFastR, In the case of 'static' profiles, the elements of the profile are
adslAtucThreshold15MinSesL, adslAtucThreshold15MinUasL, read-write as opposed to read-create when 'dynamic' profiles are
adslAturThreshold15MinSesL, and adslAturThreshold15MinUasL. implemented:
- adslConfProfileLineType,
- adslAtucThreshold15MinFailedFastR,
- adslAtucThreshold15MinSesL,
- adslAtucThreshold15MinUasL,
- adslAturThreshold15MinSesL, and
- 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 implemented,
its value is algorithmically set by the system and its value is its value is algorithmically set by the system and its value is
based on the ifIndex, hence not guaranteed across system reboots. In based on the ifIndex, hence not guaranteed across system reboots.
the case of dynamic profiles, this object is set by the SNMP manager. Similar to the handling of adslLineConfProfile [RFC2662], the
The implementor of this MIB may want to provide view of the profile on implementor of this MIB must ensure that the profile object values
a customer-by-customer standpoint, but should be cautious of the associated with these indices are maintained across system reboots.
dynamic nature of these objects.
3) ADSL layer connectivity from the ATU-R will permit the subscriber 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
profile on a customer-by-customer standpoint, but should be cautious
of the dynamic nature of these objects.
4) ADSL layer connectivity from the ATU-R will permit the subscriber
to manipulate both the ADSL link directly and the ADSL overhead to manipulate both the ADSL link directly and the ADSL overhead
control channel(AOC)/embedded operations channel (EOC) 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
traps to potentially overwhelm either the management interface to the notifications to potentially overwhelm either the management
network or the element manager. Other attacks affecting the ATU-R interface to the network or the element manager. Other attacks
portions of the MIB may also be possible. affecting the ATU-R portions of the MIB may also be possible.
12. Intellectual Property Notice 12. 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 such proprietary rights by implementors or users of this of 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 13. Authors' Addresses
Faye Ly Faye Ly
Salira Optical Systems Pedestal Networks
2698 Orchard Parkway 3045 Park Boulevard
San Jose, CA 95134, USA Palo Alto, CA 94306, USA
Phone: +1 408-382-0088 Phone: +1 650-475-1274
Fax: +1 408-382-1688 Fax: +1 650-688-3119
EMail: faye@salira.com EMail: faye@pedestalnetworks.com
Gregory Bathrick Gregory Bathrick
NOKIA High Speed Access Nodes NOKIA High Speed Access Nodes
1310 Redwood Way, 1310 Redwood Way,
Petaluma, CA 94954, USA Petaluma, CA 94954, USA
Phone: +1 707-793-7030 Phone: +1 707-793-7030
Fax: +1 707-792-0850 Fax: +1 707-792-0850
EMail: greg.bathrick@nokia.com EMail: greg.bathrick@nokia.com
14. Full Copyright Statement 14. Full Copyright Statement
Copyright (C) The Internet Society (2001). 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
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
skipping to change at line 1659 skipping to change at page 36, line 26
1. Status of this Memo ..................................... 1 1. Status of this Memo ..................................... 1
2. Abstract ............................................... 1 2. Abstract ............................................... 1
3. The SNMP Network Management Framework ................... 1 3. The SNMP Network Management Framework ................... 1
4. Introduction ............................................ 2 4. Introduction ............................................ 2
5. Relationship of ADSL LINE EXTENSION MIB with standard MIBs. 3 5. Relationship of ADSL LINE EXTENSION MIB with standard MIBs. 3
6. Conventions used in the MIB ............................. 3 6. Conventions used in the MIB ............................. 3
7. Conformance and Compliance .............................. 5 7. Conformance and Compliance .............................. 5
8. Definitions ............................................. 5 8. Definitions ............................................. 5
9. Acknowledgments ......................................... 25 9. Acknowledgments ......................................... 25
10. References ......................................... ... 26 10. References .............................................. 26
11. Security Considerations ............................ ... 27 11. Security Considerations ................................. 27
12. Intellectual Property Notice ......................... ... 27 12. Intellectual Property Notice .............................. 27
13. Authors' Addresses .................................. ... 28 13. Authors' Addresses ...................................... 28
14. Full Copyright Statement ................................ 29 14. Full Copyright Statement ............................... 29
 End of changes. 

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