Fwd: [ntpwg] KISS codes
Rob Seaman
seaman at noao.edu
Mon Jul 9 10:19:07 PDT 2007
Howdy,
The NTP WG is tying up the loose ends for the next version of NTP.
There's an interesting discussion ongoing about KoD packets for NTP:
https://lists.ntp.org/pipermail/ntpwg/2007-July/thread.html
May be pertinent to VOEvent as our customer base grows and we face
similar problems with kamikazi klients.
Rob
------
Begin forwarded message:
> From: Danny Mayer <mayer at gis.net>
> Date: June 26, 2007 4:52:13 AM MST
> To: NTP Working Group <ntpwg at lists.ntp.isc.org>
> Subject: [ntpwg] KISS codes
> Reply-To: mayer at gis.net
>
> Noone has commented on my recommendations for the KISS codes so I'm
> sending it back out again. This is much more important than the
> discussion on refid.
>
> 4) P24. Section 7.4 last sentence:
> Other than
> displaying the kiss code, KoD packets have no protocol significance
> and are discarded after inspection.
>
> I'd like to see recipients of KISS codes take actions dependent on the
> receipt of some of the codes. Practical experience has shown that the
> operators of public servers need to be able to assert more control
> over
> the clients that contact their servers. I'd like to therefore change
> this sentence to read as follows:
>
> Recipients of kiss codes MUST inspect them and in the following
> cases
> take these actions:
> 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.
> c) Other than the above conditions, KoD packets have no protocol
> significance and are discarded after inspection.
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/voevent/attachments/20070709/f7e02eb3/attachment-0001.html>
More information about the voevent
mailing list