Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6

Danny Mayer <mayer@ntp.org> Mon, 26 November 2007 20:47 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 1IwkrI-0005JR-IK; Mon, 26 Nov 2007 15:47:12 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwkrH-0005JG-7m for dhcwg@ietf.org; Mon, 26 Nov 2007 15:47:11 -0500
Received: from exchdev.pega.com ([198.22.153.35] helo=exchdev.rpega.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IwkrG-0004fJ-Tl for dhcwg@ietf.org; Mon, 26 Nov 2007 15:47:11 -0500
Received: from [10.60.98.36] ([10.60.98.36]) by exchdev.rpega.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Nov 2007 15:47:04 -0500
Message-ID: <474B3023.2080303@ntp.org>
Date: Mon, 26 Nov 2007 15:44:19 -0500
From: Danny Mayer <mayer@ntp.org>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
References: <200711260505.lAQ55V01028000@drugs.dv.isc.org>
In-Reply-To: <200711260505.lAQ55V01028000@drugs.dv.isc.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Nov 2007 20:47:04.0658 (UTC) FILETIME=[80907B20:01C8306D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: ntpwg@lists.ntp.org, dhcwg@ietf.org, Mark Andrews <Mark_Andrews@isc.org>, "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

I'd like to apologize to Ted over this and thank Mark for his input. I
hadn't realized until Mark piped up with his response that these servers
were getting all of their information from upstream and therefore there
was always some sort of human at the end of the chain actively managing
this in the SOHO routers. I hadn't wanted to get into the details of how
DHCP servers worked but it was crucial for an understanding of the
configuration mechanism.

So I withdraw my objections to using IPv6 addresses in these options but
I strongly recommend a sentence or two be added to the Security section
to warn people about the amplifying effects of provisioning NTP server
addresses to clients in this way and their potential for DDOS attacks.

Danny

Mark Andrews wrote:
> 	Danny this really is a non-issue.
> 
> 	A SOHO DHCP server side will learn its values from the
> 	SOHO DHCP client side.  SOHO DHCP servers do this today
> 	for lots of values it returns to the SOHO network.
> 
> 	Today you have a check box on SOHO routers that says
> 		[ ] DNS servers learn from network.
> 	If it is not checked you get a dialog to fill in.
> 
> 	Tomorrow you will have a check box on SOHO routers that says
> 		[ ] NTP servers learn from network.
> 	If it's not checked you will get a dialog to fill in.
> 
> 	Similarly IPv6 PD requests will chain through multiple DHCP
> 	servers until you find one which will allocate the space requested.
> 
> 	Mark


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