RE: guidelines section 4.6.1.2 (one hour rule)

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

> OK, here is some proposed text.  If accepted, it would be inserted
> just before the next-to-last paragraph of section 4.6.1.2:
> 
>    RFC 2578 Section 7.1.10 places a requirement on "standard" MIB
>    modules that the Counter64 type may be used only if the information
>    being modeled would wrap in less than one hour if the Counter32 type
>    was used instead.  Now that SNMPv3 is an Internet Standard and SNMPv1
>    is Historic (see [RFC3410]) there is no reason to continue enforcing
>    this restriction.  Henceforth "standard" MIB modules MAY use the
>    Counter64 type when it makes sense to do so, and MUST use Counter64
>    if the information being modeled would wrap in less than one hour if
>    the Counter32 type was used instead.
> 
> If I don't hear any objections, I'll put this in the next version of
> the document.
> 

I am OK with that.... but...
RFC3410 only makes the recommendation to make v1 historic and v3 STD.
The actual act is documented elsewhere, namely in the RFC-Editor
Database. Now I can live with it... but maybe better
instead of 

   (see [RFC3410])
write
   (see explanation in [RFC3410], see http://www.rfc-editor.org/rfcxx00.html for RFC status)


> //cmh
> 
>