----- Original Message ----- From: "Bhatia, Manav (Manav)" <[email protected]> To: "Acee Lindem" <[email protected]>; "Sam Hartman" <[email protected]> Cc: <[email protected]>; <[email protected]>; <[email protected]> Sent: Wednesday, February 02, 2011 3:53 AM
> Hi Acee, > > > While most modern routers have a clock with fine enough > > granularity that will never go backwards, it is typically > > not preserved across cold restarts. > > If one used a 64 bit sequence number (for the required precision) > > and had a relative clock that was never reset, it would fit the bill. > > One could store this value in a non volatile memory so that its also preserved across cold rebootd but I don't this would be an acceptable solution. Or would it be? SNMPv3 introduces a requirement for non-volatile memory in which to store snmpEngineID and snmpEngineBoots [RFC3411] in order to avoid the requirement for a real time clock. I do not know how strictly this requirement is being implemented. Tom Petch <snip> > > > Cheers, Manav > _______________________________________________ > OSPF mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/ospf _______________________________________________ OSPF mailing list [email protected] https://www.ietf.org/mailman/listinfo/ospf
