draft-ietf-adslmib-hc-tc-04.txt   draft-ietf-adslmib-hc-tc-05.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
June 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-04.txt draft-ietf-adslmib-hc-tc-05.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 2, line 14 skipping to change at page 2, line 14
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
7. Security Considerations ....................................... 9 7. Security Considerations ....................................... 9
8. Acknowledgements .............................................. 10 8. Acknowledgements .............................................. 9
9. Authors' Addresses ............................................ 10 9. Authors' Addresses ............................................ 9
10. Full Copyright Statement ...................................... 10 10. Full Copyright Statement ...................................... 10
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a Structure of Management Information (SMI). This memo specifies a
MIB module that is compliant to the SMIv2, which is described in STD MIB module that is compliant to the SMIv2, which is described in STD
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
2580 [RFC2580]. 2580 [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. Overview 2. Overview
In cases where a manager must obtain performance history data about In cases where a manager must obtain performance history data about
the behavior of equipment it manages, several strategies can be the behavior of equipment it manages, several strategies can be
followed in the design of a MIB module that represents the managed followed in the design of a MIB module that represents the managed
equipment, including: equipment, including:
- The agent counts events on a continuous basis and, whenever - The agent counts events on a continuous basis and, whenever
desired, the manager obtains the value of the event counter and desired, the manager obtains the value of the event counter and
adjusts its understanding of the history of events at the agent. adjusts its understanding of the history of events at the agent.
skipping to change at page 4, line 4 skipping to change at page 4, line 8
HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN
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 "200306060000Z" -- June 6, 2003 LAST-UPDATED "200309020000Z" -- September 2, 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 43 skipping to change at page 4, line 48
" "
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 "200306060000Z" -- June 6, 2003 REVISION "200309020000Z" -- September 2, 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 8, line 32 skipping to change at page 8, line 33
can be obtained from the IETF Secretariat. can 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.
5. Normative References 5. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
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.,
skipping to change at page 9, line 21 skipping to change at page 9, line 23
[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.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 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.
[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.
7. Security Considerations 7. Security Considerations
SNMP versions prior to SNMPv3 did not include adequate security. This module does not define any management objects. Instead, it
Even if the network itself is secure (for example by using IPSec), defines a set of textual conventions which may be used by other
even then, there is no control as to who on the secure network is MIB modules to define management objects.
allowed to access and GET/SET (read/change/create/delete) objects
which utilize the textual conventions defined in this MIB module.
It is RECOMMENDED that implementers consider the security features
as provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Meaningful security considerations can only be written in the MIB
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to modules that define management objects. This document has
enable cryptographic security. It is then a customer/operator therefore no impact on the security of the Internet.
responsibility to ensure that the SNMP entity giving access to an
instance of a MIB module which utilizes the textual conventions
defined in this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
8. Acknowledgements 8. Acknowledgements
This document borrows tremendously from [RFC2493] and [RFC2856]. This document borrows tremendously from [RFC2493] 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
 End of changes. 

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