draft-ietf-adslmib-gshdslbis-05.txt   draft-ietf-adslmib-gshdslbis-06.txt 
Network Working Group C. Sikes Network Working Group C. Sikes
Internet-Draft Paradyne Corporation Internet-Draft Paradyne Corporation
Expires: March 11, 2005 B. Ray Expires: March 29, 2005 B. Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
R. Abbi R. Abbi
Alcatel USA Alcatel USA
September 10, 2004 September 28, 2004
Definitions of Managed Objects for G.shdsl.bis Lines Definitions of Managed Objects for G.shdsl.bis Lines
draft-ietf-adslmib-gshdslbis-05.txt draft-ietf-adslmib-gshdslbis-06.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.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 March 11, 2005. This Internet-Draft will expire on March 29, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2004).
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). The MIB conventions defined in HDSL2-SHDSL-Line MIB (RFC 3276). This
module described in this document will obsolete the MIB module document obsoletes RFC 3276.
described in RFC 3276.
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 . . . . . . . . . . . . . . . . . 5
4.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . 10
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 . . . . . . . . . . . . . . . . . . . . . . . . . 14
7. Implementation Analysis . . . . . . . . . . . . . . . . . . . 65 7. Implementation Analysis . . . . . . . . . . . . . . . . . . . 65
8. Security Considerations . . . . . . . . . . . . . . . . . . . 66 8. Security Considerations . . . . . . . . . . . . . . . . . . . 66
skipping to change at page 5, line 45 skipping to change at page 5, line 45
=================================================================== ===================================================================
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
revision of the RFC does not require any new action from IANA.
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;
H2RU for HDSL2, or SRU for SHDSL. H2RU for HDSL2, or SRU for SHDSL.
E. xU refers to any HDSL2/SHDSL unit; either an xtu or xru. E. xU refers to any HDSL2/SHDSL unit; either an xtu or xru.
F. CRC is cyclic redundancy check [G.991.2]. F. CRC is cyclic redundancy check [G.991.2].
G. ES means errored second [G.991.2]. G. ES means errored second [G.991.2].
skipping to change at page 15, line 13 skipping to change at page 15, line 20
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 "200409100000Z" -- September 10, 2004 LAST-UPDATED "200409280000Z" -- September 28, 2004
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
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
skipping to change at page 16, line 5 skipping to change at page 16, line 12
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).
REVISION "200409100000Z" -- September 10, 2004 Copyright (C) The Internet Society (2004). This version of
DESCRIPTION "Initial version, published as RFC xxxx. this MIB module is part of RFC xxxx; see the RFC itself for
The following changes have been made from RFC 3276: full legal notices."
REVISION "200409280000Z" -- September 28, 2004
DESCRIPTION "This version, published as RFC xxxx.
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 32766 include 3. Clarified that the rates from RFC 32766 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
tip and ring are reversed on a wire pair. tip and ring are reversed on a wire pair.
5. Added an object to display the activation state 5. Added an object to display the activation state
skipping to change at page 69, line 48 skipping to change at page 69, line 48
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects
for the ADSL Lines", RFC 2662, August 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.
[RFC3020] Pate, P., Lynch, B. and K. Rehbehn, "Definitions of
Managed Objects for Monitoring and Controlling the UNI/
NNI Multilink Frame Relay Function", RFC 3020, December
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 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3418] Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Waldbusser, "Management Information Base (MIB) for the Access Control Model (VACM) for the Simple Network
Simple Network Management Protocol (SNNP)", STD 62, RFC Management Protocol (SNMP)", STD 62, RFC 3415, December
3418, December 2002. 2002.
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC
3593, September 2003.
[T1E1.4] American National Standards Institute, "ANSI T1E1.4/ [T1E1.4] American National Standards Institute, "ANSI T1E1.4/
2000-006", February 2000. 2000-006", February 2000.
10.2 Informative References 10.2 Informative References
[RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects
for the ADSL Lines", RFC 2662, August 1999.
[RFC3020] Pate, P., Lynch, B. and K. Rehbehn, "Definitions of
Managed Objects for Monitoring and Controlling the UNI/
NNI Multilink Frame Relay Function", RFC 3020, December
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.
[RFC3410] Case, J., Mindy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mindy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet "Introduction and Applicability Statements for Internet
Standard Management Framework", RFC 3416, December 2002. Standard Management Framework", RFC 3416, December 2002.
[RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based [RFC3418] Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S.
Access Control Model (VACM) for the Simple Network Waldbusser, "Management Information Base (MIB) for the
Management Protocol (SNMP)", STD 62, RFC 3415, December Simple Network Management Protocol (SNNP)", STD 62, RFC
2002. 3418, December 2002.
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC
3593, September 2003.
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
 End of changes. 

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