|
Yep, but as far as I can tell, in all cases it is used (in
rfc2564 at least) it is used
for read-only objects. And that was/is the limitation that
RFC4181 has put on
this method. And IEEE 802.1 want to have a read-write
Unsigned64.
I am not sure I understand why we cannot allow read-write if
we state
that the Counter64 semantics are not applicable. Dos anyone
remember?
Bert
----- Original Message -----
Sent: Thursday, March 26, 2009 11:04
PM
Subject: Re: [MIB-DOCTORS] How to do an
"Unsigned64" data type...
On Fri, Mar 27, 2009 at 03:07:56AM +0100, Bert Wijnen (IETF)
wrote:
> RFC4181 may be helpfull states:
[...]
> But since this type of solution does not allow for read-write,
I
> wonder how we can help
The APPICATION-MIB (RFC2564) has this
TC:
Unsigned64TC ::= TEXTUAL-CONVENTION
STATUS
current
DESCRIPTION
"A non-negative
64-bit bit integer, without
counter
semantics."
SYNTAX Counter64
This work predates
the RFC4181 definition.
/js
--
Juergen
Schoenwaelder
Jacobs University Bremen gGmbH
Phone: +49 421 200
3587 Campus Ring 1, 28759
Bremen, Germany
Fax: +49 421 200
3103 <http://www.jacobs-university.de/>
|