draft-ietf-adslmib-hc-tc-05.txt   draft-ietf-adslmib-hc-tc-06.txt 
Network Working Group B. Ray Network Working Group B. Ray
Category: Internet Draft PESA Switching Systems Category: Internet Draft PESA Switching Systems
R. Abbi R. Abbi
Alcatel Alcatel
September 2003 September 2003
High Capacity Textual Conventions for MIB Modules Using High Capacity Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals Performance History Based on 15 Minute Intervals
draft-ietf-adslmib-hc-tc-05.txt draft-ietf-adslmib-hc-tc-06.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that 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 42 skipping to change at page 1, line 42
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This document presents a set of High Capacity Textual Conventions This document presents a set of High Capacity Textual Conventions
for use in MIB modules which require performance history based upon for use in MIB modules which require performance history based upon
15 minute intervals. The Textual Conventions defined in this 15 minute intervals. The Textual Conventions defined in this
document extend the conventions presented in RFC 2493 to 64 bit document extend the conventions presented in RFC 3593 to 64 bit
resolution using the conventions presented in RFC 2856. resolution using the conventions presented in RFC 2856.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework .................... 2 1. The Internet-Standard Management Framework .................... 2
2. Overview ...................................................... 2 2. Overview ...................................................... 2
3. Definitions ................................................... 3 3. Definitions ................................................... 3
4. Intellectual Property ......................................... 8 4. Intellectual Property ......................................... 8
5. Normative References .......................................... 8 5. Normative References .......................................... 8
6. Informative References ........................................ 8 6. Informative References ........................................ 8
skipping to change at page 3, line 4 skipping to change at page 2, line 57
- The agent allocates events to 'buckets' where each bucket - The agent allocates events to 'buckets' where each bucket
represents an interval of time. represents an interval of time.
Telecommunications equipment often makes use of the latter strategy. Telecommunications equipment often makes use of the latter strategy.
For such equipment the standard practice is that history data is For such equipment the standard practice is that history data is
maintained by the agent in terms of 15-minute intervals [T1.231]. maintained by the agent in terms of 15-minute intervals [T1.231].
MIB modules for collecting performance history based on 15-minute MIB modules for collecting performance history based on 15-minute
intervals have been defined for the DS1/E1 [RFC2495], DS3/E3 intervals have been defined for the DS1/E1 [RFC2495], DS3/E3
[RFC2496], SONET/SDH [RFC2558], ADSL [RFC2662], HDLS2 and SHDSL [RFC2496], SONET/SDH [RFC3592], ADSL [RFC2662], HDLS2 and SHDSL
[RFC3276] interface types. These MIB modules use a common set of [RFC3276] interface types. These MIB modules use a common set of
textual conventions defined in [RFC2493]. Those textual textual conventions defined in [RFC3593]. Those textual
conventions are based on the Gauge32 data type. conventions are based on the Gauge32 data type.
A need has arisen to define 64-bit versions of the textual A need has arisen to define 64-bit versions of the textual
conventions in [RFC2493]. Ideally, these high-capacity textual conventions in [RFC3593]. Ideally, these high-capacity textual
conventions would be based on a Gauge64 or Unsigned64 data type, but conventions would be based on a Gauge64 or Unsigned64 data type, but
unfortunately no such types exist in SMIv2. The next best choice unfortunately no such types exist in SMIv2. The next best choice
would be to base them on the CounterBasedGauge64 textual convention would be to base them on the CounterBasedGauge64 textual convention
presented in [RFC2856], but that is not possible either since SMIv2 presented in [RFC2856], but that is not possible either since SMIv2
allows only base types to be used in defining textual conventions. allows only base types to be used in defining textual conventions.
Therefore, the textual conventions presented in this memo are based Therefore, the textual conventions presented in this memo are based
directly on the Counter64 type, like those in [RFC2856]. They are directly on the Counter64 type, like those in [RFC2856]. They are
subject to the following limitations: subject to the following limitations:
- The MAX-ACCESS of objects defined using these textual conventions - The MAX-ACCESS of objects defined using these textual conventions
skipping to change at page 4, line 10 skipping to change at page 4, line 9
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
Counter64, Counter64,
Unsigned32, Unsigned32,
Gauge32, Gauge32,
mib-2 FROM SNMPv2-SMI mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC; TEXTUAL-CONVENTION FROM SNMPv2-TC;
hcPerfHistTCMIB MODULE-IDENTITY hcPerfHistTCMIB MODULE-IDENTITY
LAST-UPDATED "200309020000Z" -- September 2, 2003 LAST-UPDATED "200309240000Z" -- September 24, 2003
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
Sand Channel Systems Sand Channel Systems
Postal: P.O. Box 37324 Postal: P.O. Box 37324
Raleigh NC 27627-7324 Raleigh NC 27627-7324
USA USA
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
skipping to change at page 4, line 48 skipping to change at page 4, line 47
" "
DESCRIPTION DESCRIPTION
"This MIB Module provides Textual Conventions to be "This MIB Module provides Textual Conventions to be
used by systems supporting 15 minute based performance used by systems supporting 15 minute based performance
history counts that require high-capacity counts. history counts that require high-capacity counts.
Copyright (C) The Internet Society (2003). This version Copyright (C) The Internet Society (2003). This version
of this MIB module is part of RFC XXXX: see the RFC of this MIB module is part of RFC XXXX: see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
REVISION "200309020000Z" -- September 2, 2003 REVISION "200309240000Z" -- September 24, 2003
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
::= { mib-2 YYYY } ::= { mib-2 YYYY }
-- RFC Ed.: replace YYYY with IANA-assigned number & remove this note -- RFC Ed.: replace YYYY with IANA-assigned number & remove this note
HCPerfValidIntervals ::= TEXTUAL-CONVENTION HCPerfValidIntervals ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of near end intervals for which data was "The number of near end intervals for which data was
collected. The value of an object with an collected. The value of an object with an
skipping to change at page 9, line 10 skipping to change at page 9, line 9
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[T1.231] American National Standard for Telecommunications - [T1.231] American National Standard for Telecommunications -
Digital Hierarchy - Layer 1 In-Service Digital Digital Hierarchy - Layer 1 In-Service Digital
Transmission Performance Monitoring, ANSI T1.231-1997, Transmission Performance Monitoring, ANSI T1.231-1997,
September 1997. September 1997.
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, October 1996.
[RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC
2493, January 1999.
[RFC2495] Fowler, D., "Definitions of Managed Objects for the DS1, [RFC2495] Fowler, D., "Definitions of Managed Objects for the DS1,
E1, DS2 and E2 Interface Types", RFC 2495, January 1999. E1, DS2 and E2 Interface Types", RFC 2495, January 1999.
[RFC2496] Fowler, D., "Definitions of Managed Objects for the [RFC2496] Fowler, D., "Definitions of Managed Objects for the
DS3/E3 Interface Type", RFC 2496, January 1999. DS3/E3 Interface Type", RFC 2496, January 1999.
[RFC2558] Tesink, K., "Definitions of Managed Objects for the [RFC3592] Tesink, K., "Definitions of Managed Objects for the
SONET/SDH Interface Type", RFC 2558, March 1999. Synchronous Optical Network/Synchronous Digital
Hierachy (SONET/SDH) Interface Type", RFC 3592,
September 2003.
[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.
[RFC2856] Bierman, A., McCloghrie, K. and R. Presuhn, "Textual [RFC2856] Bierman, A., McCloghrie, K. and R. Presuhn, "Textual
Conventions for Additional High Capacity Data Types", Conventions for Additional High Capacity Data Types",
RFC2856, June 2000. RFC2856, June 2000.
[RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects [RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects
for High Bit-rate DSL - 2nd Generation (HDSL2) and for High Bit-rate DSL - 2nd Generation (HDSL2) and
Single-Pair High-Speed Digital Subscriber Line (SHDSL) Single-Pair High-Speed Digital Subscriber Line (SHDSL)
Lines", RFC3276, May 2002. Lines", RFC3276, May 2002.
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC
3593, September 2003.
7. Security Considerations 7. Security Considerations
This module does not define any management objects. Instead, it This module does not define any management objects. Instead, it
defines a set of textual conventions which may be used by other defines a set of textual conventions which may be used by other
MIB modules to define management objects. MIB modules to define management objects.
Meaningful security considerations can only be written in the MIB Meaningful security considerations can only be written in the MIB
modules that define management objects. This document has modules that define management objects. This document has
therefore no impact on the security of the Internet. therefore no impact on the security of the Internet.
8. Acknowledgements 8. Acknowledgements
This document borrows tremendously from [RFC2493] and [RFC2856]. This document borrows tremendously from [RFC3593] and [RFC2856].
As such, any credit for the text found within should be fully As such, any credit for the text found within should be fully
attributed to the authors of those documents. attributed to the authors of those documents.
9. Authors' Addresses 9. Authors' Addresses
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
USA USA
 End of changes. 

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