draft-ietf-adslmib-hc-tc-03.txt   draft-ietf-adslmib-hc-tc-04.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
December 2002 June 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-03.txt draft-ietf-adslmib-hc-tc-04.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.
working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also Internet-Drafts are working documents of the Internet Engineering
distribute working documents as Internet-Drafts. Task Force (IETF), its areas, and its working groups. Note that
other groups may also 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
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference 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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This document presents a set of Textual Conventions for MIB modules This document presents a set of High Capacity Textual Conventions
which extends the conventions presented in RFC2493 to 64 bit for use in MIB modules which require performance history based upon
15 minute intervals. The Textual Conventions defined in this
document extend the conventions presented in RFC 2493 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 Internet-Standard Management Framework .................... 2
2. Overview ........................................................ 3 2. Overview ...................................................... 2
3. Definitions ..................................................... 4 3. Definitions ................................................... 3
References ...................................................... 8 4. Intellectual Property ......................................... 8
Security Considerations ......................................... 10 5. Normative References .......................................... 8
IANA Considerations ............................................. 10 6. Informative References ........................................ 8
Acknowledgements ................................................ 10 7. Security Considerations ....................................... 9
Intellectual Property Notice .................................... 11 8. Acknowledgements .............................................. 10
Authors' Addresses .............................................. 11 9. Authors' Addresses ............................................ 10
Full Copyright Statement ........................................ 11 10. Full Copyright Statement ...................................... 10
1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in STD
16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215
[RFC1215]. The second version, called SMIv2, is described in STD
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58,
RFC 2580 [RFC2580].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [RFC1157]. A second version of the
SNMP message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC 1901 [RFC1901]
and RFC 1906 [RFC1906]. The third version of the message
protocol is called SNMPv3 and described in RFC 1906 [RFC1906],
RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [RFC1157]. A second set of
protocol operations and associated PDU formats is described in
RFC 1905 [RFC1905].
o A set of fundamental applications described in RFC 2573 [RFC2573] 1. The Internet-Standard Management Framework
and the view-based access control mechanism described in RFC 2575
[RFC2575].
A more detailed introduction to the current SNMP Management Framework For a detailed overview of the documents that describe the current
can be found in RFC 2570 [RFC2570]. Internet-Standard Management Framework, please refer to section 7 of
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. Objects in the MIB are the Management Information Base or MIB. MIB objects are generally
defined using the mechanisms defined in the SMI. accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
This memo specifies a MIB module that is compliant to the SMIv2. The Structure of Management Information (SMI). This memo specifies a
textual conventions defined in this MIB module cannot be translated MIB module that is compliant to the SMIv2, which is described in STD
to SMIv1 since the Counter64 type does not exist in SMIv1. 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
2580 [RFC2580].
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 that represents the managed followed in the design of a MIB module that represents the managed
equipment, including: equipment, including:
0 The agent counts events on a continuous basis and, - The agent counts events on a continuous basis and, whenever
whenever desired, the manager obtains the value of the event desired, the manager obtains the value of the event counter and
counter and adjusts its understanding of the history of events adjusts its understanding of the history of events at the agent.
at the agent.
0 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], and ADSL [RFC2622] interface types. [RFC2496], SONET/SDH [RFC2558], ADSL [RFC2662], HDLS2 and SHDSL
These MIB modules use a common set of textual conventions defined in [RFC3276] interface types. These MIB modules use a common set of
[RFC2493]. Those textual conventions are based on the Gauge32 textual conventions defined in [RFC2493]. Those textual
data type. conventions are based on the Gauge32 data type.
A need has arisen in connection with recent work on a VDSL MIB A need has arisen to define 64-bit versions of the textual
[VDSL-MIB] to define 64-bit versions of the textual conventions conventions in [RFC2493]. Ideally, these high-capacity textual
in [RFC2493]. Ideally, these high-capacity textual conventions would conventions would be based on a Gauge64 or Unsigned64 data type, but
be based on a Gauge64 or Unsigned64 data type, but unfortunately no unfortunately no such types exist in SMIv2. The next best choice
such types exist in SMIv2. The next best choice would be to base would be to base them on the CounterBasedGauge64 textual convention
them on the CounterBasedGauge64 textual convention presented in presented in [RFC2856], but that is not possible either since SMIv2
[RFC2856], but that is not possible either since SMIv2 allows only allows only base types to be used in defining textual conventions.
base types to be used textual conventions. Therefore the textual Therefore, the textual conventions presented in this memo are based
conventions presented in this memo are based directly on the directly on the Counter64 type, like those in [RFC2856]. They are
Counter64 type, like those in [RFC2856]. They are subject to the subject to the following limitations:
following limitations:
- The MAX-ACCESS of objects defined using these textual conventions - The MAX-ACCESS of objects defined using these textual conventions
must be read-only, because the MAX-ACCESS of the underlying must be read-only, because the MAX-ACCESS of the underlying
Counter64 type is read-only. Counter64 type is read-only.
- No sub-range can be specified in object definitions using these - No sub-range can be specified in object definitions using these
textual conventions, because sub-ranges are not allowed on textual conventions, because sub-ranges are not allowed on
Counter64 objects. Counter64 objects.
- No DEFVAL clause can be specified in object definitions using - No DEFVAL clause can be specified in object definitions using
these textual conventions, because DEFVALs are not allowed on these textual conventions, because DEFVALs are not allowed on
Counter64 objects. Counter64 objects.
- Objects defined using these textual conventions cannot be used - Objects defined using these textual conventions cannot be used
in an INDEX clause, because there is no INDEX clause mapping in an INDEX clause, because there is no INDEX clause mapping
defined for objects of type Counter64. defined for objects of type Counter64.
Use of the textual conventions presented in this memo assumes the
following:
- The agent supports 15 minute based history counters.
- The agent is capable of keeping a history of 96 intervals of 15
minute performance data.
- The agent may optionally support performance data aggregating the
history intervals.
- The agent will keep separate tables for the current interval, the
history intervals, and the total aggregates.
3. Definitions 3. Definitions
HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
Counter64, Counter64,
Unsigned32, Unsigned32,
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 "200212300000Z" -- December 30, 2002 LAST-UPDATED "200306060000Z" -- June 6, 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
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
Phone: +1 206 600 7022 Phone: +1 206 600 7022
Co-editor: Bob Ray Co-editor: Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
Postal: 330-A Wynn Drive Postal: 330-A Wynn Drive
Huntsville, AL 35805 USA Huntsville, AL 35805
USA
Email: rray@pesa.com Email: rray@pesa.com
Phone: +1 256 726 9200 ext. 142 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@alcatel.com Email: Rajesh.Abbi@alcatel.com
Phone: +1 919 850 6194 Phone: +1 919 850 6194
" "
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."
REVISION "200209230000Z" -- September 23, 2002
DESCRIPTION "Added HCPerfValidIntervals, HCPerfInvalidIntervals,
HCPerfTimeElapsed, and HCPerfIntervalThreshold."
REVISION "200212300000Z" -- December 30, 2002
DESCRIPTION "Updated contact info for chair."
::= { mib-2 xxx } -- to be assigned by IANA
-- The Textual Conventions defined below are organized Copyright (C) The Internet Society (2003). This version
-- alphabetically of this MIB module is part of RFC XXXX: see the RFC
-- Use of these TCs assumes the following: itself for full legal notices."
-- 0 The agent supports 15 minute based history -- RFC Ed.: replace XXXX with assigned number & remove this note
-- counters. REVISION "200306060000Z" -- June 6, 2003
-- 0 The agent is capable of keeping a history of 96 DESCRIPTION "Initial version, published as RFC XXXX."
-- intervals of 15 minute performance data. -- RFC Ed.: replace XXXX with assigned number & remove this note
-- 0 The agent may optionally support performance ::= { mib-2 YYYY }
-- data aggregating the history intervals. -- RFC Ed.: replace YYYY with IANA-assigned number & remove this note
-- 0 The agent will keep separate tables for the
-- current interval, the history intervals, and
-- the total aggregates.
-- 0 The agent will keep the following objects.
-- If performance data is kept for multiple instances
-- of a measured entity, then
-- these objects are applied to each instance of
-- the measured entity (e.g., interfaces).
HCPerfValidIntervals ::= TEXTUAL-CONVENTION HCPerfValidIntervals ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of previous near end intervals for which "The number of near end intervals for which data was
data was collected. The value will be 96 unless the collected. The value of an object with an
measurement was (re-)started within the last 900 minutes, HCPerfValidIntervals syntax will be 96 unless the
measurement was (re-)started within the last 1440 minutes,
in which case the value will be the number of complete 15 in which case the value will be the number of complete 15
minute intervals for which the agent has at least some minute intervals for which the agent has at least some data.
data. In certain cases (e.g., in the case where the agent In certain cases (e.g., in the case where the agent is a
is a proxy) it is possible that some intervals are proxy) it is possible that some intervals are unavailable.
unavailable. In this case, this interval is the maximum In this case, this interval is the maximum interval number
interval number for which data is available." for which data is available."
SYNTAX INTEGER (0..96) SYNTAX Gauge32 (0..96)
HCPerfInvalidIntervals ::= TEXTUAL-CONVENTION HCPerfInvalidIntervals ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of previous intervals for which no data is "The number of near end intervals for which no data is
available. This object will typically be zero except in available. The value of an object with an
cases where the data for some intervals are not available HCPerfInvalidIntervals syntax will typically be zero except
in cases where the data for some intervals are not available
(e.g., in proxy situations)." (e.g., in proxy situations)."
SYNTAX INTEGER (0..96) SYNTAX Gauge32 (0..96)
HCPerfTimeElapsed ::= TEXTUAL-CONVENTION HCPerfTimeElapsed ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of seconds that have elapsed since the beginning "The number of seconds that have elapsed since the beginning
of the current measurement period. If, for some reason, such of the current measurement period. If, for some reason,
as an adjustment in the system's time-of-day clock or the such as an adjustment in the system's time-of-day clock or
addition of a leap second, the current interval exceeds the the addition of a leap second, the duration of the current
maximum value, the agent will return the maximum value. interval exceeds the maximum value, the agent will return
the maximum value.
For 15 minute intervals, the range is limited to (0..899). For 15 minute intervals, the range is limited to (0..899).
For 24 hour intervals, the range is limited to (0..86399)." For 24 hour intervals, the range is limited to (0..86399)."
SYNTAX Unsigned32 (0..86399) SYNTAX Gauge32 (0..86399)
HCPerfIntervalThreshold ::= TEXTUAL-CONVENTION HCPerfIntervalThreshold ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention defines a range of values that may be set "This convention defines a range of values that may be set
in a fault threshold alarm control. As the number of in a fault threshold alarm control. As the number of
seconds in a 15-minute interval numbers at most 900, objects seconds in a 15-minute interval numbers at most 900,
of this type may have a range of 0...900, where the value of objects of this type may have a range of 0...900, where the
0 disables the alarm." value of 0 disables the alarm."
SYNTAX Unsigned32 (0..900) SYNTAX Unsigned32 (0..900)
HCPerfCurrentCount ::= TEXTUAL-CONVENTION HCPerfCurrentCount ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter associated with a performance measurement in a "A gauge associated with a performance measurement in a
current 15 minute measurement interval. The value of this current 15 minute measurement interval. The value of an
counter starts from zero and is increased when associated object with an HCPerfCurrentCount syntax starts from zero
events occur, until the end of the 15 minute interval. and is increased when associated events occur, until the
At that time the value of the counter is stored in the end of the 15 minute interval. At that time the value of
first 15 minute history interval, and the CurrentCount is the gauge is stored in the first 15 minute history
restarted at zero. In the case where the agent has no valid interval, and the gauge is restarted at zero. In the case
data available for the current interval the corresponding where the agent has no valid data available for the
object instance is not available and upon a retrieval current interval, the corresponding object instance is not
request a corresponding error message shall be returned to available and upon a retrieval request a corresponding
indicate that this instance does not exist. error message shall be returned to indicate that this
instance does not exist.
This count represents a a non-negative integer, which This count represents a non-negative integer, which
may increase or decrease, but shall never exceed 2^64-1 may increase or decrease, but shall never exceed 2^64-1
(18446744073709551615 decimal), nor fall below 0. The (18446744073709551615 decimal), nor fall below 0. The
The value of a HCPerfCurrentCount object assumes its The value of an object with HCPerfCurrentCount syntax
maximum value whenever the underlying count exceeds assumes its maximum value whenever the underlying count
2^64-1. If the underlying count subsequently decreases exceeds 2^64-1. If the underlying count subsequently
below 2^64-1 (due, e.g., to a retroactive adjustment as a decreases below 2^64-1 (due, e.g., to a retroactive
result of entering or exiting unavailable time), then the adjustment as a result of entering or exiting unavailable
HCPerfCurrentCount object also decreases. time), then the object's value also decreases.
Note that this TC is not strictly supported in SMIv2, Note that this TC is not strictly supported in SMIv2,
because the 'always increasing' and 'counter wrap' because the 'always increasing' and 'counter wrap'
semantics associated with the Counter64 base type are not semantics associated with the Counter64 base type are not
preserved. It is possible that management applications preserved. It is possible that management applications
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-
solution, and may be deprecated as a long term solution is term solution, and may be deprecated as a long term
defined and deployed to replace it." solution is defined and deployed to replace it."
SYNTAX Counter64 SYNTAX Counter64
HCPerfIntervalCount ::= TEXTUAL-CONVENTION HCPerfIntervalCount ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter associated with a performance measurement in "A gauge associated with a performance measurement in
a previous 15 minute measurement interval. In the case a previous 15 minute measurement interval. In the case
where the agent has no valid data available for a where the agent has no valid data available for a
particular interval the corresponding object instance is particular interval, the corresponding object instance is
not available and upon a retrieval request a corresponding not available and upon a retrieval request a corresponding
error message shall be returned to indicate that this error message shall be returned to indicate that this
instance does not exist. instance does not exist.
In a system supporting a history of n intervals with Let X be an object with HCPerfIntervalCount syntax.
IntervalCount(1) and IntervalCount(n) the most and least Let Y be an object with HCPerfCurrentCount syntax.
recent intervals respectively, the following applies at Let Z be an object with HCPerfTotalCount syntax.
the end of a 15 minute interval: Then, In a system supporting a history of n intervals with
X(1) and X(n) the most and least recent intervals
respectively, the following applies at the end of a 15
minute interval:
- discard the value of IntervalCount(n) - discard the value of X(n)
- the value of IntervalCount(i) becomes that - the value of X(i) becomes that of X(i-1)
of IntervalCount(i-1) for n >= i > 1 for n >= i > 1
- the value of IntervalCount(1) becomes that - the value of X(1) becomes that of Y.
of CurrentCount
- the TotalCount, if supported, is adjusted.
This count represents a a non-negative integer, which - the value of Z, if supported, is adjusted.
This count represents a non-negative integer, which
may increase or decrease, but shall never exceed 2^64-1 may increase or decrease, but shall never exceed 2^64-1
(18446744073709551615 decimal), nor fall below 0. The (18446744073709551615 decimal), nor fall below 0. The
The value of a HCPerfIntervalCount object assumes its The value of an object with HCPerfIntervalCount syntax
maximum value whenever the underlying count exceeds assumes its maximum value whenever the underlying count
2^64-1. If the underlying count subsequently decreases exceeds 2^64-1. If the underlying count subsequently
below 2^64-1 (due, e.g., to a retroactive adjustment as a decreases below 2^64-1 (due, e.g., to a retroactive
result of entering or exiting unavailable time), then the adjustment as a result of entering or exiting unavailable
HCPerfIntervalCount object also decreases. time), then the value of the object also decreases.
Note that this TC is not strictly supported in SMIv2, Note that this TC is not strictly supported in SMIv2,
because the 'always increasing' and 'counter wrap' because the 'always increasing' and 'counter wrap'
semantics associated with the Counter64 base type are not semantics associated with the Counter64 base type are not
preserved. It is possible that management applications preserved. It is possible that management applications
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-
solution, and may be deprecated as a long term solution is term solution, and may be deprecated as a long term
defined and deployed to replace it." solution is defined and deployed to replace it."
SYNTAX Counter64 SYNTAX Counter64
HCPerfTotalCount ::= TEXTUAL-CONVENTION HCPerfTotalCount ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter associated with a performance measurements "A gauge representing the aggregate of previous valid 15
aggregating the previous valid 15 minute measurement minute measurement intervals. Intervals for which no
intervals. Intervals for which no valid data was valid data was available are not counted.
available are not counted.
This count represents a a non-negative integer, which This count represents a non-negative integer, which
may increase or decrease, but shall never exceed 2^64-1 may increase or decrease, but shall never exceed 2^64-1
(18446744073709551615 decimal), nor fall below 0. The (18446744073709551615 decimal), nor fall below 0. The
The value of a HCPerfTotalCount object assumes its The value of an object with HCPerfTotalCount syntax
maximum value whenever the underlying count exceeds assumes its maximum value whenever the underlying count
2^64-1. If the underlying count subsequently decreases exceeds 2^64-1. If the underlying count subsequently
below 2^64-1 (due, e.g., to a retroactive adjustment as a decreases below 2^64-1 (due, e.g., to a retroactive
result of entering or exiting unavailable time), then the adjustment as a result of entering or exiting unavailable
HCPerfTotalCount object also decreases. time), then the object's value also decreases.
Note that this TC is not strictly supported in SMIv2, Note that this TC is not strictly supported in SMIv2,
because the 'always increasing' and 'counter wrap' because the 'always increasing' and 'counter wrap'
semantics associated with the Counter64 base type are not semantics associated with the Counter64 base type are not
preserved. It is possible that management applications preserved. It is possible that management applications
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-
solution, and may be deprecated as a long term solution is term solution, and may be deprecated as a long term
defined and deployed to replace it." solution is defined and deployed to replace it."
SYNTAX Counter64 SYNTAX Counter64
END END
Informative References 4. Intellectual Property
[T1.231] American National Standard for Telecommunications - The IETF takes no position regarding the validity or scope of any
Digital Hierarchy - Layer 1 In-Service Digital intellectual property or other rights that might be claimed to
Transmission Performance Monitoring, ANSI T1.231-1997, pertain to the implementation or use of the technology described in
September 1997. this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances
of licenses to be made available, or the result of an attempt made
to obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification
can be obtained from the IETF Secretariat.
[RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification The IETF invites any interested party to bring to its attention any
of Management Information for TCP/IP-based Internets", copyrights, patents or patent applications, or other proprietary
STD 16, RFC 1155, May 1990. rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
[RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, 5. Normative References
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
STD 16, RFC 1212, March 1991. Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC1215] Rose, M., "A Convention for Defining Traps for use with [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
the SNMP", RFC 1215, March 1991. Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
"Introduction to Community-based SNMPv2", RFC 1901, Rose, M. and S. Waldbusser, "Conformance Statements for
January 1996. SMIv2", STD 58, RFC 2580, April 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 6. Informative References
"Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Transport Mappings for Version 2 of the Simple Network "Introduction and Applicability Statements for Internet-
Management Protocol (SNMPv2)", RFC 1906, January 1996. Standard Management Framework", RFC 3410, December 2002.
[T1.231] American National Standard for Telecommunications -
Digital Hierarchy - Layer 1 In-Service Digital
Transmission Performance Monitoring, ANSI T1.231-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 [RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC Performance History Based on 15 Minute Intervals", RFC
2493, January 1999. 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 [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
for the ADSL Lines", RFC 2662, August 1999.
[RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999.
[RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for Describing SNMP Management Frameworks",
RFC 2571, April 1999.
[RFC2572] Case, J., Harrington D., Presuhn R. and B. Wijnen,
"Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572, April
1999.
[RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999.
[RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999.
[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.,
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.
[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.
[VDSL-MIB] Ray, B. and R. Abbi, work in progress. [RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects
for High Bit-rate DSL - 2nd Generation (HDSL2) and
Security Considerations Single-Pair High-Speed Digital Subscriber Line (SHDSL)
Lines", RFC3276, May 2002.
This module does not define any management objects. Instead, it 7. Security Considerations
defines a set of textual conventions which may be used by other MIB
modules to define management objects.
Meaningful security considerations can only be written in the modules SNMP versions prior to SNMPv3 did not include adequate security.
that define management objects. Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) objects
which utilize the textual conventions defined in this MIB module.
IANA Considerations 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).
Prior to publication of this memo as an RFC, IANA is requested to Further, deployment of SNMP versions prior to SNMPv3 is NOT
make a suitable OBJECT IDENTIFIER assignment. RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
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.
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.
Intellectual Property Notice 9. Authors' Addresses
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
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 USA Huntsville, AL 35805
USA
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Fax: +1 256 726 9271 Fax: +1 256 726 9271
EMail: rray@pesa.com EMail: rray@pesa.com
Rajesh Abbi Rajesh Abbi
Alcatel USA Alcatel USA
2912 Wake Forest Road 2912 Wake Forest Road
Raleigh, NC 27609-7860 USA Raleigh, NC 27609-7860
USA
Phone: +1 919 850 6194 Phone: +1 919 850 6194
EMail: Rajesh.Abbi@alcatel.com EMail: Rajesh.Abbi@alcatel.com
Full Copyright Statement 10. Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). 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
included on all such copies and derivative works. However, this are 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
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
 End of changes. 

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