[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC 3576bis discussion at IETF 68

Anyway, if we're discussing Event-Timestamp in the context of
retransmissions, it doesn't really matter what happens to the NAS
clock when it reboots.


On 3/21/07, Avi Lior <avi@bridgewatersystems.com> wrote:




I wonder how much a problem this really is.

 It should get a time from NNTP at bootup right?

And even if the NAS had a clock drift issue, surely it wouldnt be longer
then the time it took to reboot and start the RADIUS server.


Avi Lior Office: +1 613 591-9104 x 6417 Cell : +1 613 796-4183


 ________________________________
 From: Alan DeKok
Sent: Wed 3/21/2007 7:50 AM
To: Bernard Aboba; radext mailing list
Subject: Re: RFC 3576bis discussion at IETF 68


Bernard Aboba wrote:
> Also, it was pointed out that Event-Timestamp does not require
> synchronized clocks, only for the RADIUS server to remember the last
> value for a given NAS, and to make sure that it is monotonically
> increasing.

 And when the NAS reboots, and loses its time?

 I'm not sure how to address that.

 Alan DeKok.
--
 http://deployingradius.com - The web site of the book
 http://deployingradius.com/blog/ - The blog

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>




--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>