draft-ietf-adslmib-gshdslbis-07.txt   draft-ietf-adslmib-gshdslbis-08.txt 
Network Working Group C. Sikes Network Working Group C. Sikes
Internet-Draft Paradyne Corporation Internet-Draft Paradyne Corporation
Expires: April 6, 2005 B. Ray Expires: August 25, 2005 B. Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
R. Abbi R. Abbi
Alcatel USA Alcatel USA
October 6, 2004 February 21, 2005
Definitions of Managed Objects for G.shdsl.bis Lines Definitions of Managed Objects for G.shdsl.bis Lines
draft-ietf-adslmib-gshdslbis-07.txt draft-ietf-adslmib-gshdslbis-08.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of Section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 6, 2005. This Internet-Draft will expire on August 25, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2005).
Abstract Abstract
This document defines a Management Information Base (MIB) module for This document defines a Management Information Base (MIB) module for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes objects used for managing High Bit-Rate particular, it describes objects used for managing High Bit-Rate
Digital Subscriber Line (DSL) - 2nd generation (HDSL2) and Digital Subscriber Line (DSL) - 2nd generation (HDSL2) and
Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces. Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces.
This document introduces extensions to several objects and textual This document introduces extensions to several objects and textual
conventions defined in HDSL2-SHDSL-Line MIB (RFC 3276). This conventions defined in HDSL2-SHDSL-Line MIB (RFC 3276). This
skipping to change at page 2, line 18 skipping to change at page 2, line 19
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1 Relationship of the HDSL2/SHDSL Line MIB to other MIBs . . 3 3.1 Relationship of the HDSL2/SHDSL Line MIB to other MIBs . . 3
3.1.1 General IF-MIB Integration (RFC 2863) . . . . . . . . 4 3.1.1 General IF-MIB Integration (RFC 2863) . . . . . . . . 4
3.1.2 Usage of ifTable . . . . . . . . . . . . . . . . . . . 4 3.1.2 Usage of ifTable . . . . . . . . . . . . . . . . . . . 4
3.2 IANA Considerations . . . . . . . . . . . . . . . . . . . 5 3.2 IANA Considerations . . . . . . . . . . . . . . . . . . . 5
4. Conventions used in the MIB . . . . . . . . . . . . . . . . . 5 4. Conventions used in the MIB . . . . . . . . . . . . . . . . . 6
4.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . 6 4.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . 6
4.2 Textual Conventions . . . . . . . . . . . . . . . . . . . 6 4.2 Textual Conventions . . . . . . . . . . . . . . . . . . . 6
4.3 Structure . . . . . . . . . . . . . . . . . . . . . . . . 7 4.3 Structure . . . . . . . . . . . . . . . . . . . . . . . . 7
4.3.1 Line Topology . . . . . . . . . . . . . . . . . . . . 10 4.3.1 Line Topology . . . . . . . . . . . . . . . . . . . . 10
4.4 Counters, Interval Buckets and Thresholds . . . . . . . . 10 4.4 Counters, Interval Buckets and Thresholds . . . . . . . . 11
4.5 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.5 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.6 Notifications . . . . . . . . . . . . . . . . . . . . . . 12 4.6 Notifications . . . . . . . . . . . . . . . . . . . . . . 12
5. Conformance and Compliance . . . . . . . . . . . . . . . . . . 14 5. Conformance and Compliance . . . . . . . . . . . . . . . . . . 14
6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 15
7. Implementation Analysis . . . . . . . . . . . . . . . . . . . 65 7. Implementation Analysis . . . . . . . . . . . . . . . . . . . 66
8. Security Considerations . . . . . . . . . . . . . . . . . . . 66 8. Security Considerations . . . . . . . . . . . . . . . . . . . 66
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 68 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 71
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 69 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 72
10.1 Normative References . . . . . . . . . . . . . . . . . . . . 69 10.1 Normative References . . . . . . . . . . . . . . . . . . . 72
10.2 Informative References . . . . . . . . . . . . . . . . . . . 70 10.2 Informative References . . . . . . . . . . . . . . . . . . 73
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 73
Intellectual Property and Copyright Statements . . . . . . . . 72 Intellectual Property and Copyright Statements . . . . . . . . 75
1. Introduction 1. Introduction
This document defines a Management Information Base (MIB) module for This document defines a Management Information Base (MIB) module for
use with network management protocols in the Internet community. The use with network management protocols in the Internet community. The
MIB module described in RFC 3276 [RFC3276] describes objects used for MIB module described in RFC 3276 [RFC3276] describes objects used for
managing High Bit-Rate DSL - 2nd generation (HDSL2) [T1E1.4] and managing High Bit-Rate DSL - 2nd generation (HDSL2) [T1E1.4] and
Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces
[G.991.2]. This document obsoletes RFC 3276 [RFC3276] which supports [G.991.2]. This document obsoletes RFC 3276 [RFC3276] which supports
G.shdsl in that the MIB module described herein supports G.shdsl.bis G.shdsl in that the MIB module described herein supports G.shdsl.bis
as described in the G.991.2 [G.991.2]. In addition, objects have as described in the G.991.2 [G.991.2]. In addition, objects have
been added to improve the management of SHDSL lines. been added to improve the management of SHDSL lines.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to Section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
skipping to change at page 4, line 30 skipping to change at page 4, line 30
Note that the ifFixedLengthGroup from RFC 2863 [RFC2863] MUST be Note that the ifFixedLengthGroup from RFC 2863 [RFC2863] MUST be
supported and that the ifRcvAddressGroup does not apply to this MIB. supported and that the ifRcvAddressGroup does not apply to this MIB.
3.1.2 Usage of ifTable 3.1.2 Usage of ifTable
The MIB branch identified by this ifType contains tables appropriate The MIB branch identified by this ifType contains tables appropriate
for this interface type. Most such tables extend the ifEntry table, for this interface type. Most such tables extend the ifEntry table,
and are indexed by ifIndex. For interfaces in systems implementing and are indexed by ifIndex. For interfaces in systems implementing
this MIB, those table entries indexed by ifIndex MUST be persistent. this MIB, those table entries indexed by ifIndex MUST be persistent.
The following attributes are part of the mandatory ifGeneral group in The following attributes are part of the mandatory
RFC 2863 [RFC2863], and are not duplicated in the HDSL2/SHDSL Line ifGeneralInformationGroup in RFC 2863 [RFC2863], and are not
MIB. duplicated in the HDSL2/SHDSL Line MIB.
=================================================================== ==================================================================
ifIndex Interface index. ifIndex Interface index.
ifDescr See interfaces MIB [RFC2863]. ifDescr See interfaces MIB [RFC2863].
ifType hdsl2(168) or shdsl(169). ifType hdsl2(168) or shdsl(169).
ifSpeed Set as appropriate. ifSpeed Set as appropriate.
(This is fixed at 1552000 for HDSL2 (This is fixed at 1552000 for HDSL2
lines) lines)
skipping to change at page 5, line 28 skipping to change at page 5, line 28
with zero length. with zero length.
ifAdminStatus See interfaces MIB [RFC2863]. ifAdminStatus See interfaces MIB [RFC2863].
ifOperStatus See interfaces MIB [RFC2863]. ifOperStatus See interfaces MIB [RFC2863].
ifLastChange See interfaces MIB [RFC2863]. ifLastChange See interfaces MIB [RFC2863].
ifName See interfaces MIB [RFC2863]. ifName See interfaces MIB [RFC2863].
ifAlias See interfaces MIB [RFC2863].
ifLinkUpDownTrapEnable Default to enabled(1). ifLinkUpDownTrapEnable Default to enabled(1).
ifHighSpeed Set as appropriate. ifHighSpeed Set as appropriate.
(For HDSL2 lines, this is fixed at 2) (For HDSL2 lines, this is fixed at 2)
ifConnectorPresent Set as appropriate. ifConnectorPresent Set as appropriate.
=================================================================== ==================================================================
Figure 1: Use of ifTable Objects Figure 1: Use of ifTable Objects
3.2 IANA Considerations 3.2 IANA Considerations
The HDSL2-SHDSL-LINE-MIB module requires the allocation of a single The HDSL2-SHDSL-LINE-MIB module requires the allocation of a single
object identifier for its MODULE-IDENTITY. The IANA has allocated object identifier for its MODULE-IDENTITY. The IANA has allocated
this object identifier in the transmission subtree (48), defined in this object identifier in the transmission subtree (48), defined in
the SNMPv2-SMI MIB module. the SNMPv2-SMI MIB module.
The assignment was in fact done when RFC 3276 was published, and this The assignment was in fact done when RFC 3276 was published, and this
skipping to change at page 8, line 31 skipping to change at page 8, line 32
o Segment Endpoint Configuration Group: o Segment Endpoint Configuration Group:
This group supports MIB objects for configuring parameters for the This group supports MIB objects for configuring parameters for the
HDSL2/SHDSL segment endpoints. It contains the following table: HDSL2/SHDSL segment endpoints. It contains the following table:
- hdsl2ShdslEndpointConfTable - hdsl2ShdslEndpointConfTable
o Segment Endpoint Current Status/Performance Group: o Segment Endpoint Current Status/Performance Group:
This group supports MIB objects that provide the current status/ This group supports MIB objects that provide the current
performance information relating to segment endpoints. It status/performance information relating to segment endpoints. It
contains the following table: contains the following table:
- hdsl2ShdslEndpointCurrTable - hdsl2ShdslEndpointCurrTable
o Segment Endpoint 15-Minute Interval Status/Performance Group: o Segment Endpoint 15-Minute Interval Status/Performance Group:
This group supports MIB objects that provide historic status/ This group supports MIB objects that provide historic
performance information relating to segment endpoints in 15-minute status/performance information relating to segment endpoints in
intervals. It contains the following table: 15-minute intervals. It contains the following table:
- hdsl2Shdsl15MinIntervalTable - hdsl2Shdsl15MinIntervalTable
o Segment Endpoint 1-Day Interval Status/Performance Group: o Segment Endpoint 1-Day Interval Status/Performance Group:
This group supports MIB objects that provide historic status/ This group supports MIB objects that provide historic
performance information relating to segment endpoints in 1-day status/performance information relating to segment endpoints in
intervals. It contains the following table: 1-day intervals. It contains the following table:
- hdsl2Shdsl1DayIntervalTable - hdsl2Shdsl1DayIntervalTable
o Maintenance Group: o Maintenance Group:
This group supports MIB objects for performing maintenance This group supports MIB objects for performing maintenance
operations such as loopbacks for HDSL2/SHDSL lines. It contains operations such as loopbacks for HDSL2/SHDSL lines. It contains
the following table(s): the following table(s):
- hdsl2ShdslEndpointMaintTable - hdsl2ShdslEndpointMaintTable
- hdsl2ShdslUnitMaintTable - hdsl2ShdslUnitMaintTable
o Span Configuration Profile Group: o Span Configuration Profile Group:
skipping to change at page 12, line 10 skipping to change at page 12, line 14
parameters are only applicable for SHDSL, the support for span parameters are only applicable for SHDSL, the support for span
configuration profiles are optional for HDSL2 interfaces. configuration profiles are optional for HDSL2 interfaces.
Note that the configuration of the span dictates the behavior for Note that the configuration of the span dictates the behavior for
each individual segment endpoint in the span. If a different each individual segment endpoint in the span. If a different
configuration is provisioned for any given segment endpoint within configuration is provisioned for any given segment endpoint within
the span, the new configuration for this segment endpoint will the span, the new configuration for this segment endpoint will
override the span configuration for this segment endpoint only. override the span configuration for this segment endpoint only.
o Segment Endpoint Alarm Configuration Profiles - These profiles o Segment Endpoint Alarm Configuration Profiles - These profiles
contain parameters for configuring alarm thresholds for HDSL2/ contain parameters for configuring alarm thresholds for
SHDSL segment endpoints. These profiles are defined in the HDSL2/SHDSL segment endpoints. These profiles are defined in the
hdsl2ShdslEndpointAlarmConfProfileTable. hdsl2ShdslEndpointAlarmConfProfileTable.
The index value for this profile is a locally-unique The index value for this profile is a locally-unique
administratively assigned name for the profile having the textual administratively assigned name for the profile having the textual
convention 'SnmpAdminString' (RFC 3411 [RFC3411]). convention 'SnmpAdminString' (RFC 3411 [RFC3411]).
One or more lines may be configured to share parameters of a single One or more lines may be configured to share parameters of a single
profile (e.g., hdsl2ShdslEndpointAlarmConfProfile = 'silver') by profile (e.g., hdsl2ShdslEndpointAlarmConfProfile = 'silver') by
setting its hdsl2ShdslEndpointAlarmConfProfile objects to the value setting its hdsl2ShdslEndpointAlarmConfProfile objects to the value
of this profile. If a change is made to the profile, all lines that of this profile. If a change is made to the profile, all lines that
skipping to change at page 12, line 47 skipping to change at page 12, line 51
tables. tables.
Profile changes MUST take effect immediately. These changes MAY Profile changes MUST take effect immediately. These changes MAY
result in a restart (hard reset or soft restart) of the units on the result in a restart (hard reset or soft restart) of the units on the
line. line.
4.6 Notifications 4.6 Notifications
The ability to generate the SNMP notifications coldStart/WarmStart The ability to generate the SNMP notifications coldStart/WarmStart
(per [RFC3418]) which are per agent (e.g., per Digital Subscriber (per [RFC3418]) which are per agent (e.g., per Digital Subscriber
Line Access Multiplexer, or DSLAM, in such a device), and linkUp/ Line Access Multiplexer, or DSLAM, in such a device), and
linkDown (per [RFC2863]) which are per interface (i.e., HDSL2/SHDSL linkUp/linkDown (per [RFC2863]) which are per interface (i.e.,
line) is required. HDSL2/SHDSL line) is required.
A linkDown notification MAY be generated whenever any of ES, SES, CRC A linkDown notification MAY be generated whenever any of ES, SES, CRC
Anomaly, LOSW, or UAS event occurs. The corresponding linkUp Anomaly, LOSW, or UAS event occurs. The corresponding linkUp
notification MAY be sent when all link failure conditions are notification MAY be sent when all link failure conditions are
cleared. cleared.
The notifications defined in this MIB are for initialization failure The notifications defined in this MIB are for initialization failure
and for the threshold crossings associated with the following events: and for the threshold crossings associated with the following events:
ES, SES, CRC Anomaly, LOSW, and UAS. Each threshold has its own ES, SES, CRC Anomaly, LOSW, and UAS. Each threshold has its own
enable/threshold value. When that value is 0, the notification is enable/threshold value. When that value is 0, the notification is
skipping to change at page 13, line 41 skipping to change at page 13, line 45
this has no impact. For repeaters, this implies an implementation this has no impact. For repeaters, this implies an implementation
variance where the agent in the terminal unit is responsible for variance where the agent in the terminal unit is responsible for
detecting a threshold crossing. As the reporting of a repeater detecting a threshold crossing. As the reporting of a repeater
detected alarm condition to the polling terminal unit occurs in the detected alarm condition to the polling terminal unit occurs in the
same EOC message as the reporting of the current SNR Margin and Loop same EOC message as the reporting of the current SNR Margin and Loop
Attenuation values, it is anticipated that this will have very little Attenuation values, it is anticipated that this will have very little
impact on agent implementation. impact on agent implementation.
A threshold notification occurs whenever the corresponding current A threshold notification occurs whenever the corresponding current
15-minute interval error counter becomes equal to, or exceeds the 15-minute interval error counter becomes equal to, or exceeds the
threshold value. One notification may be sent per interval per threshold value. Only one notification SHOULD be sent per interval
interface. Since the current 15-minute counter is reset to 0 every per interface. Since the current 15-minute counter is reset to 0
15 minutes, and if the condition persists, the notification may recur every 15 minutes, and if the condition persists, the notification may
as often as every 15 minutes. For example, to get a notification recur as often as every 15 minutes. For example, to get a
whenever a "loss of" event occurs (but at most once every 15 notification whenever a "loss of" event occurs (but at most once
minutes), set the corresponding threshold to 1. The agent will every 15 minutes), set the corresponding threshold to 1. The agent
generate a notification when the event originally occurs. will generate a notification when the event originally occurs.
Notifications, other than the threshold notifications listed above,
SHOULD be rate limited (throttled) such that there is at least a
one-minute gap between the generation of consecutive notification of
the same event. When notifications are rate limited, they are
dropped and not queued for sending at a future time. This is
intended to be a general rate-limiting statement for notifications
that have no explicit rate limiting assertions in this document
otherwise.
Note that the Network Management System, or NMS, may receive a Note that the Network Management System, or NMS, may receive a
linkDown notification, as well, if enabled (via linkDown notification, as well, if enabled (via
ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15
minute interval, the counter is reset. When the first second goes by minute interval, the counter is reset. When the first second goes by
and the event occurs, the current interval bucket will be 1, which and the event occurs, the current interval bucket will be 1, which
equals the threshold, and the notification will be sent again. equals the threshold, and the notification will be sent again.
A hdsl2ShdslSpanInvalidNumRepeaters notification may be generated A hdsl2ShdslSpanInvalidNumRepeaters notification may be generated
following completion of the discovery phase if the number of following completion of the discovery phase if the number of
skipping to change at page 15, line 8 skipping to change at page 15, line 18
HDSL2-SHDSL-LINE-MIB DEFINITIONS ::= BEGIN HDSL2-SHDSL-LINE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Counter32, Counter32,
Unsigned32, Unsigned32,
Gauge32, Gauge32,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
Integer32, Integer32,
transmission FROM SNMPv2-SMI transmission
FROM SNMPv2-SMI
RowStatus, RowStatus,
TEXTUAL-CONVENTION FROM SNMPv2-TC TEXTUAL-CONVENTION
ifIndex FROM IF-MIB FROM SNMPv2-TC
ifIndex
FROM IF-MIB
PerfCurrentCount, PerfCurrentCount,
PerfIntervalCount FROM PerfHist-TC-MIB PerfIntervalCount
SnmpAdminString FROM SNMP-FRAMEWORK-MIB FROM PerfHist-TC-MIB
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF; NOTIFICATION-GROUP
FROM SNMPv2-CONF;
hdsl2ShdslMIB MODULE-IDENTITY hdsl2ShdslMIB MODULE-IDENTITY
LAST-UPDATED "200410060000Z" -- October 6, 2004 LAST-UPDATED "200502210000Z" -- February 21, 2005
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
WG-URL: WG-URL:
http://www.ietf.org/html.charters/adslmib-charter.html http://www.ietf.org/html.charters/adslmib-charter.html
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
Postal: P.O. Box 37324 Postal: P.O. Box 37324
Raleigh NC 27627-7324 Raleigh NC 27627-7324 USA
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
Co-Chair Bob Ray
PESA Switching Systems, Inc.
Postal 330-A Wynn Drive
Huntsville, AL 35805 USA
Phone +1 256 726 9200 ext. 142
Co-editor: Clay Sikes Co-editor: Clay Sikes
Paradyne Corporation Paradyne Corporation
Postal: 8545 126th Ave. N. Postal: 8545 126th Ave. N.
Largo, FL 33772 USA Largo, FL 33772 USA
Email: csikes@paradyne.com Email: csikes@paradyne.com
Phone: +1 727 530 8257 Phone: +1 727 530 8257
Co-editor: Bob Ray Co-editor: Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
Postal: 330-A Wynn Drive Postal: 330-A Wynn Drive
Huntsville, AL 35805 USA Huntsville, AL 35805 USA
Email: rray@pesa.com Email: rray@pesa.com
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Co-editor: Rajesh Abbi Co-editor: Rajesh Abbi
Alcatel USA Alcatel USA
Postal: 2912 Wake Forest Road Postal: 2912 Wake Forest Road
Raleigh, NC 27609-7860 USA Raleigh, NC 27609-7860 USA
Email: Rajesh.Abbi@alcatel.com Email: Rajesh.Abbi@alcatel.com
Phone: +1 919 850 6194 Phone: +1 919 850 6194"
"
DESCRIPTION DESCRIPTION
"This MIB module defines a collection of objects for managing "This MIB module defines a collection of objects for managing
HDSL2/SHDSL lines. An agent may reside at either end of the HDSL2/SHDSL lines. An agent may reside at either end of the
line, however the MIB is designed to require no management line, however the MIB is designed to require no management
communication between the modems beyond that inherent in the communication between the modems beyond that inherent in the
low-level EOC line protocol as defined in ANSI T1E1.4/2000-006 low-level EOC line protocol as defined in ANSI T1E1.4/2000-006
(for HDSL2 lines), or in ITU G.991.2 (for SHDSL lines). (for HDSL2 lines), or in ITU G.991.2 (for SHDSL lines).
Copyright (C) The Internet Society (2004). This version of Copyright (C) The Internet Society (2005). This version of
this MIB module is part of RFC xxxx; see the RFC itself for this MIB module is part of RFC xxxx; see the RFC itself for
full legal notices." full legal notices."
REVISION "200410060000Z" -- October 6, 2004 REVISION "200502210000Z" -- February 21, 2005
DESCRIPTION "This version, published as RFC xxxx. DESCRIPTION "This version, published as RFC xxxx.
The following changes have been made in this version: The following changes have been made in this version:
1. Added a 3rd and 4th wire pair. 1. Added a 3rd and 4th wire pair.
2. Modified all rates such that their rates are only 2. Modified all rates such that their rates are only
constrained by an unsigned 32-bit value and not by constrained by an unsigned 32-bit value and not by
what today's perceived technology limitations are. what today's perceived technology limitations are.
3. Clarified that the rates from RFC 3276 include 3. Clarified that the rates from RFC 3276 include
payload and any applicable framing and added payload and any applicable framing and added
objects for payload-only rates. objects for payload-only rates.
4. Added an object to indicate whether or not the 4. Added an object to indicate whether or not the
skipping to change at page 20, line 25 skipping to change at page 20, line 47
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslSpanConfTable. Each entry "An entry in the hdsl2ShdslSpanConfTable. Each entry
represents the complete Span in a single HDSL2/SHDSL line. represents the complete Span in a single HDSL2/SHDSL line.
It is indexed by the ifIndex of the associated HDSL2/SHDSL It is indexed by the ifIndex of the associated HDSL2/SHDSL
line." line."
INDEX { ifIndex } INDEX { ifIndex }
::= { hdsl2ShdslSpanConfTable 1 } ::= { hdsl2ShdslSpanConfTable 1 }
Hdsl2ShdslSpanConfEntry ::= Hdsl2ShdslSpanConfEntry ::
SEQUENCE SEQUENCE
{ {
hdsl2ShdslSpanConfNumRepeaters Unsigned32, hdsl2ShdslSpanConfNumRepeaters Unsigned32,
hdsl2ShdslSpanConfProfile SnmpAdminString, hdsl2ShdslSpanConfProfile SnmpAdminString,
hdsl2ShdslSpanConfAlarmProfile SnmpAdminString hdsl2ShdslSpanConfAlarmProfile SnmpAdminString
} }
hdsl2ShdslSpanConfNumRepeaters OBJECT-TYPE hdsl2ShdslSpanConfNumRepeaters OBJECT-TYPE
SYNTAX Unsigned32(0..8) SYNTAX Unsigned32(0..8)
UNITS "repeaters" UNITS "repeaters"
skipping to change at page 22, line 14 skipping to change at page 22, line 36
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslSpanStatusTable. Each entry "An entry in the hdsl2ShdslSpanStatusTable. Each entry
represents the complete span in a single HDSL2/SHDSL line. represents the complete span in a single HDSL2/SHDSL line.
It is indexed by the ifIndex of the associated HDSL2/SHDSL It is indexed by the ifIndex of the associated HDSL2/SHDSL
line." line."
INDEX { ifIndex } INDEX { ifIndex }
::= { hdsl2ShdslSpanStatusTable 1 } ::= { hdsl2ShdslSpanStatusTable 1 }
Hdsl2ShdslSpanStatusEntry ::= Hdsl2ShdslSpanStatusEntry ::
SEQUENCE SEQUENCE
{ {
hdsl2ShdslStatusNumAvailRepeaters Unsigned32, hdsl2ShdslStatusNumAvailRepeaters Unsigned32,
hdsl2ShdslStatusMaxAttainableLineRate Unsigned32, hdsl2ShdslStatusMaxAttainableLineRate Unsigned32,
hdsl2ShdslStatusActualLineRate Unsigned32, hdsl2ShdslStatusActualLineRate Unsigned32,
hdsl2ShdslStatusTransmissionModeCurrent hdsl2ShdslStatusTransmissionModeCurrent
Hdsl2ShdslTransmissionModeType, Hdsl2ShdslTransmissionModeType,
hdsl2ShdslStatusMaxAttainablePayloadRate Unsigned32, hdsl2ShdslStatusMaxAttainablePayloadRate Unsigned32,
hdsl2ShdslStatusActualPayloadRate Unsigned32 hdsl2ShdslStatusActualPayloadRate Unsigned32
} }
skipping to change at page 23, line 7 skipping to change at page 23, line 29
and any applicable framing overhead." and any applicable framing overhead."
::= { hdsl2ShdslSpanStatusEntry 2 } ::= { hdsl2ShdslSpanStatusEntry 2 }
hdsl2ShdslStatusActualLineRate OBJECT-TYPE hdsl2ShdslStatusActualLineRate OBJECT-TYPE
SYNTAX Unsigned32(0..4294967295) SYNTAX Unsigned32(0..4294967295)
UNITS "bps" UNITS "bps"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Contains the actual line rate in this HDSL2/SHDSL span. This "Contains the actual line rate in this HDSL2/SHDSL span. This
should equal ifSpeed. This rate includes payload (user data) SHOULD equal ifSpeed. This rate includes payload (user data)
and any applicable framing overhead" and any applicable framing overhead"
::= { hdsl2ShdslSpanStatusEntry 3 } ::= { hdsl2ShdslSpanStatusEntry 3 }
hdsl2ShdslStatusTransmissionModeCurrent OBJECT-TYPE hdsl2ShdslStatusTransmissionModeCurrent OBJECT-TYPE
SYNTAX Hdsl2ShdslTransmissionModeType SYNTAX Hdsl2ShdslTransmissionModeType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Contains the current Power Spectral Density (PSD) regional "Contains the current Power Spectral Density (PSD) regional
setting of the HDSL2/SHDSL span." setting of the HDSL2/SHDSL span."
skipping to change at page 24, line 33 skipping to change at page 25, line 7
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslInventoryTable. Each entry "An entry in the hdsl2ShdslInventoryTable. Each entry
represents inventory information for a single unit in a represents inventory information for a single unit in a
HDSL2/SHDSL line. It is indexed by the ifIndex of the HDSL2/SHDSL line. It is indexed by the ifIndex of the
HDSL2/SHDSL line and the Hdsl2ShdslUnitId of the HDSL2/SHDSL line and the Hdsl2ShdslUnitId of the
associated unit." associated unit."
INDEX { ifIndex, hdsl2ShdslInvIndex } INDEX { ifIndex, hdsl2ShdslInvIndex }
::= { hdsl2ShdslInventoryTable 1 } ::= { hdsl2ShdslInventoryTable 1 }
Hdsl2ShdslInventoryEntry ::= Hdsl2ShdslInventoryEntry ::
SEQUENCE SEQUENCE
{ {
hdsl2ShdslInvIndex Hdsl2ShdslUnitId, hdsl2ShdslInvIndex Hdsl2ShdslUnitId,
hdsl2ShdslInvVendorID OCTET STRING, hdsl2ShdslInvVendorID OCTET STRING,
hdsl2ShdslInvVendorModelNumber OCTET STRING, hdsl2ShdslInvVendorModelNumber OCTET STRING,
hdsl2ShdslInvVendorSerialNumber OCTET STRING, hdsl2ShdslInvVendorSerialNumber OCTET STRING,
hdsl2ShdslInvVendorEOCSoftwareVersion Integer32, hdsl2ShdslInvVendorEOCSoftwareVersion Integer32,
hdsl2ShdslInvStandardVersion Integer32, hdsl2ShdslInvStandardVersion Integer32,
hdsl2ShdslInvVendorListNumber OCTET STRING, hdsl2ShdslInvVendorListNumber OCTET STRING,
hdsl2ShdslInvVendorIssueNumber OCTET STRING, hdsl2ShdslInvVendorIssueNumber OCTET STRING,
skipping to change at page 28, line 23 skipping to change at page 28, line 45
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslEndpointConfTable. Each entry "An entry in the hdsl2ShdslEndpointConfTable. Each entry
represents a single segment endpoint in a HDSL2/SHDSL line. represents a single segment endpoint in a HDSL2/SHDSL line.
It is indexed by the ifIndex of the HDSL2/SHDSL line, the It is indexed by the ifIndex of the HDSL2/SHDSL line, the
UnitId of the associated unit, the side of the unit, and the UnitId of the associated unit, the side of the unit, and the
wire pair of the associated modem." wire pair of the associated modem."
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide,
hdsl2ShdslEndpointWirePair} hdsl2ShdslEndpointWirePair}
::= { hdsl2ShdslEndpointConfTable 1 } ::= { hdsl2ShdslEndpointConfTable 1 }
Hdsl2ShdslEndpointConfEntry ::= Hdsl2ShdslEndpointConfEntry ::
SEQUENCE SEQUENCE
{ {
hdsl2ShdslEndpointSide Hdsl2ShdslUnitSide, hdsl2ShdslEndpointSide Hdsl2ShdslUnitSide,
hdsl2ShdslEndpointWirePair Hdsl2ShdslWirePair, hdsl2ShdslEndpointWirePair Hdsl2ShdslWirePair,
hdsl2ShdslEndpointAlarmConfProfile SnmpAdminString hdsl2ShdslEndpointAlarmConfProfile SnmpAdminString
} }
hdsl2ShdslEndpointSide OBJECT-TYPE hdsl2ShdslEndpointSide OBJECT-TYPE
SYNTAX Hdsl2ShdslUnitSide SYNTAX Hdsl2ShdslUnitSide
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The side of the unit associated with this segment endpoint - "The side of the unit associated with this segment endpoint -
Network/Customer side - as per the Hdsl2ShdslUnitSide textual Network/Customer side - as per the Hdsl2ShdslUnitSide textual
convention." convention."
::= { hdsl2ShdslEndpointConfEntry 1 } ::= { hdsl2ShdslEndpointConfEntry 1 }
skipping to change at page 30, line 4 skipping to change at page 30, line 24
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslEndpointCurrTable. Each entry "An entry in the hdsl2ShdslEndpointCurrTable. Each entry
contains status and performance information relating to a contains status and performance information relating to a
single segment endpoint. It is indexed by the ifIndex of the single segment endpoint. It is indexed by the ifIndex of the
HDSL2/SHDSL line, the UnitId of the associated unit, the side HDSL2/SHDSL line, the UnitId of the associated unit, the side
of the unit, and the wire pair of the associated modem." of the unit, and the wire pair of the associated modem."
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide,
hdsl2ShdslEndpointWirePair } hdsl2ShdslEndpointWirePair }
::= { hdsl2ShdslEndpointCurrTable 1 } ::= { hdsl2ShdslEndpointCurrTable 1 }
Hdsl2ShdslEndpointCurrEntry ::=
Hdsl2ShdslEndpointCurrEntry ::
SEQUENCE SEQUENCE
{ {
hdsl2ShdslEndpointCurrAtn Integer32, hdsl2ShdslEndpointCurrAtn Integer32,
hdsl2ShdslEndpointCurrSnrMgn Integer32, hdsl2ShdslEndpointCurrSnrMgn Integer32,
hdsl2ShdslEndpointCurrStatus BITS, hdsl2ShdslEndpointCurrStatus BITS,
hdsl2ShdslEndpointES Counter32, hdsl2ShdslEndpointES Counter32,
hdsl2ShdslEndpointSES Counter32, hdsl2ShdslEndpointSES Counter32,
hdsl2ShdslEndpointCRCanomalies Counter32, hdsl2ShdslEndpointCRCanomalies Counter32,
hdsl2ShdslEndpointLOSWS Counter32, hdsl2ShdslEndpointLOSWS Counter32,
hdsl2ShdslEndpointUAS Counter32, hdsl2ShdslEndpointUAS Counter32,
skipping to change at page 37, line 22 skipping to change at page 37, line 44
hdsl2Shdsl15MinIntervalEntry OBJECT-TYPE hdsl2Shdsl15MinIntervalEntry OBJECT-TYPE
SYNTAX Hdsl2Shdsl15MinIntervalEntry SYNTAX Hdsl2Shdsl15MinIntervalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2Shdsl15MinIntervalTable." "An entry in the hdsl2Shdsl15MinIntervalTable."
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide,
hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber} hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber}
::= { hdsl2Shdsl15MinIntervalTable 1 } ::= { hdsl2Shdsl15MinIntervalTable 1 }
Hdsl2Shdsl15MinIntervalEntry ::= Hdsl2Shdsl15MinIntervalEntry ::
SEQUENCE SEQUENCE
{ {
hdsl2Shdsl15MinIntervalNumber Unsigned32, hdsl2Shdsl15MinIntervalNumber Unsigned32,
hdsl2Shdsl15MinIntervalES PerfIntervalCount, hdsl2Shdsl15MinIntervalES PerfIntervalCount,
hdsl2Shdsl15MinIntervalSES PerfIntervalCount, hdsl2Shdsl15MinIntervalSES PerfIntervalCount,
hdsl2Shdsl15MinIntervalCRCanomalies PerfIntervalCount, hdsl2Shdsl15MinIntervalCRCanomalies PerfIntervalCount,
hdsl2Shdsl15MinIntervalLOSWS PerfIntervalCount, hdsl2Shdsl15MinIntervalLOSWS PerfIntervalCount,
hdsl2Shdsl15MinIntervalUAS PerfIntervalCount hdsl2Shdsl15MinIntervalUAS PerfIntervalCount
} }
skipping to change at page 39, line 20 skipping to change at page 39, line 43
hdsl2Shdsl1DayIntervalEntry OBJECT-TYPE hdsl2Shdsl1DayIntervalEntry OBJECT-TYPE
SYNTAX Hdsl2Shdsl1DayIntervalEntry SYNTAX Hdsl2Shdsl1DayIntervalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2Shdsl1DayIntervalTable." "An entry in the hdsl2Shdsl1DayIntervalTable."
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide,
hdsl2ShdslEndpointWirePair, hdsl2Shdsl1DayIntervalNumber } hdsl2ShdslEndpointWirePair, hdsl2Shdsl1DayIntervalNumber }
::= { hdsl2Shdsl1DayIntervalTable 1 } ::= { hdsl2Shdsl1DayIntervalTable 1 }
Hdsl2Shdsl1DayIntervalEntry ::= Hdsl2Shdsl1DayIntervalEntry ::
SEQUENCE SEQUENCE
{ {
hdsl2Shdsl1DayIntervalNumber Unsigned32, hdsl2Shdsl1DayIntervalNumber Unsigned32,
hdsl2Shdsl1DayIntervalMoniSecs Hdsl2ShdslPerfTimeElapsed, hdsl2Shdsl1DayIntervalMoniSecs Hdsl2ShdslPerfTimeElapsed,
hdsl2Shdsl1DayIntervalES Hdsl2Shdsl1DayIntervalCount, hdsl2Shdsl1DayIntervalES Hdsl2Shdsl1DayIntervalCount,
hdsl2Shdsl1DayIntervalSES Hdsl2Shdsl1DayIntervalCount, hdsl2Shdsl1DayIntervalSES Hdsl2Shdsl1DayIntervalCount,
hdsl2Shdsl1DayIntervalCRCanomalies Hdsl2Shdsl1DayIntervalCount, hdsl2Shdsl1DayIntervalCRCanomalies Hdsl2Shdsl1DayIntervalCount,
hdsl2Shdsl1DayIntervalLOSWS Hdsl2Shdsl1DayIntervalCount, hdsl2Shdsl1DayIntervalLOSWS Hdsl2Shdsl1DayIntervalCount,
hdsl2Shdsl1DayIntervalUAS Hdsl2Shdsl1DayIntervalCount hdsl2Shdsl1DayIntervalUAS Hdsl2Shdsl1DayIntervalCount
} }
skipping to change at page 41, line 40 skipping to change at page 42, line 15
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslEndpointMaintTable. Each entry "An entry in the hdsl2ShdslEndpointMaintTable. Each entry
corresponds to a single segment endpoint, and is indexed by the corresponds to a single segment endpoint, and is indexed by the
ifIndex of the HDSL2/SHDSL line, the UnitId of the associated ifIndex of the HDSL2/SHDSL line, the UnitId of the associated
unit and the side of the unit." unit and the side of the unit."
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide } INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide }
::= { hdsl2ShdslEndpointMaintTable 1 } ::= { hdsl2ShdslEndpointMaintTable 1 }
Hdsl2ShdslEndpointMaintEntry ::= Hdsl2ShdslEndpointMaintEntry ::
SEQUENCE SEQUENCE
{ {
hdsl2ShdslMaintLoopbackConfig INTEGER, hdsl2ShdslMaintLoopbackConfig INTEGER,
hdsl2ShdslMaintTipRingReversal INTEGER, hdsl2ShdslMaintTipRingReversal INTEGER,
hdsl2ShdslMaintPowerBackOff INTEGER, hdsl2ShdslMaintPowerBackOff INTEGER,
hdsl2ShdslMaintSoftRestart INTEGER hdsl2ShdslMaintSoftRestart INTEGER
} }
hdsl2ShdslMaintLoopbackConfig OBJECT-TYPE hdsl2ShdslMaintLoopbackConfig OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
skipping to change at page 43, line 35 skipping to change at page 44, line 10
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslUnitMaintTable. Each entry "An entry in the hdsl2ShdslUnitMaintTable. Each entry
corresponds to a single unit, and is indexed by the corresponds to a single unit, and is indexed by the
ifIndex of the HDSL2/SHDSL line and the UnitId of the ifIndex of the HDSL2/SHDSL line and the UnitId of the
associated unit." associated unit."
INDEX { ifIndex, hdsl2ShdslInvIndex } INDEX { ifIndex, hdsl2ShdslInvIndex }
::= { hdsl2ShdslUnitMaintTable 1 } ::= { hdsl2ShdslUnitMaintTable 1 }
Hdsl2ShdslUnitMaintEntry ::= Hdsl2ShdslUnitMaintEntry ::
SEQUENCE SEQUENCE
{ {
hdsl2ShdslMaintLoopbackTimeout Integer32, hdsl2ShdslMaintLoopbackTimeout Integer32,
hdsl2ShdslMaintUnitPowerSource INTEGER hdsl2ShdslMaintUnitPowerSource INTEGER
} }
hdsl2ShdslMaintLoopbackTimeout OBJECT-TYPE hdsl2ShdslMaintLoopbackTimeout OBJECT-TYPE
SYNTAX Integer32(0..4095) SYNTAX Integer32(0..4095)
UNITS "minutes" UNITS "minutes"
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 44, line 48 skipping to change at page 45, line 24
parameters. The configuration parameters in a profile are parameters. The configuration parameters in a profile are
applied to those lines referencing that profile (see the applied to those lines referencing that profile (see the
hdsl2ShdslSpanConfProfile object). Profiles may be hdsl2ShdslSpanConfProfile object). Profiles may be
created/deleted using the row creation/deletion mechanism created/deleted using the row creation/deletion mechanism
via hdsl2ShdslSpanConfProfileRowStatus. If an active via hdsl2ShdslSpanConfProfileRowStatus. If an active
entry is referenced in hdsl2ShdslSpanConfProfile, the entry is referenced in hdsl2ShdslSpanConfProfile, the
entry MUST remain active until all references are removed." entry MUST remain active until all references are removed."
INDEX { IMPLIED hdsl2ShdslSpanConfProfileName } INDEX { IMPLIED hdsl2ShdslSpanConfProfileName }
::= { hdsl2ShdslSpanConfProfileTable 1 } ::= { hdsl2ShdslSpanConfProfileTable 1 }
Hdsl2ShdslSpanConfProfileEntry ::= Hdsl2ShdslSpanConfProfileEntry ::
SEQUENCE SEQUENCE
{ {
hdsl2ShdslSpanConfProfileName SnmpAdminString, hdsl2ShdslSpanConfProfileName SnmpAdminString,
hdsl2ShdslSpanConfWireInterface INTEGER, hdsl2ShdslSpanConfWireInterface INTEGER,
hdsl2ShdslSpanConfMinLineRate Unsigned32, hdsl2ShdslSpanConfMinLineRate Unsigned32,
hdsl2ShdslSpanConfMaxLineRate Unsigned32, hdsl2ShdslSpanConfMaxLineRate Unsigned32,
hdsl2ShdslSpanConfPSD INTEGER, hdsl2ShdslSpanConfPSD INTEGER,
hdsl2ShdslSpanConfTransmissionMode hdsl2ShdslSpanConfTransmissionMode
Hdsl2ShdslTransmissionModeType, Hdsl2ShdslTransmissionModeType,
hdsl2ShdslSpanConfRemoteEnabled INTEGER, hdsl2ShdslSpanConfRemoteEnabled INTEGER,
skipping to change at page 49, line 9 skipping to change at page 49, line 33
SYNTAX BITS SYNTAX BITS
{ {
currCondDown(0), currCondDown(0),
worstCaseDown(1), worstCaseDown(1),
currCondUp(2), currCondUp(2),
worstCaseUp(3) worstCaseUp(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Contains indicates whether a target SNR margin is enabled or "Indicates whether a target SNR margin is enabled or
disabled. This is a bit-map of possible settings. The disabled. This is a bit-map of possible settings. The
various bit positions are: various bit positions are:
currCondDown - current condition downstream target SNR currCondDown - current condition downstream target SNR
margin enabled margin enabled
worstCaseDown - worst case downstream target SNR margin worstCaseDown - worst case downstream target SNR margin
enabled enabled
currCondUp - current condition upstream target SNR currCondUp - current condition upstream target SNR
skipping to change at page 50, line 47 skipping to change at page 51, line 23
thresholds for various performance attributes monitored at thresholds for various performance attributes monitored at
HDSL2/SHDSL segment endpoints. Profiles may be created/deleted HDSL2/SHDSL segment endpoints. Profiles may be created/deleted
using the row creation/deletion mechanism via using the row creation/deletion mechanism via
hdsl2ShdslEndpointAlarmConfProfileRowStatus. If an active hdsl2ShdslEndpointAlarmConfProfileRowStatus. If an active
entry is referenced in either hdsl2ShdslSpanConfAlarmProfile entry is referenced in either hdsl2ShdslSpanConfAlarmProfile
or hdsl2ShdslEndpointAlarmConfProfile, the entry MUST remain or hdsl2ShdslEndpointAlarmConfProfile, the entry MUST remain
active until all references are removed." active until all references are removed."
INDEX { IMPLIED hdsl2ShdslEndpointAlarmConfProfileName } INDEX { IMPLIED hdsl2ShdslEndpointAlarmConfProfileName }
::= { hdsl2ShdslEndpointAlarmConfProfileTable 1 } ::= { hdsl2ShdslEndpointAlarmConfProfileTable 1 }
Hdsl2ShdslEndpointAlarmConfProfileEntry ::= Hdsl2ShdslEndpointAlarmConfProfileEntry ::
SEQUENCE SEQUENCE
{ {
hdsl2ShdslEndpointAlarmConfProfileName SnmpAdminString, hdsl2ShdslEndpointAlarmConfProfileName SnmpAdminString,
hdsl2ShdslEndpointThreshLoopAttenuation Integer32, hdsl2ShdslEndpointThreshLoopAttenuation Integer32,
hdsl2ShdslEndpointThreshSNRMargin Integer32, hdsl2ShdslEndpointThreshSNRMargin Integer32,
hdsl2ShdslEndpointThreshES hdsl2ShdslEndpointThreshES
Hdsl2ShdslPerfIntervalThreshold, Hdsl2ShdslPerfIntervalThreshold,
hdsl2ShdslEndpointThreshSES hdsl2ShdslEndpointThreshSES
Hdsl2ShdslPerfIntervalThreshold, Hdsl2ShdslPerfIntervalThreshold,
hdsl2ShdslEndpointThreshCRCanomalies Integer32, hdsl2ShdslEndpointThreshCRCanomalies Integer32,
skipping to change at page 58, line 19 skipping to change at page 58, line 42
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates impending unit failure due to "This notification indicates impending unit failure due to
loss of local power (last gasp)." loss of local power (last gasp)."
::= { hdsl2ShdslNotifications 16 } ::= { hdsl2ShdslNotifications 16 }
-- conformance information -- conformance information
-- --
hdsl2ShdslConformance OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 3 } hdsl2ShdslConformance OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 3 }
hdsl2ShdslGroups OBJECT IDENTIFIER ::= hdsl2ShdslGroups OBJECT IDENTIFIER ::
{ hdsl2ShdslConformance 1 } { hdsl2ShdslConformance 1 }
hdsl2ShdslCompliances OBJECT IDENTIFIER ::= hdsl2ShdslCompliances OBJECT IDENTIFIER ::
{ hdsl2ShdslConformance 2 } { hdsl2ShdslConformance 2 }
-- agent compliance statements -- agent compliance statements
hdsl2ShdslLineMibCompliance MODULE-COMPLIANCE hdsl2ShdslLineMibCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The section outlines compliance requirements for this MIB." "The section outlines compliance requirements for this MIB."
MODULE MODULE
MANDATORY-GROUPS MANDATORY-GROUPS
skipping to change at page 66, line 12 skipping to change at page 66, line 34
with a G.shdsl.bis unit and with a G.shdsl.bis unit and
hdsl2ShdslEndpointCurrSnrMgn.1.1.1.1 = 0 hdsl2ShdslEndpointCurrSnrMgn.1.1.1.1 = 0
with an HDSL2 unit as these objects are indexed by with an HDSL2 unit as these objects are indexed by
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslendpointSide, INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslendpointSide,
hdsl2ShdslEndpointWirePair } hdsl2ShdslEndpointWirePair }
A management application intended to manage G.shdsl.bis agents, A management application intended to manage G.shdsl.bis agents SHOULD
should be modified to accept this sequence. be modified to accept this sequence.
One should note that this same unmodified management application is One should note that this same unmodified management application is
still capable of managing G.shdsl.bis agents albeit to the degree of still capable of managing G.shdsl.bis agents albeit to the degree of
G.SHDSL (non-bis) limitations. That is, it can create and monitor G.SHDSL (non-bis) limitations. That is, it can create and monitor
configurations limited to two wire pairs with an upper rate limit of configurations limited to two wire pairs with an upper rate limit of
4112000 bits/second. 4112000 bits/second.
8. Security Considerations 8. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations. These are the tables and objects and their
sensitivity/vulnerability:
Some of the readable objects in this MIB module ( i.e., objects with o hdsl2ShdslSpanConfTable
a MAX-ACCESS other than not-accessible) may be considered sensitive
or vulnerable in some network environments. It is thus important to The table consists of the following objects that support SET
operations:
* hdsl2ShdslSpanConfNumRepeaters
* hdsl2ShdslSpanConfProfile
* hdsl2ShdslSpanConfAlarmProfile
Unauthorized changes to hdsl2ShdslSpanConfNumRepeaters could
result in a hdsl2ShdslSpanInvalidNumRepeaters notification. Note
the discussion on hdsl2ShdslSpanInvalidNumRepeaters in the
Notifications Section above.
Unapproved changes to hdsl2ShdslSpanConfProfile could have an
adverse operational effect on a span. Reference the
hdsl2ShdslSpanConfProfileTable discussion below.
Unofficial changes to hdsl2ShdslSpanConfAlarmProfile could have a
contrary effect on notifications. Reference the
hdsl2ShdslEndpointAlarmConfProfileTable discussion below.
o hdsl2ShdslEndpointConfTable
This table contains one object,
hdsl2ShdslEndpointAlarmConfProfile, that supports SET operations.
Unauthorized changes could have an undesirable notifications.
Reference the hdsl2ShdslEndpointAlarmConfProfileTable discussion
below.
o hdsl2ShdslEndpointMaintTable
The table consists of the following objects that support SET
operations:
* hdsl2ShdslMaintLoopbackConfig
* hdsl2ShdslMaintPowerBackoff
* hdsl2ShdslMaintSoftRestart
Unauthorized changes to hdsl2ShdslMaintLoopbackConfig could
prevent end-to-end data transfer due to an activation of a
loopback.
Illegitimate changes to hdsl2ShdslMaintPowerBackoff could result
in an increased in bundle interference.
Unapproved changes to hdsl2ShdslMaintSoftRestart could result in a
temporary interruption of end-to-end data transfer as the result
of the triggering of a soft restart.
o hdsl2ShdslUnitMaintTable
This table contains one object, hdsl2ShdslMaintLoopbackTimeout,
that supports SET operations. An unauthorized change to this
object could result in the timeout value for loopbacks being
increased, decreased, or disabled.
o hdsl2ShdslSpanConfProfileTable
The table consists of the following objects that support SET
operations:
* hdsl2ShdslSpanConfWireInterface
* hdsl2ShdslSpanConfMinLineRate
* hdsl2ShdslSpanConfMaxLineRate
* hdsl2ShdslSpanConfPSD
* hdsl2ShdslSpanConfTransmissionMode
* hdsl2ShdslSpanConfRemoteEnabled
* hdsl2ShdslSpanConfPowerFeeding
* hdsl2ShdslSpanConfCurrCondTargetMarginDown
* hdsl2ShdslSpanConfWorstCaseTargetMarginDown
* hdsl2ShdslSpanConfCurrCondTargetMarginUp
* hdsl2ShdslSpanConfWorstCaseTargetMarginUp
* hdsl2ShdslSpanConfUsedTargetMargins
* hdsl2ShdslSpanConfReferenceClock
* hdsl2ShdslSpanConfLineProbeEnable
* hdsl2ShdslSpanConfProfileRowStatus
Setting any of the objects to an incorrect value could have an
adverse operational effect on a span.
Unauthorized changes to the hdsl2ShdslSpanConfWireInterface could
result in the failure of a span to achieve activation to a state
that would permit data flow. For example, setting this object to
six-wire or eight-wire operation when one of the units in the span
only supports two-wire or four-wire operation would likely prevent
an expected end-to-end data transfer capability.
Illegitimate changes to hdsl2ShdslSpanConfMinLineRate or
hdsl2ShdslSpanConfMaxLineRate could have an adverse effect on
performance. The range of allowable line rates could be altered
such that the span may not be able to train to an line rate that
would permit any end-user data to traverse the span or the span
could train to a line rate that is either greater than or less
than the line rate that the provider has pledged.
Unapproved changes to hdsl2ShdslSpanConfPSD or
hdsl2ShdslSpanConfTransmissionMode could have a detrimental effect
loop reach, performance, or spectral compatibility.
Unofficial changes to hdsl2ShdslSpanConfRemoteEnable could alter
the remote management ability of units.
Unsanctioned changes to hdsl2ShdslSpanConfPowerFeeding could
shutdown units that are expected to be feed power remotely.
Changing the configuration such that wetting current is not
supplied may result in corrosion of electrical contacts.
Unwarranted changes to hdsl2ShdslSpanConfCurrCondTargetMarginDown,
hdsl2ShdslSpanConfWorstCaseTargetMarginDown,
hdsl2ShdslSpanConfCurrCondTargetMarginUp,
hdsl2ShdslSpanConfWorstCaseTargetMarginUp, or
hdsl2ShdslSpanConfUsedTargetMargins could result in invalid
parameters used to determine if a data rate can be supported under
current and worst-case noise.
Illegal changes to hdsl2ShdslSpanConfReferenceClock could result
in the selection of a clock source which might either prevent any
data from being transferred or impair data transfer. In addition,
an increase in CRC anomalies may be experienced.
Undesired changes to hdsl2ShdslSpanConfLineProbeEnable could have
a negative effect on selecting the optimum rate or power level
based on current line conditions.
Unauthorized changes to row status could result in unwanted
profiles being created or brought into service. Also, changes to
the row status could result in profiles being inadvertently
deleted or taken out of service.
o hdsl2ShdslEndpointAlarmConfProfileTable
The table consists of the following objects that support SET
operations:
* hdsl2ShdslEndpointThreshLoopAttenuation
* hdsl2ShdslEndpointThreshSNRMargin
* hdsl2ShdslEndpointThreshES
* hdsl2ShdslEndpointThreshSES
* hdsl2ShdslEndpointThreshCRCanomalies
* hdsl2ShdslEndpointThreshLOSWS
* hdsl2ShdslEndpointThreshUAS
* hdsl2ShdslEndpointAlarmConfProfileRowStatus
Increasing any of the threshold values could result a notification
being suppressed or deferred. Setting a threshold to 0 could
result in a notification being suppressed. Suppressing or
deferring a notification could prevent the timely delivery of
important diagnostic information. Decreasing any of the threshold
values could result in a notification being sent from the network
falsely reporting a threshold crossing.
Changing a threshold value could also have an impact on the amount
of notifications the agent sends. This document adds a paragraph,
which was not in RFC 3276 [RFC3276], to the Notifications Section
which provides general guidance to the rate limiting of
notifications. Agent implementations not adhering to the
rate-limiting desires could result in notifications being
generated at an uncontrolled rate. Illegitimate changes to a
threshold value could result in an undesired notification rate.
Unauthorized changes to row status could result in unwanted
profiles being created or brought into service. Also, changes to
the row status could result in profiles being inadvertently
deleted or taken out of service.
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
o hdsl2ShdslInventoryTable
Access to these objects would allow an intruder to obtain
information about which vendor's equipment is in use on the
network. Further, such information is considered sensitive in
many environments for competitive reasons.
* hdsl2ShdslInvVendorID
* hdsl2ShdslInvVendorModelNumber
* hdsl2ShdslInvVendorSerialNumber
* hdsl2ShdslInvVendorEOCSoftwareVersion
* hdsl2ShdslInvStandardVersion
* hdsl2ShdslInvVendorListNumber
* hdsl2ShdslInvVendorIssueNumber
* hdsl2ShdslInvVendorSoftwareVersion
* hdsl2ShdslInvEquipmentCode
* hdsl2ShdslInvVendorOther
* hdsl2ShdslInvTransmissionModeCapability
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access the GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], Section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
Blocking unauthorized access to the HDSL2-SHDSL MIB via the element
management system is outside the scope of this document. It should
be noted that access to the MIB permits the unauthorized entity to
modify the profiles such that both subscriber service and network
operations can be interfered with. Subscriber service can 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 SES
thresholds.
There are a number of managed objects in this MIB that may be
considered to contain sensitive information. Access to these objects
would allow an intruder to obtain information about which vendor's
equipment is in use on the network. Further, such information is
considered sensitive in many environments for competitive reasons.
These identifying objects in the inventory group are:
- hdsl2ShdslInvVendorID
- hdsl2ShdslInvVendorModelNumber
- hdsl2ShdslInvVendorSerialNumber
- hdsl2ShdslInvVendorEOCSoftwareVersion
- hdsl2ShdslInvStandardVersion
- hdsl2ShdslInvVendorListNumber
- hdsl2ShdslInvVendorIssueNumber
- hdsl2ShdslInvVendorSoftwareVersion
- hdsl2ShdslInvEquipmentCode
- hdsl2ShdslInvVendorOther
- hdsl2ShdslInvTransmissionModeCapability
Therefore, it may be 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.
It is recommended that the implementors consider the security
features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 3414 [RFC3414] and the
View-based Access Control Model RFC 3415 [RFC3415] are recommended.
It is then the customer/user's responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly
configured to give access to those objects only to those principals
(users) that have legitimate rights to access them.
HDSL2-SHDSL layer connectivity from the xtuR will permit the
subscriber to manipulate both the HDSL2-SHDSL link directly and the
HDSL2-SHDSL embedded operations channel (EOC) for their own loop.
For example, unchecked or unfiltered fluctuations initiated by the
subscriber could generate sufficient notifications to potentially
overwhelm either the management interface to the network or the
element manager.
It should be noted that interface indices in this MIB are maintained
persistently. View-based Access Control Model (VACM) data relating
to these should be stored persistently.
There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.
It is conceivable that a management application that was designed to
support G.SHDSL as defined in RFC 3276 [RFC3276] could be broken by a
G.shdsl.bis agent which reports objects for additional wire pairs (as
noted in Section 7).
For example, if a management application blindly loaded object
instances into an array until the object changes (during repeated
GET-NEXT requests). It is anticipated that the modifications to the
management application code would be straightforward.
9. Acknowledgments 9. Acknowledgments
The authors are deeply grateful to the authors of the ADSL LINE MIB The authors are deeply grateful to the authors of the ADSL LINE MIB
(RFC 2662 [RFC2662]), Gregory Bathrick and Faye Ly, as much of the (RFC 2662 [RFC2662]), Gregory Bathrick and Faye Ly, as much of the
text and structure of this document originates in their documents. text and structure of this document originates in their documents.
The authors are also grateful to the authors of FR MFR MIB (RFC 3020 The authors are also grateful to the authors of FR MFR MIB (RFC 3020
[RFC3020]), Prayson Pate, Bob Lynch, and Kenneth Rehbehn, as the [RFC3020]), Prayson Pate, Bob Lynch, and Kenneth Rehbehn, as the
majority of the Security Considerations section was lifted from their majority of the Security Considerations section was lifted from their
document. document.
The authors also acknowledge the importance of the contributions and The authors also acknowledge the importance of the contributions and
suggestions regarding interface indexing structures received from suggestions regarding interface indexing structures received from
David Horton of CITR. David Horton of CITR.
The authors are extremely thankful to Bert Wijnen, Randy Presuhn, and
C. M. Heard for their extensive review and the many suggestions
they provided.
Other contributions were received from the following: Other contributions were received from the following:
Matt Beanland (Extel Communications) Matt Beanland (Extel Communications)
Philip Bergstresser (Adtran) Philip Bergstresser (Adtran)
Steve Blackwell (Centillium) Steve Blackwell (Centillium)
Umberto Bonollo (NEC Australia) Umberto Bonollo (NEC Australia)
John Egan (Metalink BroadBand) John Egan (Metalink BroadBand)
Yagal Hachmon (RAD) Yagal Hachmon (RAD)
Mark Johnson (Red Point) Mark Johnson (Red Point)
Sharon Mantin (Orckit) Sharon Mantin (Orckit)
skipping to change at page 69, line 32 skipping to change at page 72, line 32
Bert Wijnen (Lucent) Bert Wijnen (Lucent)
Michael Wrobel (Memotec) Michael Wrobel (Memotec)
10. References 10. References
10.1 Normative References 10.1 Normative References
[G.991.2] Blackwell, S., "Single-Pair High-Speed Digital Subscriber [G.991.2] Blackwell, S., "Single-Pair High-Speed Digital Subscriber
Line (SHDSL) Transceivers", ITU-T G.991.2, December 2003. Line (SHDSL) Transceivers", ITU-T G.991.2, December 2003.
[RFC2119] Brandner, S., "Key Words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
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. and J. Schoenwaelder,
Rose, M. and S. Waldbusser, "Conformance Statements for "Conformance Statements for SMIv2", STD 58, RFC 2580,
SMIv2", STD 58, RFC 2580, April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects for
High Bit-Rate DSL - 2nd generation (HDSL2) and
Single-Pair High-Speed Digital Subscriber Line (SHDSL)
Lines", RFC 3276, May 2003.
[RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002. December 2002.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", STD 62, RFC 3415, December
2002.
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC Performance History Based on 15 Minute Intervals",
3593, September 2003. RFC 3593, September 2003.
[T1E1.4] American National Standards Institute, "ANSI T1E1.4/ [T1E1.4] American National Standards Institute, "ANSI
2000-006", February 2000. T1E1.4/2000-006", February 2000.
10.2 Informative References 10.2 Informative References
[RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects
for the ADSL Lines", RFC 2662, August 1999. for the ADSL Lines", RFC 2662, August 1999.
[RFC3020] Pate, P., Lynch, B. and K. Rehbehn, "Definitions of [RFC3020] Pate, P., Lynch, B. and K. Rehbehn, "Definitions of
Managed Objects for Monitoring and Controlling the UNI/ Managed Objects for Monitoring and Controlling the UNI/NNI
NNI Multilink Frame Relay Function", RFC 3020, December Multilink Frame Relay Function", RFC 3020, December 2000.
2000.
[RFC3410] Case, J., Mindy, R., Partain, D. and B. Stewart, [RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects for
"Introduction and Applicability Statements for Internet High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair
Standard Management Framework", RFC 3410, December 2002. High-Speed Digital Subscriber Line (SHDSL) Lines
Processing", RFC 3276, May 2002.
[RFC3418] Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
Waldbusser, "Management Information Base (MIB) for the "Introduction and Applicability Statements for
Simple Network Management Protocol (SNNP)", STD 62, RFC Internet-Standard Management Framework", RFC 3410,
3418, December 2002. December 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002.
Authors' Addresses Authors' Addresses
Clay Sikes Clay Sikes
Paradyne Corporation Paradyne Corporation
8454 126th Ave. N. 8454 126th Ave. N.
Largo, FL 33773 Largo, FL 33773
US US
Phone: +1 727 530 8257 Phone: +1 727 530 8257
Fax: +1 727 532 5698 Fax: +1 727 532 5698
EMail: csikes@paradyne.com Email: csikes@paradyne.com
Bob Ray Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
330-A Wynn Drive 330-A Wynn Drive
Huntsville, AL 35805 Huntsville, AL 35805
US US
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Fax: +1 256 726 9271 Fax: +1 256 726 9271
EMail: rray@pesa.com Email: rray@pesa.com
Rajesh Abbi Rajesh Abbi
Alcatel USA Alcatel USA
2912 Wake Forest Road 2912 Wake Forest Road
Raleigh, NC 27609-7860 Raleigh, NC 27609-7860
US US
Phone: +1 919-850-6194 Phone: +1 919-850-6194
Fax: +1 919-850-6670 Fax: +1 919-850-6670
EMail: Rajesh.Abbi@alcatel.com Email: Rajesh.Abbi@alcatel.com
Intellectual Property Statement Intellectual Property Statement
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 Rights or other rights that might be claimed to Intellectual Property Rights 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; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
skipping to change at page 72, line 46 skipping to change at page 75, line 46
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
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.
 End of changes. 

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