draft-ietf-adslmib-gshdslbis-01.txt   draft-ietf-adslmib-gshdslbis-02.txt 
Network Working Group C. Sikes Network Working Group C. Sikes
Internet-Draft Paradyne Corporation Internet-Draft Paradyne Corporation
Expires: December 6, 2004 B. Ray Expires: December 16, 2004 B. Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
R. Abbi R. Abbi
Alcatel USA Alcatel USA
June 7, 2004 June 17, 2004
Definitions of Managed Objects for G.SHDSL.BIS Lines Definitions of Managed Objects for G.SHDSL.BIS Lines
draft-ietf-adslmib-gshdslbis-01.txt draft-ietf-adslmib-gshdslbis-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with and any of which I 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
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 December 6, 2004. This Internet-Draft will expire on December 16, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) module for use with network management protocols in the (MIB) module for use with network management protocols in the
Internet community. In particular, it describes objects used for Internet community. In particular, it describes objects used for
managing High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair managing High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair
High-Speed Digital Subscriber Line (SHDSL) interfaces. This document High-Speed Digital Subscriber Line (SHDSL) interfaces. This document
introduces extensions to several objects and textual conventions introduces extensions to several objects and textual conventions
defined in HDSL2-SHDSL-Line MIB (RFC 3276). This MIB described in defined in HDSL2-SHDSL-Line MIB (RFC 3276). The MIB described in
this document will obsolete the MIB described in RFC 3276. this document will obsolete the MIB described in RFC 3276.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The SNMP Management Framework . . . . . . . . . . . . . . . . 3 2. The SNMP Management Framework . . . . . . . . . . . . . . . . 3
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1 Relationship of the HDSL2/SHDSL Line MIB to other MIBs . . 4 3.1 Relationship of the HDSL2/SHDSL Line MIB to other MIBs . . 4
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 . . . . . . . . . . . . . . . . . . . 5 3.1.2 Usage of ifTable . . . . . . . . . . . . . . . . . . . 5
3.2 IANA Considerations . . . . . . . . . . . . . . . . . . . 6 3.2 IANA Considerations . . . . . . . . . . . . . . . . . . . 6
4. Conventions used in the MIB . . . . . . . . . . . . . . . . . 6 4. Conventions used in the MIB . . . . . . . . . . . . . . . . . 6
4.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . 6 4.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . 6
4.2 Textual Conventions . . . . . . . . . . . . . . . . . . . 7 4.2 Textual Conventions . . . . . . . . . . . . . . . . . . . 7
4.3 Structure . . . . . . . . . . . . . . . . . . . . . . . . 8 4.3 Structure . . . . . . . . . . . . . . . . . . . . . . . . 8
4.3.1 Line Topology . . . . . . . . . . . . . . . . . . . . 11 4.3.1 Line Topology . . . . . . . . . . . . . . . . . . . . 10
4.4 Counters, Interval Buckets and Thresholds . . . . . . . . 11 4.4 Counters, Interval Buckets and Thresholds . . . . . . . . 11
4.5 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.5 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.6 Notifications . . . . . . . . . . . . . . . . . . . . . . 13 4.6 Notifications . . . . . . . . . . . . . . . . . . . . . . 13
5. Conformance and Compliance . . . . . . . . . . . . . . . . . . 15 5. Conformance and Compliance . . . . . . . . . . . . . . . . . . 14
6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 15 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 15
7. Implementation Analysis . . . . . . . . . . . . . . . . . . . 64 7. Implementation Analysis . . . . . . . . . . . . . . . . . . . 65
8. Security Considerations . . . . . . . . . . . . . . . . . . . 65 8. Security Considerations . . . . . . . . . . . . . . . . . . . 66
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 67 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 68
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 67 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 69
10.1 Normative References . . . . . . . . . . . . . . . . . . . . 67 10.1 Normative References . . . . . . . . . . . . . . . . . . . . 69
10.2 Informative References . . . . . . . . . . . . . . . . . . . 69 10.2 Informative References . . . . . . . . . . . . . . . . . . . 71
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 71
Intellectual Property and Copyright Statements . . . . . . . . 71 Intellectual Property and Copyright Statements . . . . . . . . 73
1. Introduction 1. Introduction
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) module for use with network management protocols in the (MIB) module for use with network management protocols in the
Internet community. The MIB described in RFC 3276 [RFC3276] Internet community. The MIB described in RFC 3276 [RFC3276]
describes objects used for managing High Bit-Rate DSL - 2nd describes objects used for managing High Bit-Rate DSL - 2nd
generation (HDSL2) [T1E1.4] and Single-Pair High-Speed Digital generation (HDSL2) [T1E1.4] and Single-Pair High-Speed Digital
Subscriber Line (SHDSL) interfaces [G.991.2]. This document Subscriber Line (SHDSL) interfaces [G.991.2]. This document
obsoletes RFC 3276 [RFC3276] which supports G.SHDSL in that the MIB obsoletes RFC 3276 [RFC3276] which supports G.SHDSL in that the MIB
skipping to change at page 8, line 32 skipping to change at page 8, line 26
o Hdsl2ShdslPerfCurrDayCount: o Hdsl2ShdslPerfCurrDayCount:
Attributes with this syntax define the behavior of the 1-day (24 Attributes with this syntax define the behavior of the 1-day (24
hour) gauges found in the MIB. hour) gauges found in the MIB.
o Hdsl2Shdsl1DayIntervalCount: o Hdsl2Shdsl1DayIntervalCount:
Attributes with this syntax define the behavior of the 1-day (24 Attributes with this syntax define the behavior of the 1-day (24
hour) interval counters found in the MIB. hour) interval counters found in the MIB.
o Hdsl2ShdslPerfTimeElapsed: Attributes with this syntax define the o Hdsl2ShdslPerfTimeElapsed:
behavior of the elapsed time counters found in the MIB.
Attributes with this syntax define the behavior of the elapsed
time counters found in the MIB.
o Hdsl2ShdslPerfIntervalThreshold: o Hdsl2ShdslPerfIntervalThreshold:
Attributes with this syntax define the behavior of the alarm Attributes with this syntax define the behavior of the alarm
thresholds found in the MIB. thresholds found in the MIB.
o Hdsl2ShdslClockReferenceType o Hdsl2ShdslClockReferenceType:
Attributes with this syntax define the clock references for the Attributes with this syntax define the clock references for the
HDSL2/SHDSL span. HDSL2/SHDSL span.
4.3 Structure 4.3 Structure
The MIB is structured into following MIB groups: The MIB is structured into following MIB groups:
o Span Configuration Group: This group supports MIB objects for o Span Configuration Group:
configuring parameters for the HDSL2/SHDSL span. It contains the
following table:
- hdsl2ShdslSpanConfTable This group supports MIB objects for configuring parameters for the
HDSL2/SHDSL span. It contains the following table:
- hdsl2ShdslSpanConfTable
o Span Status Group: o Span Status Group:
This group supports MIB objects for retrieving span status This group supports MIB objects for retrieving span status
information. It contains the following table: information. It contains the following table:
- hdsl2ShdslSpanStatusTable - hdsl2ShdslSpanStatusTable
o Unit Inventory Group: o Unit Inventory Group:
This group supports MIB objects for retrieving unit inventory This group supports MIB objects for retrieving unit inventory
skipping to change at page 15, line 48 skipping to change at page 15, line 44
TEXTUAL-CONVENTION FROM SNMPv2-TC TEXTUAL-CONVENTION FROM SNMPv2-TC
ifIndex FROM IF-MIB ifIndex FROM IF-MIB
PerfCurrentCount, PerfCurrentCount,
PerfIntervalCount FROM PerfHist-TC-MIB PerfIntervalCount FROM PerfHist-TC-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-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 "200406070000Z" -- June 7, 2004 LAST-UPDATED "200406170000Z" -- June 17, 2004
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
Postal: P.O. Box 37324 Postal: P.O. Box 37324
Raleigh NC 27627-7324 Raleigh NC 27627-7324
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
Co-editor: Clay Sikes Co-editor: Clay Sikes
Paradyne Corporation Paradyne Corporation
skipping to change at page 16, line 40 skipping to change at page 16, line 36
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)."
REVISION "200406170000Z" -- June 17, 2004
DESCRIPTION
"Had an error in the syntax checker environment such
that any error in the MIB would not be caught. As a result,
the previous version of this MIB would not compile. The
changes to correct the MIB so it would compile are as follows:
1. Changed hdsl2shdslEndpointCurrTipRingReversal in
Hdsl2ShdslEndpointCurrEntry from Integer to INTEGER.
2. Changed hdsl2shdslEndpointCurrActivationState in
Hdsl2ShdslEndpointCurrEntry from Integer to INTEGER.
3. The REFERENCE statement for
hdsl2ShdslEndpointCurr15MinCRCanomalies was missing
a closing quote.
4. hdsl2shdslEndpointCurrTipRingReversal had a bad OID.
5. hdsl2shdslEndpointCurrActivationState had a bad OID."
REVISION "200406070000Z" -- June 7, 2004 REVISION "200406070000Z" -- June 7, 2004
DESCRIPTION "Initial version, published as draft G.SHDSL.BIS." DESCRIPTION
"Initial version, -01, published as draft G.SHDSL.BIS.
The changes from RFC 3276 are as follows:
1. Hdsl2ShdslWirePair
Added wirePair3 and wirePair4.
2. hdsl2ShdslStatusMaxAttainableLineRate
Removed the rate limitations. It's now just Unsigned32.
Also, clarified in the description that this rate
includes both payload and any applicable framing.
3. hdsl2ShdslStatusActualLineRate
Removed the rate limitations. It's now just
Unsigned32. Also, clarified in the description that
this rate includes both payload and any applicable
framing.
4. hdsl2ShdslStatusMaxAttainablePayloadRate
Added this object.
5. hdsl2ShdslStatusActualPayloadRate
Added this object.
6. hdsl2ShdslEndpointCurrTipRingReversal
Added this object for status on a per-wire pair.
7. hdsl2shdslEndpointCurrActivationState
Added this object for status on a per-wire pair.
8. hdsl2ShdslSpanConfMinLineRate
Removed the rate limitations. It's now just Unsigned32.
Also, clarified in the description that this rate
includes both payload and any applicable framing.
9. hdsl2ShdslSpanConfMaxLineRate
Removed the rate limitations. It's now just
Unsigned32. Also, clarified in the description
that this rate includes both payload and any applicable
framing.
10. Updated conformance statements.
11. Added DISPLAY-HINT to TEXTUAL-CONVENTIONS where needed
to get rid of some MIB compiler complaints such as
smilint version 0.4.2.
12. White space clean up.
13. Added six-wire and eight-wire references to the
description for hdsl2ShdslSpanConfWireInterface."
::= { transmission 48 } ::= { transmission 48 }
hdsl2ShdslMibObjects OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 1 } hdsl2ShdslMibObjects OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 1 }
-- Textual Conventions used in this MIB -- Textual Conventions used in this MIB
-- --
Hdsl2ShdslPerfCurrDayCount ::= TEXTUAL-CONVENTION Hdsl2ShdslPerfCurrDayCount ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A gauge associated with interface performance measurements in "A gauge associated with interface performance measurements in
a current 1-day (24 hour) measurement interval. a current 1-day (24 hour) measurement interval.
The value of this gauge starts at zero at the beginning of an The value of this gauge starts at zero at the beginning of an
interval and is increased when associated events occur, until interval and is increased when associated events occur, until
the end of the 1-day interval. At that time the value of the the end of the 1-day interval. At that time the value of the
gauge is stored in the previous 1-day history interval, as gauge is stored in the previous 1-day history interval, as
defined in a companion object of type defined in a companion object of type
skipping to change at page 17, line 24 skipping to change at page 18, line 26
is restarted at zero. is restarted at zero.
In the case where the agent has no valid data available for In the case where the agent has no valid data available for
this interval the corresponding object instance is not this interval the corresponding object instance is not
available and upon a retrieval request a corresponding error available and upon a retrieval request a corresponding error
message shall be returned to indicate that this instance does message shall be returned to indicate that this instance does
not exist. Please note that zero is a valid value." not exist. Please note that zero is a valid value."
SYNTAX Gauge32 SYNTAX Gauge32
Hdsl2Shdsl1DayIntervalCount ::= TEXTUAL-CONVENTION Hdsl2Shdsl1DayIntervalCount ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter associated with interface performance measurements "A counter associated with interface performance measurements
during the most previous 1-day (24 hour) measurement interval. during the most previous 1-day (24 hour) measurement interval.
The value of this gauge is equal to the value of the current The value of this gauge is equal to the value of the current
day gauge, as defined in a companion object of type day gauge, as defined in a companion object of type
Hdsl2ShdslPerfCurrDayCount, at the end of its most recent Hdsl2ShdslPerfCurrDayCount, at the end of its most recent
interval. interval.
In the case where the agent has no valid data available for In the case where the agent has no valid data available for
this interval the corresponding object instance is not this interval the corresponding object instance is not
available and upon a retrieval request a corresponding error available and upon a retrieval request a corresponding error
message shall be returned to indicate that this instance does message shall be returned to indicate that this instance does
not exist." not exist."
SYNTAX Gauge32 SYNTAX Gauge32
Hdsl2ShdslPerfTimeElapsed ::= TEXTUAL-CONVENTION Hdsl2ShdslPerfTimeElapsed ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of seconds that have elapsed since the beginning of "The number of seconds that have elapsed since the beginning of
the current measurement period. If, for some reason, such as the current measurement period. If, for some reason, such as
an adjustment in the system's time-of-day clock or the addition an adjustment in the system's time-of-day clock or the addition
of a leap second, the current interval exceeds the maximum of a leap second, the current interval exceeds the maximum
value, the agent will return the maximum value. value, the agent will return the maximum value.
For 15 minute intervals, the range is limited to (0..899). For 15 minute intervals, the range is limited to (0..899).
For 24 hour intervals, the range is limited to (0..86399)." For 24 hour intervals, the range is limited to (0..86399)."
skipping to change at page 18, line 4 skipping to change at page 19, line 8
DESCRIPTION DESCRIPTION
"The number of seconds that have elapsed since the beginning of "The number of seconds that have elapsed since the beginning of
the current measurement period. If, for some reason, such as the current measurement period. If, for some reason, such as
an adjustment in the system's time-of-day clock or the addition an adjustment in the system's time-of-day clock or the addition
of a leap second, the current interval exceeds the maximum of a leap second, the current interval exceeds the maximum
value, the agent will return the maximum value. value, the agent will return the maximum value.
For 15 minute intervals, the range is limited to (0..899). For 15 minute intervals, the range is limited to (0..899).
For 24 hour intervals, the range is limited to (0..86399)." For 24 hour intervals, the range is limited to (0..86399)."
SYNTAX Unsigned32(0..86399) SYNTAX Unsigned32(0..86399)
Hdsl2ShdslPerfIntervalThreshold ::= TEXTUAL-CONVENTION Hdsl2ShdslPerfIntervalThreshold ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention defines a range of values that may be set in "This convention defines a range of values that may be set in
a fault threshold alarm control. As the number of seconds in a fault threshold alarm control. As the number of seconds in
a 15-minute interval numbers at most 900, objects of this type a 15-minute interval numbers at most 900, objects of this type
may have a range of 0...900, where the value of 0 disables the may have a range of 0...900, where the value of 0 disables the
alarm." alarm."
SYNTAX Unsigned32(0..900) SYNTAX Unsigned32(0..900)
Hdsl2ShdslUnitId ::= TEXTUAL-CONVENTION Hdsl2ShdslUnitId ::= TEXTUAL-CONVENTION
skipping to change at page 18, line 51 skipping to change at page 20, line 8
{ {
networkSide(1), networkSide(1),
customerSide(2) customerSide(2)
} }
Hdsl2ShdslWirePair ::= TEXTUAL-CONVENTION Hdsl2ShdslWirePair ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the referenced pair of wires in a HDSL2/SHDSL Segment. "This is the referenced pair of wires in a HDSL2/SHDSL Segment.
HDSL2 only supports a single pair (wirePair1 or two wire), HDSL2 only supports a single pair (wirePair1 or two wire),
SHDS lines support an optional second pair (wirePair2 or four SHDSL lines support an optional second pair (wirePair2 or four
wire), and G.SHDSL.bis support an optional third pair wire), and G.SHDSL.bis support an optional third pair
(wirePair3 or six wire) and an optional fourth pair (wirePair3 or six wire) and an optional fourth pair
(wirePair4 or eight wire)." (wirePair4 or eight wire)."
SYNTAX INTEGER SYNTAX INTEGER
{ {
wirePair1(1), -- two wire wirePair1(1), -- two wire
wirePair2(2), -- four wire wirePair2(2), -- four wire
wirePair3(3), -- six wire wirePair3(3), -- six wire
wirePair4(4) -- eight wire wirePair4(4) -- eight wire
} }
skipping to change at page 29, line 47 skipping to change at page 31, line 5
hdsl2ShdslEndpointCurr1DayES hdsl2ShdslEndpointCurr1DayES
Hdsl2ShdslPerfCurrDayCount, Hdsl2ShdslPerfCurrDayCount,
hdsl2ShdslEndpointCurr1DaySES hdsl2ShdslEndpointCurr1DaySES
Hdsl2ShdslPerfCurrDayCount, Hdsl2ShdslPerfCurrDayCount,
hdsl2ShdslEndpointCurr1DayCRCanomalies hdsl2ShdslEndpointCurr1DayCRCanomalies
Hdsl2ShdslPerfCurrDayCount, Hdsl2ShdslPerfCurrDayCount,
hdsl2ShdslEndpointCurr1DayLOSWS hdsl2ShdslEndpointCurr1DayLOSWS
Hdsl2ShdslPerfCurrDayCount, Hdsl2ShdslPerfCurrDayCount,
hdsl2ShdslEndpointCurr1DayUAS hdsl2ShdslEndpointCurr1DayUAS
Hdsl2ShdslPerfCurrDayCount, Hdsl2ShdslPerfCurrDayCount,
hdsl2ShdslEndpointCurrTipRingReversal Integer, hdsl2ShdslEndpointCurrTipRingReversal INTEGER,
hdsl2ShdslEndpointCurrActivationState Integer hdsl2ShdslEndpointCurrActivationState INTEGER
} }
hdsl2ShdslEndpointCurrAtn OBJECT-TYPE hdsl2ShdslEndpointCurrAtn OBJECT-TYPE
SYNTAX Integer32(-127..128) SYNTAX Integer32(-127..128)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current loop attenuation for this endpoint as reported in "The current loop attenuation for this endpoint as reported in
a Network or Customer Side Performance Status message." a Network or Customer Side Performance Status message."
skipping to change at page 33, line 38 skipping to change at page 34, line 44
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 11 } ::= { hdsl2ShdslEndpointCurrEntry 11 }
hdsl2ShdslEndpointCurr15MinCRCanomalies OBJECT-TYPE hdsl2ShdslEndpointCurr15MinCRCanomalies OBJECT-TYPE
SYNTAX PerfCurrentCount SYNTAX PerfCurrentCount
UNITS "detected CRC Anomalies" UNITS "detected CRC Anomalies"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of CRC anomalies in the current 15-minute interval." "Count of CRC anomalies in the current 15-minute interval."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 12 } ::= { hdsl2ShdslEndpointCurrEntry 12 }
hdsl2ShdslEndpointCurr15MinLOSWS OBJECT-TYPE hdsl2ShdslEndpointCurr15MinLOSWS OBJECT-TYPE
SYNTAX PerfCurrentCount SYNTAX PerfCurrentCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of Loss of Sync Word (LOSW) Seconds in the current "Count of Loss of Sync Word (LOSW) Seconds in the current
15-minute interval." 15-minute interval."
skipping to change at page 35, line 43 skipping to change at page 36, line 48
SYNTAX INTEGER SYNTAX INTEGER
{ {
normal(1), normal(1),
reversed(2) reversed(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the state of the tip/ring for the "This object indicates the state of the tip/ring for the
wire pair." wire pair."
::= { hdsl2ShdslEndpointCurrEntryEntry 21 } ::= { hdsl2ShdslEndpointCurrEntry 21 }
hdsl2ShdslEndpointCurrActivationState OBJECT-TYPE hdsl2ShdslEndpointCurrActivationState OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
{ {
preActivation(1), -- PreTrain preActivation(1), -- PreTrain
activation(2), -- Training activation(2), -- Training
data(3) -- Trained data(3) -- Trained
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the activation or training state of "This object indicates the activation or training state of
the wirepair." the wirepair."
REFERENCE "ITU-T G.991.2, Section 6.2 PMD Activation Sequence" REFERENCE "ITU-T G.991.2, Section 6.2 PMD Activation Sequence"
::= { hdsl2ShdslEndpointCurrEntryEntry 21 } ::= { hdsl2ShdslEndpointCurrEntry 22 }
-- Segment Endpoint 15-Minute Interval Status/Performance Group -- Segment Endpoint 15-Minute Interval Status/Performance Group
-- --
hdsl2Shdsl15MinIntervalTable OBJECT-TYPE hdsl2Shdsl15MinIntervalTable OBJECT-TYPE
SYNTAX SEQUENCE OF Hdsl2Shdsl15MinIntervalEntry SYNTAX SEQUENCE OF Hdsl2Shdsl15MinIntervalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides one row for each HDSL2/SHDSL endpoint "This table provides one row for each HDSL2/SHDSL endpoint
skipping to change at page 45, line 11 skipping to change at page 46, line 15
SYNTAX INTEGER SYNTAX INTEGER
{ {
twoWire(1), twoWire(1),
fourWire(2), fourWire(2),
sixWire(3), sixWire(3),
eightWire(4) eightWire(4)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the two-wire or optional four-wire "This object configures the two-wire or optional four-wire,
operation for SHDSL Lines." six-wire, or eight-wire operation for SHDSL Lines."
DEFVAL { twoWire } DEFVAL { twoWire }
::= { hdsl2ShdslSpanConfProfileEntry 2 } ::= { hdsl2ShdslSpanConfProfileEntry 2 }
hdsl2ShdslSpanConfMinLineRate OBJECT-TYPE hdsl2ShdslSpanConfMinLineRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bps" UNITS "bps"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the minimum transmission rate for "This object configures the minimum transmission rate for
skipping to change at page 67, line 23 skipping to change at page 68, line 31
[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.
Other contributions were received from the following: Other contributions were received from the following:
Mike 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)
Moti Morgenstern (ECI) Moti Morgenstern (ECI)
Raymond Murphy (Ericsson) Raymond Murphy (Ericsson)
Lee Nipper (Verilink) Lee Nipper (Verilink)
 End of changes. 

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