Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Options for DHCPv6

Brian Utterback <Brian.Utterback@Sun.COM> Sun, 25 November 2007 12:50 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwGvy-0004Z4-Jk; Sun, 25 Nov 2007 07:50:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwGvx-0004VE-LE for dhcwg@ietf.org; Sun, 25 Nov 2007 07:50:01 -0500
Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwGvt-000252-HX for dhcwg@ietf.org; Sun, 25 Nov 2007 07:50:01 -0500
Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id lAPCnvit009954 for <dhcwg@ietf.org>; Sun, 25 Nov 2007 12:49:57 GMT
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JS200F01BFOFM00@mail-amer.sun.com> (original mail from Brian.Utterback@Sun.COM) for dhcwg@ietf.org; Sun, 25 Nov 2007 05:49:57 -0700 (MST)
Received: from [192.168.1.5] ([71.168.64.220]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JS20006KBN71680@mail-amer.sun.com>; Sun, 25 Nov 2007 05:49:56 -0700 (MST)
Date: Sun, 25 Nov 2007 07:49:55 -0500
From: Brian Utterback <Brian.Utterback@Sun.COM>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Options for DHCPv6
In-reply-to: <4748F4C4.1090407@ntp.org>
To: Danny Mayer <mayer@ntp.org>
Message-id: <47496F73.8040206@sun.com>
MIME-version: 1.0
Content-type: text/plain; format="flowed"; charset="ISO-8859-1"
Content-transfer-encoding: 7bit
References: <20071121052610.DD3EF39E3F@mail1.ntp.org> <4748DAB1.2030506@ntp.org> <6EDC6595-CD66-490F-90FD-A730E4BF3360@fugue.com> <4748F4C4.1090407@ntp.org>
User-Agent: Thunderbird 2.0.0.6 (X11/20071009)
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <mellon@fugue.com>, "Richard Gayraud (rgayraud)" <rgayraud@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Danny Mayer wrote:
> Ted Lemon wrote:
>   
>
>>   The problem you're afraid will happen is
>> not going to happen.
>>     
>
> You're too late. It already has. We are already in the situation that we
> need to take defensive measures against existing errant NTP clients.
>
>   

No it hasn't. AFAIK, there has not been a case of multitudes of clients 
that received NTP server
IP addresses from DHCP spamming servers abusively for extended periods 
of time. My gut feel
is that Ted is correct and that this is not likely to be a problem.

However, the fact that we have had other situations develop into just 
such problems means
that examining the proposal for potential abuse scenarios is worthwhile. 
Before we start
looking for a compromise solution, perhaps we should look more closely 
at the problem.

For instance, I don't see the problem as being any worse than an 
ntp.conf file that has
the server given by an IP address. If you are going to restrict DHCP, 
perhaps we
should consider not allowing IP addresses in the ntp.conf file. If you 
think that
is absurd, then perhaps the DHCP restriction is absurd as well. Or 
perhaps not.

Brian Utterback

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg