draft-ietf-adslmib-hdsl2-10.txt   draft-ietf-adslmib-hdsl2-11.txt 
Network Working Group B. Ray Network Working Group B. Ray
Request for Comments: xxxx Verilink Corporation Request for Comments: xxxx Verilink Corporation
Category: Standards Track R. Abbi Category: Standards Track R. Abbi
Alcatel Alcatel
July 2001 November 2001
Definitions of Managed Objects for HDSL2 and SHDSL Lines Definitions of Managed Objects for HDSL2 and SHDSL Lines
draft-ietf-adslmib-hdsl2-10.txt draft-ietf-adslmib-hdsl2-11.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all
provisions of Section 10 of RFC2026.
This document specifies an Internet standards track protocol for the This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited. and status of this protocol. Distribution of this memo is unlimited.
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
Table of Contents Table of Contents
1. Abstract .................................................. 2 1. Abstract .................................................. 2
2. The SNMP Network Management Framework ..................... 2 2. The SNMP Network Management Framework ..................... 2
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.2 IANA Considerations ....................................... 5
4. Conventions used in the MIB ............................... 5 4. Conventions used in the MIB ............................... 5
4.1 Naming Conventions ........................................ 5 4.1 Naming Conventions ........................................ 5
4.2 Textual Conventions ....................................... 5 4.2 Textual Conventions ....................................... 5
4.3 Structure ................................................. 6 4.3 Structure ................................................. 6
4.4 Counters, Interval Buckets and Thresholds ................. 9 4.4 Counters, Interval Buckets and Thresholds ................. 9
4.5 Profiles .................................................. 9 4.5 Profiles .................................................. 10
4.6 Notifications ............................................. 10 4.6 Notifications ............................................. 11
5. Conformance and Compliance ................................ 12 5. Conformance and Compliance ................................ 12
6. Definitions ............................................... 12 6. Definitions ............................................... 13
7. Security Considerations ................................... 53 7. Security Considerations ................................... 56
8. Acknowledgments ........................................... 54 8. Acknowledgments ........................................... 57
9. References ................................................ 55 9. References ................................................ 57
10. Intellectual Property Notice .............................. 56 10. Intellectual Property Notice .............................. 59
11. Authors' Addresses ........................................ 57 11. Authors' Addresses ........................................ 60
12. Full Copyright Statement .................................. 57 12. Full Copyright Statement .................................. 60
1. Abstract 1. 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) [18] and managing High Bit-Rate DSL - 2nd generation (HDSL2) [18] and
Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces
[19]. [19].
skipping to change at page 4, line 20 skipping to change at page 4, line 22
IANAifType ::= TEXTUAL-CONVENTION IANAifType ::= TEXTUAL-CONVENTION
... ...
SYNTAX INTEGER { SYNTAX INTEGER {
... ...
hdsl2 (168), -- High Bit-Rate DSL, 2nd generation hdsl2 (168), -- High Bit-Rate DSL, 2nd generation
shdsl (169), -- Multirate HDSL2 shdsl (169), -- Multirate HDSL2
... ...
} }
Note that the ifFixedLengthGroup from RFC 2863 [21] MUST be
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 ifGeneral group in
RFC 2863 [21], and are not duplicated in the HDSL2/SHDSL Line MIB. RFC 2863 [21], and are not duplicated in the HDSL2/SHDSL Line MIB.
skipping to change at page 5, line 8 skipping to change at page 5, line 15
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
The SNMPv2-TM MIB module requires the allocation of a single object
identifier for its MODULE-IDENTITY. IANA should allocate this object
identifier in the transmission subtree, defined in the SNMPv2-SMI MIB
module.
4. Conventions used in the MIB 4. Conventions used in the MIB
4.1. Naming Conventions 4.1. Naming Conventions
A. xtuC refers to a central site terminal unit; A. xtuC refers to a central site terminal unit;
H2TU-C for HDSL2, or STU-C for SHDSL. H2TU-C for HDSL2, or STU-C for SHDSL.
B. xtuR refers to a remote site terminal unit; B. xtuR refers to a remote site terminal unit;
H2TU-R for HDSL2, or STU-R for SHDSL. H2TU-R for HDSL2, or STU-R for SHDSL.
C. xtu refers to a terminal unit; either an xtuC or xtuR. C. xtu refers to a terminal unit; either an xtuC or xtuR.
D. xru refer to a regenerator unit; D. xru refer to a regenerator unit;
skipping to change at page 6, line 34 skipping to change at page 6, line 50
o Hdsl2ShdslPerfTimeElapsed: o Hdsl2ShdslPerfTimeElapsed:
Attributes with this syntax define the behavior of the elapsed Attributes with this syntax define the behavior of the elapsed
time counters found in the MIB. 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.
4.3. Structure o Hdsl2ShdslClockReferenceType
Attributes with this syntax define the clock references for
the HDSL2/SHDSL span.
4.3. Structure
The MIB is structured into following MIB groups: The MIB is structured into following MIB groups:
o Span Configuration Group: o Span Configuration Group:
This group supports MIB objects for configuring parameters for This group supports MIB objects for configuring parameters for
the HDSL2/SHDSL span. It contains the following table: the HDSL2/SHDSL span. It contains the following table:
- hdsl2ShdslSpanConfTable - hdsl2ShdslSpanConfTable
o Span Status Group: o Span Status Group:
skipping to change at page 12, line 55 skipping to change at page 13, line 31
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 "200107190000Z" -- July 19, 2001 LAST-UPDATED "200111150000Z" -- November 15, 2001
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: XDSLMIB@LISTSERV.ECIRALEIGH.COM CONTACT-INFO "WG-email: XDSLMIB@LISTSERV.ECIRALEIGH.COM
Subscribe: LISTSERV@LISTSERV.ECIRALEIGH.COM Subscribe: LISTSERV@LISTSERV.ECIRALEIGH.COM
In Body: subscribe/signoff XDSLMIB In Body: subscribe/signoff XDSLMIB
Archive: index XDSLMIB/get <archivename> Archive: index XDSLMIB/get <archivename>
Chair: Mike Sneed Chair: Mike Sneed
ECI Telecom ECI Telecom
Postal: 1017 Main Campus Drive Postal: 1017 Main Campus Drive
Raleigh NC 27606 USA Raleigh NC 27606 USA
skipping to change at page 13, line 38 skipping to change at page 14, line 15
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 "200107190000Z" -- July 19, 2001 REVISION "200111150000Z" -- November 15, 2001
DESCRIPTION "Initial version, published as RFC xxxx." DESCRIPTION "Initial version, published as RFC xxxx."
::= { transmission xxxx } -- to be assigned by IANA ::= { transmission xxxx } -- to be assigned by IANA
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
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
Hdsl2Shdsl1DayIntevalCount, and the current interval counter Hdsl2Shdsl1DayIntevalCount, and the current interval gauge
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
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 counter is equal to the value of the current The value of this gauge is equal to the value of the current
day counter, 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
skipping to change at page 16, line 10 skipping to change at page 16, line 42
Bit Meaning Description Bit Meaning Description
1 region 1 Indicates ITU-T G.991.2 Annex A. 1 region 1 Indicates ITU-T G.991.2 Annex A.
2 region 2 Indicates ITU-T G.991.2 Annex B." 2 region 2 Indicates ITU-T G.991.2 Annex B."
SYNTAX BITS SYNTAX BITS
{ {
region1(0), region1(0),
region2(1) region2(1)
} }
Hdsl2ShdslClockReferenceType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The various STU-C symbol clock references for the
HDSL2/SHDSL span, represented as an enumeration."
SYNTAX INTEGER
{
localClk(1), -- Mode-1 per G991.2
networkClk(2), -- Mode-2 per G991.2
dataOrNetworkClk(3), -- Mode-3a per G991.2
dataClk(4) -- Mode-3b per G991.2
}
-- Span Configuration Group -- Span Configuration Group
-- --
hdsl2ShdslSpanConfTable OBJECT-TYPE hdsl2ShdslSpanConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfEntry SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports overall configuration of HDSL2/SHDSL "This table supports overall configuration of HDSL2/SHDSL
Spans. Entries in this table MUST be maintained in a Spans. Entries in this table MUST be maintained in a
skipping to change at page 16, line 45 skipping to change at page 17, line 38
Hdsl2ShdslSpanConfEntry ::= Hdsl2ShdslSpanConfEntry ::=
SEQUENCE SEQUENCE
{ {
hdsl2ShdslSpanConfNumRepeaters INTEGER, hdsl2ShdslSpanConfNumRepeaters INTEGER,
hdsl2ShdslSpanConfProfile SnmpAdminString, hdsl2ShdslSpanConfProfile SnmpAdminString,
hdsl2ShdslSpanConfAlarmProfile SnmpAdminString hdsl2ShdslSpanConfAlarmProfile SnmpAdminString
} }
hdsl2ShdslSpanConfNumRepeaters OBJECT-TYPE hdsl2ShdslSpanConfNumRepeaters OBJECT-TYPE
SYNTAX INTEGER(0..8) SYNTAX INTEGER(0..8)
UNITS "repeaters"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object provisions the number of repeaters/regenerators "This object provisions the number of repeaters/regenerators
in this HDSL2/SHDSL Span." in this HDSL2/SHDSL Span."
::= { hdsl2ShdslSpanConfEntry 1 } ::= { hdsl2ShdslSpanConfEntry 1 }
hdsl2ShdslSpanConfProfile OBJECT-TYPE hdsl2ShdslSpanConfProfile OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(1..32)) SYNTAX SnmpAdminString (SIZE(1..32))
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 18, line 37 skipping to change at page 19, line 33
discovered in this HDSL2/SHDSL span." discovered in this HDSL2/SHDSL span."
::= { hdsl2ShdslSpanStatusEntry 1 } ::= { hdsl2ShdslSpanStatusEntry 1 }
hdsl2ShdslStatusMaxAttainableLineRate OBJECT-TYPE hdsl2ShdslStatusMaxAttainableLineRate OBJECT-TYPE
SYNTAX INTEGER(0..4112000) SYNTAX INTEGER(0..4112000)
UNITS "bps" UNITS "bps"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Contains the maximum attainable line rate in this HDSL2/SHDSL "Contains the maximum attainable line rate in this HDSL2/SHDSL
span." span. This object provides the maximum rate the line is
capable of achieving. This is based upon measurements made
during line probing."
::= { hdsl2ShdslSpanStatusEntry 2 } ::= { hdsl2ShdslSpanStatusEntry 2 }
hdsl2ShdslStatusActualLineRate OBJECT-TYPE hdsl2ShdslStatusActualLineRate OBJECT-TYPE
SYNTAX INTEGER(0..4112000) SYNTAX INTEGER(0..4112000)
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." should equal ifSpeed."
skipping to change at page 37, line 24 skipping to change at page 38, line 41
hdsl2ShdslSpanConfPSD INTEGER, hdsl2ShdslSpanConfPSD INTEGER,
hdsl2ShdslSpanConfTransmissionMode hdsl2ShdslSpanConfTransmissionMode
Hdsl2ShdslTransmissionModeType, Hdsl2ShdslTransmissionModeType,
hdsl2ShdslSpanConfRemoteEnabled INTEGER, hdsl2ShdslSpanConfRemoteEnabled INTEGER,
hdsl2ShdslSpanConfPowerFeeding INTEGER, hdsl2ShdslSpanConfPowerFeeding INTEGER,
hdsl2ShdslSpanConfCurrCondTargetMarginDown INTEGER, hdsl2ShdslSpanConfCurrCondTargetMarginDown INTEGER,
hdsl2ShdslSpanConfWorstCaseTargetMarginDown INTEGER, hdsl2ShdslSpanConfWorstCaseTargetMarginDown INTEGER,
hdsl2ShdslSpanConfCurrCondTargetMarginUp INTEGER, hdsl2ShdslSpanConfCurrCondTargetMarginUp INTEGER,
hdsl2ShdslSpanConfWorstCaseTargetMarginUp INTEGER, hdsl2ShdslSpanConfWorstCaseTargetMarginUp INTEGER,
hdsl2ShdslSpanConfUsedTargetMargins BITS, hdsl2ShdslSpanConfUsedTargetMargins BITS,
hdsl2ShdslSpanConfReferenceClock
Hdsl2ShdslClockReferenceType,
hdsl2ShdslSpanConfLineProbeEnable INTEGER,
hdsl2ShdslSpanConfProfileRowStatus RowStatus hdsl2ShdslSpanConfProfileRowStatus RowStatus
} }
hdsl2ShdslSpanConfProfileName OBJECT-TYPE hdsl2ShdslSpanConfProfileName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(1..32)) SYNTAX SnmpAdminString (SIZE(1..32))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the unique index associated with this profile. "This object is the unique index associated with this profile.
Entries in this table are referenced via the object Entries in this table are referenced via the object
skipping to change at page 38, line 51 skipping to change at page 40, line 20
DEFVAL { symmetric } DEFVAL { symmetric }
::= { hdsl2ShdslSpanConfProfileEntry 5 } ::= { hdsl2ShdslSpanConfProfileEntry 5 }
hdsl2ShdslSpanConfTransmissionMode OBJECT-TYPE hdsl2ShdslSpanConfTransmissionMode OBJECT-TYPE
SYNTAX Hdsl2ShdslTransmissionModeType SYNTAX Hdsl2ShdslTransmissionModeType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the regional setting for the SHDSL "This object specifies the regional setting for the SHDSL
line." line."
DEFVAL { region1 } DEFVAL { { region1 } }
::= { hdsl2ShdslSpanConfProfileEntry 6 } ::= { hdsl2ShdslSpanConfProfileEntry 6 }
hdsl2ShdslSpanConfRemoteEnabled OBJECT-TYPE hdsl2ShdslSpanConfRemoteEnabled OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
{ {
enabled(1), enabled(1),
disabled(2) disabled(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 40, line 55 skipping to change at page 42, line 26
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
margin enabled margin enabled
worstCaseUp worst case upstream target SNR margin worstCaseUp worst case upstream target SNR margin
enabled." enabled."
DEFVAL { 0 } DEFVAL { { currCondDown } }
::= { hdsl2ShdslSpanConfProfileEntry 13 } ::= { hdsl2ShdslSpanConfProfileEntry 13 }
hdsl2ShdslSpanConfReferenceClock OBJECT-TYPE
SYNTAX Hdsl2ShdslClockReferenceType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object configures the clock reference for the STU-C
in a SHDSL Line."
DEFVAL { localClk }
::= { hdsl2ShdslSpanConfProfileEntry 14 }
hdsl2ShdslSpanConfLineProbeEnable OBJECT-TYPE
SYNTAX INTEGER
{
disable(1),
enable(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object enables/disables support for Line Probe of
the units in a SHDSL line. When Line Probe is enabled, the
system performs Line Probing to find the best possible
rate. If Line probe is disabled, the rate adaptation phase
is skipped to shorten set up time."
DEFVAL { disable }
::= { hdsl2ShdslSpanConfProfileEntry 15 }
hdsl2ShdslSpanConfProfileRowStatus OBJECT-TYPE hdsl2ShdslSpanConfProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls creation/deletion of the associated "This object controls creation/deletion of the associated
entry in this table per the semantics of RowStatus. If an entry in this table per the semantics of RowStatus. If an
active entry is referenced in hdsl2ShdslSpanConfProfile, the active entry is referenced in hdsl2ShdslSpanConfProfile, the
entry MUST remain active until all references are removed." entry MUST remain active until all references are removed."
::= { hdsl2ShdslSpanConfProfileEntry 14 } ::= { hdsl2ShdslSpanConfProfileEntry 16 }
-- Segment Endpoint Alarm Configuration Profile group -- Segment Endpoint Alarm Configuration Profile group
-- --
hdsl2ShdslEndpointAlarmConfProfileTable OBJECT-TYPE hdsl2ShdslEndpointAlarmConfProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF Hdsl2ShdslEndpointAlarmConfProfileEntry SYNTAX SEQUENCE OF Hdsl2ShdslEndpointAlarmConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports definitions of alarm configuration "This table supports definitions of alarm configuration
skipping to change at page 53, line 35 skipping to change at page 55, line 45
hdsl2ShdslSpanConfMaxLineRate, hdsl2ShdslSpanConfMaxLineRate,
hdsl2ShdslSpanConfPSD, hdsl2ShdslSpanConfPSD,
hdsl2ShdslSpanConfTransmissionMode, hdsl2ShdslSpanConfTransmissionMode,
hdsl2ShdslSpanConfRemoteEnabled, hdsl2ShdslSpanConfRemoteEnabled,
hdsl2ShdslSpanConfPowerFeeding, hdsl2ShdslSpanConfPowerFeeding,
hdsl2ShdslSpanConfCurrCondTargetMarginDown, hdsl2ShdslSpanConfCurrCondTargetMarginDown,
hdsl2ShdslSpanConfWorstCaseTargetMarginDown, hdsl2ShdslSpanConfWorstCaseTargetMarginDown,
hdsl2ShdslSpanConfCurrCondTargetMarginUp, hdsl2ShdslSpanConfCurrCondTargetMarginUp,
hdsl2ShdslSpanConfWorstCaseTargetMarginUp, hdsl2ShdslSpanConfWorstCaseTargetMarginUp,
hdsl2ShdslSpanConfUsedTargetMargins, hdsl2ShdslSpanConfUsedTargetMargins,
hdsl2ShdslSpanConfReferenceClock,
hdsl2ShdslSpanConfLineProbeEnable,
hdsl2ShdslSpanConfProfileRowStatus hdsl2ShdslSpanConfProfileRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports objects that constitute configuration "This group supports objects that constitute configuration
profiles for configuring span related parameters in SHDSL profiles for configuring span related parameters in SHDSL
lines." lines."
::= { hdsl2ShdslGroups 13 } ::= { hdsl2ShdslGroups 13 }
END END
7. Security Considerations 7. Security Considerations
There are a number of management objects defined in this MIB that Blocking unauthorized access to the HDSL2-SHDSL MIB via the
have a MAX-ACCESS clause of read-write and/or read-create. Such element management system is outside the scope of this document.
objects may be considered sensitive or vulnerable in some network It should be noted that access to the MIB permits the unauthorized
environments. The support for SET operations in a non-secure entity to modify the profiles (section 6.4) such that both subscriber
environment without proper protection can have a negative effect on service and network operations can be interfered with. Subscriber
network operations. service can be altered by modifying any of a number of service
characteristics such as rate partitioning and maximum transmission
No managed objects in this MIB contain sensitive information. rates. Network operations can be impacted by modification of
notification thresholds such as SES thresholds.
SNMPv1 by itself is not a secure environment. Even if the network There are a number of managed objects in this MIB that may be
itself is secure (for example by using IPSec), even then, there is no considered to contain sensitive information. In particular,
control as to who on the secure network is allowed to access and certain objects may be considered sensitive in many environments,
GET/SET (read/change/create/delete) the objects in this MIB. since access to these objects would allow an intruder to obtain
information about which vendor's equipment is in use on the network.
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 It is recommended that the implementors consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the
of the User-based Security Model RFC 2574 [12] and the View- use of the User-based Security Model RFC 2574 [12] and the
based Access Control Model (VACM) RFC 2575 [15] is recommended. View-based Access Control Model RFC 2575 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to those objects only to those principals
(users) that have legitimate rights to indeed GET or SET (users) that have legitimate rights to access them.
(change/create/delete) 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 It should be noted that interface indices in this MIB are maintained
persistently. VACM data relating to these should be stored persistently. VACM data relating to these should be stored
persistently. 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.
8. Acknowledgments 8. 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 [23]), Gregory Bathrick and Faye Ly, as much of the text (RFC 2662 [23]), Gregory Bathrick and Faye Ly, as much of the text
and structure of this document originates in their documents. 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
[24]), Prayson Pate, Bob Lynch, and Kenneth Rehbehn, as the entirety [24]), Prayson Pate, Bob Lynch, and Kenneth Rehbehn, as the entirety
of the Security Considerations section was lifted from their document. of the Security Considerations section was lifted from their document.
skipping to change at page 54, line 47 skipping to change at page 57, line 28
David Horton of CITR. David Horton of CITR.
Other contributions were received from the following: Other contributions were received from the following:
Philip Bergstresser (Adtran) Philip Bergstresser (Adtran)
Steve Blackwell (Centillium) Steve Blackwell (Centillium)
Umberto Bonollo (NEC Australia) Umberto Bonollo (NEC Australia)
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)
Randy Presuhn (BMC Software)
Katy Sherman (Orckit) Katy Sherman (Orckit)
Mike Sneed (ECI) Mike Sneed (ECI)
Jon Turney (DSL Solutions) Jon Turney (DSL Solutions)
Aron Wahl (Memotec) Aron Wahl (Memotec)
Bert Wijnen (Lucent)
Michael Wrobel (Memotec) Michael Wrobel (Memotec)
9. References 9. References
[1] Harrington, D., Presuhn, R., and Wijnen, B., "An Architecture [1] Harrington, D., Presuhn, R., and Wijnen, B., "An Architecture
for Describing SNMP Management Frameworks", RFC 2571, April 1999. for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[2] Rose, M., and McCloghrie, K., "Structure and Identification of [2] Rose, M., and McCloghrie, K., "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, RFC Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990. 1155, May 1990.
[3] Rose, M., and McCloghrie, K., "Concise MIB Definitions", STD 16, [3] Rose, M., and McCloghrie, K., "Concise MIB Definitions", STD 16,
RFC 1212, March 1991. RFC 1212, March 1991.
skipping to change at page 56, line 47 skipping to change at page 59, line 37
[22] Tesink, K., "Textual Conventions for MIB Modules Using [22] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC 2493, January Performance History Based on 15 Minute Intervals", RFC 2493, January
1999. 1999.
[23] Bathrick, G., Ly, F., "Definitions of Managed Objects for the [23] Bathrick, G., Ly, F., "Definitions of Managed Objects for the
ADSL Lines", RFC 2662, August 1999. ADSL Lines", RFC 2662, August 1999.
[24] Pate, P., Lynch, B., Rehbehn, K., "Definitions of Managed [24] Pate, P., Lynch, B., Rehbehn, K., "Definitions of Managed
Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Objects for Monitoring and Controlling the UNI/NNI Multilink Frame
Relay Function", RFC 3020, December 2000. Relay Function", RFC 3020, December 2000.
[25] American National Standards Institute, "Coded Identification
of Equipment Entities of the North American Telecommunications
System for the Purpose of Information Exchange", T1.213-2001.
10. Intellectual Property Notice 10. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
 End of changes. 

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