search

ietf-wg-ntp / draft-ietf-ntp-ntpv5-requirements

Other
1 stars 2 forks source link

Service availability #20

Closed fiestajetsam closed 1 year ago

fiestajetsam commented 1 year ago

Ulrich writes:

On " The protocol MUST have the capability for servers to notify clients that the service is unavailable": I think it should be mentioned that clients deliberately ignoring such signaling SHOULD (or MUST) be handled accordingly (still to be defined or at least suggested how to).

In addition to this there should be some text describing some suggestions on how this should be dealt with.

fiestajetsam commented 1 year ago

In thinking about this, I'm not sure there's any requirements we could add here to the protocol - if a source is sending a lot of incoming requests and is not (intentionally or otherwise) ignoring a KoD or something of that nature, as a host or a network operator your options are limited to implementing traffic management in firewall/routing and/or emailing noc@ on the other side. I don't see any other realistic options here. Further I don't think there's any more that could be included into a document because like in #39, this becomes more in the "deployment considerations" domain which I think is outside of scope of this I-D.