Ira,
The Protocol document was changed in section 3.6 to make the example value
for clients that aren't using it be the constant 1, instead of 0,
so that its value is a legal value as agreed to align with the Job MIB and
the SNMP requirement not to use 0 as a table index value.
However, the ABNF fails to specify the syntax of the request-id token.
(0 or 1). It should be SIGNED-INTEGER, as all four octet integers are,
but with some restriction on the range to be 1 to 2**31-1.
Also I would think that section 3.6 should also include the range limits,
as has been done for other fields.
Also the Model document doesn't seem to mention the request-id at all,
that I could find. I'm not sure whether it should or not, since the
request-id is more of a protocol mechanism.
Thanks,
Tom
snip...