[dhcwg] DHCP-DHCPv6 Issues and IPv4 options drafts

Tim Chown <tjc@ecs.soton.ac.uk> Tue, 10 February 2004 22:35 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 RAA26530 for <dhcwg-archive@odin.ietf.org>; Tue, 10 Feb 2004 17:35:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqgTM-0001PE-H9 for dhcwg-archive@odin.ietf.org; Tue, 10 Feb 2004 17:35:16 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1AMZGCF005401 for dhcwg-archive@odin.ietf.org; Tue, 10 Feb 2004 17:35:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqgTM-0001P2-BV for dhcwg-web-archive@optimus.ietf.org; Tue, 10 Feb 2004 17:35:16 -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 RAA26455 for <dhcwg-web-archive@ietf.org>; Tue, 10 Feb 2004 17:35:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqgTJ-0001tq-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 17:35:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqgSL-0001kB-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 17:34:14 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AqgRN-0001Z6-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 17:33:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqgRB-0001D9-SK; Tue, 10 Feb 2004 17:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqgQy-0001Cf-SE for dhcwg@optimus.ietf.org; Tue, 10 Feb 2004 17:32:48 -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 RAA26161 for <dhcwg@ietf.org>; Tue, 10 Feb 2004 17:32:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqgQw-0001Si-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 17:32:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqgQ1-0001Iq-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 17:31:49 -0500
Received: from raven.ecs.soton.ac.uk ([152.78.70.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqgPH-00017P-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 17:31:03 -0500
Received: from pigeon.ecs.soton.ac.uk (pigeon [152.78.68.1]) by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id i1AMUCOr021157 for <dhcwg@ietf.org>; Tue, 10 Feb 2004 22:30:12 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 WAA00881 for <dhcwg@ietf.org>; Tue, 10 Feb 2004 22:30:08 GMT
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i1AMU7602826 for dhcwg@ietf.org; Tue, 10 Feb 2004 22:30:07 GMT
Date: Tue, 10 Feb 2004 22:30:07 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: dhcwg@ietf.org
Message-ID: <20040210223007.GA2626@login.ecs.soton.ac.uk>
Mail-Followup-To: dhcwg@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
Subject: [dhcwg] DHCP-DHCPv6 Issues and IPv4 options drafts
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

Hi,

These two drafts have now been published.   As they may not be copied to
the dhc list due to their personal status, their summaries are below.

The purpose of the drafts is to form a framework for discussion in Seoul,
where Stig Venaas will present the issues draft.   Both drafts have a short
slot on the agenda. 

The main options appear to be keeping the functionality separate, or adding
IPv4 information options to allow only DHCPv6 to be required for dual-stack
nodes.   In additional, some "administrative" considerations could/should be
made, e.g. whether or not to use a split name space (*.ipv6.foo.com) for 
early IPv6 deployment.


        Title           : IPv4 and IPv6 Dual-Stack Issues for DHCPv6
        Author(s)       : T. Chown
        Filename        : draft-chown-dhc-dual-stack-00.txt
        Pages           : 10
        Date            : 2004-2-10

   A node may have support for communications using IPv4 and/or IPv6
   protocols.  Such a node may wish to obtain IPv4 and/or IPv6
   configuration settings via the Dynamic Host Configuration Protocol
   (DHCP).   The original version of DHCP [1] designed for IPv4 has now
   been complemented by a new DHCPv6 [4] for IPv6. This document
   describes issues identified with dual IP version DHCP interactions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-chown-dhc-dual-stack-00.txt


        Title           : DHCPv6 IPv4 Information Options
        Author(s)       : C. Cadar
        Filename        : draft-cadar-dhc-dhcpv6-v4options-00.txt
        Pages           : 21
        Date            : 2004-2-10

   To ease the management of a site, the Dynamic Host Configuration
   Protocol (DHCP) is often used. DHCP exists both for the Internet
   Protocol Version 4 (DHCPv4 for IPv4) and Version 6 (DHCPv6 for IPv6).
   To avoid possible pitfalls that occur if both DHCP versions are used
   and to avoid redundancy, IPv4 Information Options may be transmitted
   using DHCPv6 as described in this document. In dual-stack IPv4/IPv6
   scenarios that employ DHCPv6, DHCPv4 can be completely replaced by
   using the DHCPv6 IPv4 Information Options.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cadar-dhc-dhcpv6-v4options-00.txt


Tim

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