IETF Logo Mail Archive

Re: [dhcwg] Renumbering Requirements for Stateless DHCPv6

Ralph Droms <rdroms@cisco.com> Tue, 10 February 2004 22:03 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23018 for <dhcwg-archive@odin.ietf.org>; Tue, 10 Feb 2004 17:03:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqfyV-0006IA-03 for dhcwg-archive@odin.ietf.org; Tue, 10 Feb 2004 17:03:23 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1AM3Mbh024182 for dhcwg-archive@odin.ietf.org; Tue, 10 Feb 2004 17:03:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqfyU-0006Hx-Rq for dhcwg-web-archive@optimus.ietf.org; Tue, 10 Feb 2004 17:03:22 -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 RAA22971 for <dhcwg-web-archive@ietf.org>; Tue, 10 Feb 2004 17:03:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqfyS-0004PB-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 17:03:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aqfws-00043a-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 17:01:43 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AqfvU-0003sT-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 17:00:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqfvH-0005xb-Hu; Tue, 10 Feb 2004 17:00:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aqfuc-0005ns-Qj for dhcwg@optimus.ietf.org; Tue, 10 Feb 2004 16:59:22 -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 QAA22593 for <dhcwg@ietf.org>; Tue, 10 Feb 2004 16:59:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aqfua-0003l7-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 16:59:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aqftx-0003cZ-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 16:58:41 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1Aqfsu-0003IZ-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 16:57:36 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 10 Feb 2004 14:05:12 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i1ALv4u5024960; Tue, 10 Feb 2004 13:57:04 -0800 (PST)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-1-31.cisco.com [10.86.240.31]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AFY83549; Tue, 10 Feb 2004 16:57:02 -0500 (EST)
Message-Id: <4.3.2.7.2.20040210164055.01fcc2e0@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 10 Feb 2004 16:56:59 -0500
To: Tim Chown <tjc@ecs.soton.ac.uk>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Renumbering Requirements for Stateless DHCPv6
Cc: dhcwg@ietf.org
In-Reply-To: <20040210134549.GC15972@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Tim - I think it would be useful to add a section ("Considerations in
choosing a solution") that lists some of the issues you hint at in section
5, "Solution space".  Here are some candidate considerations:

* must support planned renumbering; desirable to support unplanned renumbering
* security; e.g., avoid DOS attacks mounted through Reconfigure messages
   sent from attacker
* must update options even if network is not renumbered
* desirable to maintain "stateless" property; i.e., no per-client state kept
   in the server

I agree with Bernie's observation that it would be good to add text (already
in RFC 3315 for stateful DHCPv6) specifying conditions under which client
should send an Information-request, such as reconnection to a link.

Another possible solution would be to redefine the semantics of the 'O' flag
in RAs, so toggling the 'O' flag would trigger clients to send an
Information-request message.

Nits:

The current citation for stateless DHCPv6 is "Stateless DHCP Service for
IPv6", draft-ietf-dhc-dhcpv6-stateless-04.txt, January 2004.  (this draft is
currently in the RFC Editor pub queue)

The current citation for the renumbering procedure draft is "Procedures for
Renumbering an IPv6 Network without a Flag Day",
draft-ietf-v6ops-renumbering-procedure-00.txt, February 2004.



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

v2.23.0 | Report a Bug | By Email