Hello,
I believe that SndNxt should be an unsigned 32 quantity, but currently
tcp-kis.txt lists it as an Integer32 which according to RFC 1902 is a signed
32 bit quantity:
The Integer32 type represents integer-valued information between -2^31 and
2^31-1 inclusive (-2147483648 to 2147483647 decimal). This type is
indistinguishable from the INTEGER type. Both the INTEGER and Integer32
types may be sub-typed to be more constrained than the Integer32 type.
Other variables that refer to sequence numbers such as SndUna and SndMax are
of type Counter32. Which is defined in RFC 1902 as:
The Counter32 type represents a non-negative integer which monotonically
increases until it reaches a maximum value of 2^32-1 (4294967295 decimal),
when it wraps around and starts increasing again from zero.
That sounds more like a sequence number to me.
Am I missing something?
Incidentially I ran into this working on a Python program to export Web100
data to into our streaming data framework -- I couldn't pack SndNxt into an
Integer32. As part of this effort I ended up writing a simple script that
generates a Python module that has a hash with information about all the
variables in the Web100 MIB. If there is interest in this code I'd be happy
to share.
Thanks,
Jon
--
Jon M. Dugan <jdugan@xxxxxxxxxxxxx>
Senior Network Engineer, Network Research, NCSA
_______________________________________________
Discussion mailing list
Discussion@xxxxxxxxxx
http://internal.web100.org/mailman/listinfo/discussion
|