[ntpwg] [dhcwg] NTP option: IP address and/or FQDN

[Harlan Stenn]

Todd,

> Boy is this commentary going to make me unpopular...  but the key to this 
> problem isn't technology - its the License. The real failing in this matter 
> is that the NTP License allows people to mis-use NTP  and to do whatever 
> they want in hard coding the addresses into the product and based on the 
> existing license and the modified license created by the IETF there never 
> will be anyway to control the mis-use of NTP.
> 
> By the way - as I noted, the IETF's "Any and All" uses model further creates 
> this same problem by making those that misuse of the protocol still within 
> their licensing models so while it's nice that the WG is worried about 
> bad-NTP users or vendor's who do things that damage those of us operating 
> public access NIST servers.

I think in some ways you have a great point here.

And as proof of concept, I invite you to show how well this will work by
using these very same techiniques to solve something like the spam,
phishing, or malware problems.  I won't ask for a "finish-line" solution
(ie, "At 200902281234, the last piece of spam email was sent", but if
you can get that race actually started then I'll have much more
confidence that this will work.

And just to ask, what are some of the 2nd and 3rd order effects of your
proposal? I'm talking holistically here.  Like "the wall" in a General
Systems Theory analysis.

H