[dhcwg] Re: Last Call: 'A Guide to Implementing Stateless DHCPv6 Service' to Proposed Standard

Tim Chown <tjc@ecs.soton.ac.uk> Fri, 14 November 2003 16:07 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17642 for <dhcwg-archive@odin.ietf.org>; Fri, 14 Nov 2003 11:07:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKgTa-0002Af-4m for dhcwg-archive@odin.ietf.org; Fri, 14 Nov 2003 11:07:14 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEG7Dn2008339 for dhcwg-archive@odin.ietf.org; Fri, 14 Nov 2003 11:07:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKgTZ-0002AQ-P6 for dhcwg-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 11:07:13 -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 LAA17595 for <dhcwg-web-archive@ietf.org>; Fri, 14 Nov 2003 11:06:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKgTX-0007n7-00 for dhcwg-web-archive@ietf.org; Fri, 14 Nov 2003 11:07:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKgTW-0007n4-00 for dhcwg-web-archive@ietf.org; Fri, 14 Nov 2003 11:07:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKgTP-00024F-8T; Fri, 14 Nov 2003 11: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 1AKgTE-0001yW-Az for dhcwg@optimus.ietf.org; Fri, 14 Nov 2003 11:06:52 -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 LAA17576; Fri, 14 Nov 2003 11:06:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKgTB-0007me-00; Fri, 14 Nov 2003 11:06:49 -0500
Received: from raven.ecs.soton.ac.uk ([152.78.70.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKgTA-0007mb-00; Fri, 14 Nov 2003 11:06:49 -0500
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1]) by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id QAA17437; Fri, 14 Nov 2003 16:06:46 GMT
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162]) by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id QAA18201; Fri, 14 Nov 2003 16:06:46 GMT
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.11.6/8.11.6) id hAEG6j419983; Fri, 14 Nov 2003 16:06:46 GMT
Date: Fri, 14 Nov 2003 16:06:45 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: dhcwg@ietf.org, iesg@ietf.org
Message-ID: <20031114160645.GE19013@login.ecs.soton.ac.uk>
Mail-Followup-To: dhcwg@ietf.org, iesg@ietf.org
References: <E1AFLj4-0003Pq-Or@asgard.ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E1AFLj4-0003Pq-Or@asgard.ietf.org>
User-Agent: Mutt/1.4i
Subject: [dhcwg] Re: Last Call: 'A Guide to Implementing Stateless DHCPv6 Service' to Proposed Standard
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>

On Thu, Oct 30, 2003 at 05:57:10PM -0500, The IESG wrote:
> The IESG has received a request from the Dynamic Host Configuration WG to 
> consider the following document:
> 
> - 'A Guide to Implementing Stateless DHCPv6 Service'
>    <draft-ietf-dhc-dhcpv6-stateless-01.txt> as a Proposed Standard

Wrt recent exchanges on the dhcwg list, are we concerned that there is
no mechanism in stateless DHCPv6 for the DHCPv6 server to inform DHCPv6
clients of renumbering events to DNS or NTP servers (for example) where
the clients are using stateless autocinfiguration (RFC2462) for address
assignment and DHCPv6 (stateless) for options (DNS, NTP, ...).

If the clients use DHCPv6 for address assignment, the DHCPv6 server could
use its IP lease information to unicast the Reconfigure message, but in
a stateless-only DHCPv6 server this client information would presumably
not be available.

The current solution seems to be that clients must poll for changes, which
is not ideal, but which may suffice in some cases.

Tim

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