Re: FYI - 4 week IETF Last Call on endpoint MIB

[Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>]

>>>>> itojun  writes:

itojun> Does scope identifier portion needed to be 4 digits?

The `4d' means that you take 4 bytes from the current position in the
OCTET STRING value and you render it as a decimal number. The SMIv2
says that leading 0s are suppressed. (Well, it says this for INTEGER
base types - but I guess that this also applies to OCTET STRING base
types by interpretation.)

itojun> From C structure definition in RFC2553, it is declared as
itojun> being 32bit unsigned integer.  Not sure if many uses higher
itojun> bits, but some may use them.

There is no format specifier for unsigned numbers in the SMIv2. The
text for the `d' specifier on primitive OCTET STRING types just says
decimal and is silent about the sign. So one could argue that `d' is
somewhat ambiguous. Since there is no format specifier for unsigned
numbers in SMIv2, using `d' is the best we can do.

[I expect that the NMRG will pick up this issue, probably introducing
 a `u' specifier in the next revision of the SMIng specification.]

/js

-- 
Juergen Schoenwaelder      Technical University Braunschweig
<schoenw@ibr.cs.tu-bs.de>  Dept. Operating Systems & Computer Networks
Phone: +49 531 391 3289    Bueltenweg 74/75, 38106 Braunschweig, Germany
Fax:   +49 531 391 5936    <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>