1 HCNUM-TC DEFINITIONS ::= BEGIN
4 MODULE-IDENTITY, mib-2, Counter64
9 hcnumTC MODULE-IDENTITY
10 LAST-UPDATED "200006080000Z"
12 ORGANIZATION "IETF OPS Area"
14 " E-mail: mibs@ops.ietf.org
15 Subscribe: majordomo@psg.com
16 with msg body: subscribe mibs
21 San Jose, CA 95134 USA
28 San Jose, CA 95134 USA
35 2141 North First Street
36 San Jose, California 95131 USA
40 "A MIB module containing textual conventions
41 for high capacity data types. This module
42 addresses an immediate need for data types not directly
43 supported in the SMIv2. This short-term solution
44 is meant to be deprecated as a long-term solution
46 REVISION "200006080000Z"
48 "Initial Version of the High Capacity Numbers
49 MIB module, published as RFC 2856."
52 CounterBasedGauge64 ::= TEXTUAL-CONVENTION
55 "The CounterBasedGauge64 type represents a non-negative
56 integer, which may increase or decrease, but shall never
57 exceed a maximum value, nor fall below a minimum value. The
58 maximum value can not be greater than 2^64-1
59 (18446744073709551615 decimal), and the minimum value can
61 not be smaller than 0. The value of a CounterBasedGauge64
62 has its maximum value whenever the information being modeled
63 is greater than or equal to its maximum value, and has its
64 minimum value whenever the information being modeled is
65 smaller than or equal to its minimum value. If the
66 information being modeled subsequently decreases below
67 (increases above) the maximum (minimum) value, the
68 CounterBasedGauge64 also decreases (increases).
70 Note that this TC is not strictly supported in SMIv2,
71 because the 'always increasing' and 'counter wrap' semantics
72 associated with the Counter64 base type are not preserved.
73 It is possible that management applications which rely
74 solely upon the (Counter64) ASN.1 tag to determine object
75 semantics will mistakenly operate upon objects of this type
76 as they would for Counter64 objects.
78 This textual convention represents a limited and short-term
79 solution, and may be deprecated as a long term solution is
80 defined and deployed to replace it."
83 ZeroBasedCounter64 ::= TEXTUAL-CONVENTION
86 "This TC describes an object which counts events with the
87 following semantics: objects of this type will be set to
88 zero(0) on creation and will thereafter count appropriate
89 events, wrapping back to zero(0) when the value 2^64 is
92 Provided that an application discovers the new object within
93 the minimum time to wrap it can use the initial value as a
94 delta since it last polled the table of which this object is
95 part. It is important for a management station to be aware
96 of this minimum time and the actual time between polls, and
97 to discard data if the actual time is too long or there is
98 no defined minimum time.
100 Typically this TC is used in tables where the INDEX space is
101 constantly changing and/or the TimeFilter mechanism is in
104 Note that this textual convention does not retain all the
105 semantics of the Counter64 base type. Specifically, a
106 Counter64 has an arbitrary initial value, but objects
107 defined with this TC are required to start at the value
109 zero. This behavior is not likely to have any adverse
110 effects on management applications which are expecting
113 This textual convention represents a limited and short-term
114 solution, and may be deprecated as a long term solution is
115 defined and deployed to replace it."