[dhcwg] Re: Renumbering DNS with stateless DHCPv6 - bug?

Iljitsch van Beijnum <iljitsch@muada.com> Thu, 13 November 2003 22:07 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23405 for <dhcwg-archive@odin.ietf.org>; Thu, 13 Nov 2003 17:07:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKPcL-0001sQ-0D for dhcwg-archive@odin.ietf.org; Thu, 13 Nov 2003 17:07:12 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hADM78Q9007189 for dhcwg-archive@odin.ietf.org; Thu, 13 Nov 2003 17:07:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKPcK-0001rK-5X for dhcwg-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 17:07:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23207 for <dhcwg-web-archive@ietf.org>; Thu, 13 Nov 2003 17:06:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKPcH-0006Hg-00 for dhcwg-web-archive@ietf.org; Thu, 13 Nov 2003 17:07:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKPcG-0006HZ-00 for dhcwg-web-archive@ietf.org; Thu, 13 Nov 2003 17:07:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKPcF-0001mL-UY; Thu, 13 Nov 2003 17:07:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKNik-0001E6-9G for dhcwg@optimus.ietf.org; Thu, 13 Nov 2003 15:05:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16301 for <dhcwg@ietf.org>; Thu, 13 Nov 2003 15:05:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKNie-00044M-00 for dhcwg@ietf.org; Thu, 13 Nov 2003 15:05:32 -0500
Received: from sequoia.muada.com ([213.156.1.123]) by ietf-mx with esmtp (Exim 4.12) id 1AKNid-00043i-00 for dhcwg@ietf.org; Thu, 13 Nov 2003 15:05:31 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123]) by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id hADK4ted060122; Thu, 13 Nov 2003 21:04:55 +0100 (CET) (envelope-from iljitsch@muada.com)
In-Reply-To: <20031113191145.GS3473@login.ecs.soton.ac.uk>
References: <20031113191145.GS3473@login.ecs.soton.ac.uk>
Mime-Version: 1.0 (Apple Message framework v606)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <AFC008FD-1614-11D8-8CC8-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org, dnsop@cafax.se
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Thu, 13 Nov 2003 14:05:11 -0600
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.606)
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Re: Renumbering DNS with stateless DHCPv6 - bug?
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On 13-nov-03, at 13:11, Tim Chown wrote:

> With DHCPv6 Light for DNS option configuration, how is the client told
> that DNS options have changed?

Operationally, you'd probably have to support these addresses forever. 
Not just because of DHCP issues but also because users tend to jot down 
dynamic stuff and then hardcode it. (For instance for hosts that don't 
support dynamic DNS discovery (which obviously are almost all of them 
today (in IPv6)).)

> One option for passing the new DNS options from the DHCPv6 Light server
> to the client is a multicast Reconfigure message.

Hm, I can already imagine the posters on the men's room at IETF 63: 
"whoever is sending "reconfigure DNS" multicast messages every second, 
quit it as the 1200 DHCPv6 requests per second are killing the wireless 
performance".

There are DoS issues here.


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