Hi WG, the reboot session id as defined in -sign-12 has potential for implementations errors. I think is not a really big issue, but I would like to at least make sure everybody is aware of it.
The range for reboot session id is defined to be 0..999999999. This is beyond the scope of unsigned 32 bit int, which is 0..4294967295. I assume that this bears the risk that some implementors do not realize that they need to apply 64 bit arithmetics, which means that some of them may need to write the necessary code to support this. I guess this is the reason why the reboot id has been latched the the *signed* 32 bit integer value in SNMPv3 (RFC 2574). There, it is in the range of 0..2147483647. I am not sure if we really need a that large reboot session id, if it is worth the potential trouble. I propose to limit the range to 0..4294967295 OR mention the need for 64 bit arithmetic prominently where the reboot id is defined (so it can't simply be overlooked). Rainer
