[ntpwg] KoD 'backoff' BCP/direction

Greg Dowd GDowd at symmetricom.com
Wed May 28 23:10:59 UTC 2008


The server reply has poll field.  It could suggest a maximum poll rate?


Greg Dowd
gdowd at symmetricom dot com (antispam format)
Symmetricom, Inc.
www.symmetricom.com
"Everything should be made as simple as possible, but no simpler" Albert
Einstein

-----Original Message-----
From: ntpwg-bounces+gdowd=symmetricom.com at lists.ntp.org
[mailto:ntpwg-bounces+gdowd=symmetricom.com at lists.ntp.org] On Behalf Of
Harlan Stenn
Sent: Wednesday, May 28, 2008 4:00 PM
To: ntpwg at ntp.org
Subject: [ntpwg] KoD 'backoff' BCP/direction

The draft says:

   a.  For kiss codes: DENY, RSTR the client MUST demobilize any
       associations to that server and stop sending packets to that
       server;

   b.  For kiss code: RATE the client MUST immediately reduce its
       polling interval to that server and continue to reduce it each
       time it receives a RATE kiss code.

>From my POV this is almost helpful.

For case (a), for what duration SHOULD the client demobilize and stop
sending packets to that server?

For case (b), are there any recommendations on how much the client
SHOULD reduce the rate at which it is polling the server?

In case (b), do we mean 'polling rate' (or frequency) instead of
'polling interval'?

Is there an easy way the server could 'offer a suggestion' in either of
these cases?  What are the costs/benefits to having the server offer
ideas on these rate limits instead of relying solely on the client?

--
Harlan Stenn <stenn at ntp.org>
http://ntpforum.isc.org  - be a member!
_______________________________________________
ntpwg mailing list
ntpwg at lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


More information about the ntpwg mailing list