smilint output for ./HCNUM-TC

Messages:

HCNUM-TC

   1: -- extracted from rfc2856.txt
   2: -- at Tue Jun 20 07:07:37 2000

  53: 
  54:    CounterBasedGauge64 ::= TEXTUAL-CONVENTION

  55:      STATUS       current
  56:      DESCRIPTION
  57:            "The CounterBasedGauge64 type represents a non-negative
  58:            integer, which may increase or decrease, but shall never
  59:            exceed a maximum value, nor fall below a minimum value. The
  60:            maximum value can not be greater than 2^64-1
  61:            (18446744073709551615 decimal), and the minimum value can
  62:            not be smaller than 0.  The value of a CounterBasedGauge64
  63:            has its maximum value whenever the information being modeled
  64:            is greater than or equal to its maximum value, and has its
  65:            minimum value whenever the information being modeled is
  66:            smaller than or equal to its minimum value.  If the
  67:            information being modeled subsequently decreases below
  68:            (increases above) the maximum (minimum) value, the
  69:            CounterBasedGauge64 also decreases (increases).
  70: 
  71:            Note that this TC is not strictly supported in SMIv2,
  72:            because the 'always increasing' and 'counter wrap' semantics
  73:            associated with the Counter64 base type are not preserved.
  74:            It is possible that management applications which rely
  75:            solely upon the (Counter64) ASN.1 tag to determine object
  76:            semantics will mistakenly operate upon objects of this type
  77:            as they would for Counter64 objects.
  78: 
  79:            This textual convention represents a limited and short-term
  80:            solution, and may be deprecated as a long term solution is
  81:            defined and deployed to replace it."
  82:      SYNTAX Counter64
  83: 
  84: 
  85:    ZeroBasedCounter64 ::= TEXTUAL-CONVENTION

  86:      STATUS current
  87:      DESCRIPTION
  88:            "This TC describes an object which counts events with the
  89:            following semantics: objects of this type will be set to
  90:            zero(0) on creation and will thereafter count appropriate
  91:            events, wrapping back to zero(0) when the value 2^64 is
  92:            reached.
  93: 
  94:            Provided that an application discovers the new object within
  95:            the minimum time to wrap it can use the initial value as a
  96:            delta since it last polled the table of which this object is
  97:            part.  It is important for a management station to be aware
  98:            of this minimum time and the actual time between polls, and
  99:            to discard data if the actual time is too long or there is
 100:            no defined minimum time.
 101: 
 102:            Typically this TC is used in tables where the INDEX space is
 103:            constantly changing and/or the TimeFilter mechanism is in
 104:            use.
 105: 
 106:            Note that this textual convention does not retain all the
 107:            semantics of the Counter64 base type. Specifically, a
 108:            Counter64 has an arbitrary initial value, but objects
 109:            defined with this TC are required to start at the value
 110:            zero.  This behavior is not likely to have any adverse
 111:            effects on management applications which are expecting
 112:            Counter64 semantics.
 113: 
 114:            This textual convention represents a limited and short-term
 115:            solution, and may be deprecated as a long term solution is
 116:            defined and deployed to replace it."
 117:      SYNTAX Counter64
 118: 
 119:    END

 120: 
 121: -- 
 122: --    Copyright (C) The Internet Society (2000).  All Rights Reserved.
 123: -- 
 124: --    This document and translations of it may be copied and furnished to
 125: --    others, and derivative works that comment on or otherwise explain it
 126: --    or assist in its implementation may be prepared, copied, published
 127: --    and distributed, in whole or in part, without restriction of any
 128: --    kind, provided that the above copyright notice and this paragraph are
 129: --    included on all such copies and derivative works.  However, this
 130: --    document itself may not be modified in any way, such as by removing
 131: --    the copyright notice or references to the Internet Society or other
 132: --    Internet organizations, except as needed for the purpose of
 133: --    developing Internet standards in which case the procedures for
 134: --    copyrights defined in the Internet Standards process must be
 135: --    followed, or as required to translate it into languages other than
 136: --    English.
 137: -- 
 138: --    The limited permissions granted above are perpetual and will not be
 139: --    revoked by the Internet Society or its successors or assigns.
 140: -- 
 141: --    This document and the information contained herein is provided on an
 142: --    "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
 143: --    TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
 144: --    BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
 145: --    HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
 146: --    MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 147: -- 
 148: