draft-ietf-adslmib-hc-tc-00.txt   draft-ietf-adslmib-hc-tc-01.txt 
INTERNET DRAFT R. Abbi Network Working Group B. Ray
Expires October 1, 2002 Alcatel Category: Internet Draft PESA Switching Systems
R. Abbi
B. Ray Alcatel
March 2002 June 2002
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-00.txt draft-ietf-adslmib-hc-tc-01.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]. Internet-Drafts are all provisions of Section 10 of [RFC2026]. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
skipping to change at page 2, line 7 skipping to change at page 2, line 7
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
This document presents a set of Textual Conventions for MIB modules This document presents a set of Textual Conventions for MIB modules
which extends the conventions presented in RFC2493 to 64 bit which extends the conventions presented in RFC2493 to 64 bit
resolution using the conventions presented in RFC2856. resolution using the conventions presented in RFC2856.
Table of Contents Table of Contents
1 The SNMP Management Framework ................................. 2 1. The SNMP Management Framework ................................... 2
2 Overview ...................................................... 3 2. Overview ........................................................ 3
3 Definitions ................................................... 4 3. Definitions ..................................................... 4
4 Acknowledgements .............................................. 8 References ...................................................... 8
5 References .................................................... 8 Security Considerations ......................................... 10
6 Security Considerations ....................................... 10 IANA Considerations ............................................. 10
7 Author's Address .............................................. 10 Acknowledgements ................................................ 10
8 Intellectual Property ......................................... 10 Intellectual Property Notice .................................... 10
9 Full Copyright Statement ...................................... 11 Authors' Addresses .............................................. 10
Full Copyright Statement ........................................ 11
1. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [RFC2571]. o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
skipping to change at page 4, line 20 skipping to change at page 4, line 21
HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
Counter64, Counter64,
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 "200203310000Z" -- March 31, 2002 LAST-UPDATED "200206160000Z" -- June 16, 2002
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
Inovia Telecoms Postal: P.O. Box 37324
Postal: 1017 Main Campus Drive Raleigh NC 27627-7324
Raleigh NC 27606 USA Email: sneedmike@hotmail.com
Email: Mike.Sneed@go.ecitele.com
Phone: +1 919 513 1435 Co-editor: Bob Ray
PESA Switching Systems, Inc.
Postal: 330-A Wynn Drive
Huntsville, AL 35805 USA
Email: rray@pesa.com
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@usa.alcatel.com Email: Rajesh.Abbi@alcatel.com
Phone: +1 919 850 6194 Phone: +1 919 850 6194
Co-editor: Bob Ray
Email: bob_ray_99@yahoo.com
" "
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."
REVISION "200206160000Z" -- June 16, 2002
DESCRIPTION "Corrected addresses and references."
::= { mib-2 xxx } -- to be assigned by IANA ::= { mib-2 xxx } -- to be assigned by IANA
-- The Textual Conventions defined below are organized -- The Textual Conventions defined below are organized
-- alphabetically -- alphabetically
-- Use of these TCs assumes the following: -- Use of these TCs assumes the following:
-- 0 The agent supports 15 minute based history -- 0 The agent supports 15 minute based history
-- counters. -- counters.
-- 0 The agent is capable of keeping a history of n -- 0 The agent is capable of keeping a history of n
-- intervals of 15 minute performance data. The -- intervals of 15 minute performance data. The
-- value of n is defined by the specific MIB -- value of n is defined by the specific MIB
-- module but shall be 0 < n =< 96. -- module but shall be 0 < n =< 96.
-- 0 The agent may optionally support performance -- 0 The agent may optionally support performance
-- data aggregating the history intervals. -- data aggregating the history intervals.
-- 0 The agent will keep separate tables for the -- 0 The agent will keep separate tables for the
-- current interval, the history intervals, and -- current interval, the history intervals, and
-- the total aggregates. -- the total aggregates.
-- 0 The agent will keep the following objects. -- 0 The agent will keep the following objects.
-- If performance data is kept for multiple instances -- If performance data is kept for multiple instances
-- of a measured entity, then -- of a measured entity, then
-- these objects are applied to each instance of -- these objects are applied to each instance of
-- the measured entity (e.g., interfaces). -- the measured entity (e.g., interfaces).
skipping to change at page 8, line 21 skipping to change at page 8, line 19
which rely solely upon the (Counter64) ASN.1 tag to which rely solely upon the (Counter64) ASN.1 tag to
determine object semantics will mistakenly operate upon determine object semantics will mistakenly operate upon
objects of this type as they would for Counter64 objects. objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term This textual convention represents a limited and short-term
solution, and may be deprecated as a long term solution is solution, and may be deprecated as a long term solution is
defined and deployed to replace it." defined and deployed to replace it."
SYNTAX Counter64 SYNTAX Counter64
END END
4. Acknowledgements Informative References
This document borrows tremendously from [RFC2493] and [RFC2856].
As such, any credit for the text found within should be fully
attributed to the authors of those documents.
5. References
[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.
[RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification [RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", of Management Information for TCP/IP-based Internets",
STD 16, RFC 1155, May 1990. STD 16, RFC 1155, May 1990.
skipping to change at page 9, line 25 skipping to change at page 9, line 14
[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 [RFC2558] Tesink, K., "Definitions of Managed Objects for the
SONET/SDH Interface Type", RFC 2558, March 1999. SONET/SDH Interface Type", RFC 2558, March 1999.
[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.
[RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction to Version 3 of the Internet-standard "Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999. Network Management Framework", RFC 2570, April 1999.
[RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for Describing SNMP Management Frameworks", Architecture for Describing SNMP Management Frameworks",
RFC 2571, April 1999. RFC 2571, April 1999.
skipping to change at page 10, line 11 skipping to change at page 9, line 54
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.
[RFC2856] Bierman, A., McCloghrie, K., Presuhn, R., "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.
[VDSL-MIB] Abbi, R., Ray, B., work in progress. [VDSL-MIB] Ray, B. and R. Abbi, work in progress.
6. Security Considerations 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 MIB defines a set of textual conventions which may be used by other MIB
modules to define management objects. modules to define management objects.
Meaningful security considerations can only be written in the modules Meaningful security considerations can only be written in the modules
that define management objects. that define management objects.
7. Author's Address IANA Considerations
Rajesh Abbi Prior to publication of this memo as an RFC, IANA is requested to
Alcatel USA make a suitable OBJECT IDENTIFIER assignment.
2912 Wake Forest Road
Raleigh, NC 27609-7860 USA
EMail: Rajesh.Abbi@usa.alcatel.com
Phone: +1 919 850 6194
Bob Ray Acknowledgements
EMail: bob_ray_99@yahoo.com
8. Intellectual Property This document borrows tremendously from [RFC2493] and [RFC2856].
As such, any credit for the text found within should be fully
attributed to the authors of those documents.
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
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of claims of rights made available for publication and any assurances of
skipping to change at page 11, line 8 skipping to change at page 10, line 49
obtain a general license or permission for the use of such obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
9. Full Copyright Statement Authors' Addresses
Bob Ray
PESA Switching Systems, Inc.
330-A Wynn Drive
Huntsville, AL 35805 USA
Phone: +1 256 726 9200 ext. 142
Fax: +1 256 726 9271
EMail: rray@pesa.com
Rajesh Abbi
Alcatel USA
2912 Wake Forest Road
Raleigh, NC 27609-7860 USA
Phone: +1 919 850 6194
EMail: Rajesh.Abbi@alcatel.com
Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
 End of changes. 

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