Re: RFC1155 Timeticks hitting maximum value

Hi -

> From: "Gene Matusovsky" <[email protected]>
> To: "Jon Saperia" <[email protected]>
> Cc: <[email protected]>; "Randy Presuhn" <[email protected]>
> Sent: Thursday, June 24, 2010 12:00 PM
> Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
>
> Workarounds are possible, and can be done, but not everyone has development
> resources. With todays technology and higher capacity systems, the root of the
> issue can be addressed directly by extending RFC 1155/ 1902 Timeticks data type.

Not an option.  SMI rules do not allow this, for good reason - it would change the
on-the-wire representation.   See the ASN.1 in RFC 3416 for an explanation:
the Unsigned32 is tagged [APPLICATION 2], while Counter64 is tagged
[APPLICATION 6].

> This was done before with RFC 2863, when IfInOctets was updated to IfHCInOctets.

No, in that case a *new* object type was defined, because changing the syntax
of IfInOctets was not an option.  IfHCInOctets is a *different* object, not an "update"
to IfInOctets, even though their semantics are remarkably similar.

> Are there any existing SNMP workgroups or ongoing projects.
....

I'm not aware of any where this sort of change would be within scope.

Randy