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

[TS Glassey]

----- Original Message ----- 
From: "Brian Utterback" <Brian.Utterback at Sun.COM>
To: "Richard Gayraud (rgayraud)" <rgayraud at cisco.com>
Cc: "Danny Mayer" <mayer at ntp.org>; "Ralph Droms (rdroms)" 
<rdroms at cisco.com>; "Alain Durand" <alain_durand at cable.comcast.com>; "NTP 
Working Group" <ntpwg at lists.ntp.isc.org>; "MORAND Lionel RD-CORE-ISS" 
<lionel.morand at orange-ftgroup.com>; "DHC WG" <dhcwg at ietf.org>
Sent: Monday, December 10, 2007 4:49 AM
Subject: Re: [ntpwg] [dhcwg] NTP option: IP address and/or FQDN


> Richard Gayraud (rgayraud) wrote:
>> Hello Alain,
>>
>> This is not really different, but the impact of it will be less
>> important:
>>
>>   - If an hardcoded NTP IP address is shipped within a SOHO thing,
>>     (as it happened in the past), then this IP address is dead,
>>     for good. Not usable anymore. Also, I suspect routers on the
>>     path to this subnet are impacted, unless global internet
>>     routing tables are updated to drop this traffic upstream.
>>
> To elaborate, not only is the IP address forever dead, the bandwidth
> continues to be consumed.

You mean like what the DLink devices did to Poul-Henning and my server's? We 
formally moved the San Jose NIST Server to a new ISP to address this.

> I suspect that if we see many more such situations, there will have to
> be a mechanism
> installed in the Internet routers like the certificate revocation
> protocol in PKI. A way to
> tell all routers everywhere that certain IP addresses are never to be
> forwarded.
>
> Brian Utterback
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.org
> https://lists.ntp.org/mailman/listinfo/ntpwg