IETF Logo Mail Archive

RE: Node Req: Issue31: DHCPv6 text (ignore previous mails)

Ralph Droms <rdroms@cisco.com> Thu, 04 December 2003 16:45 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03983 for <ipv6-archive@odin.ietf.org>; Thu, 4 Dec 2003 11:45:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARwbI-0001Lm-P6 for ipv6-archive@odin.ietf.org; Thu, 04 Dec 2003 11:45:13 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB4GjCe7005183 for ipv6-archive@odin.ietf.org; Thu, 4 Dec 2003 11:45:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARwbI-0001LV-0G for ipv6-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 11:45:12 -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 LAA03943 for <ipv6-web-archive@ietf.org>; Thu, 4 Dec 2003 11:44:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ARwbG-0004Uk-00 for ipv6-web-archive@ietf.org; Thu, 04 Dec 2003 11:45:10 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ARwbG-0004Uh-00 for ipv6-web-archive@ietf.org; Thu, 04 Dec 2003 11:45:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARwa9-00018Q-UF; Thu, 04 Dec 2003 11:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARwZF-00017E-PQ for ipv6@optimus.ietf.org; Thu, 04 Dec 2003 11:43:05 -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 LAA03904 for <ipv6@ietf.org>; Thu, 4 Dec 2003 11:42:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ARwZE-0004Tn-00 for ipv6@ietf.org; Thu, 04 Dec 2003 11:43:04 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1ARwZE-0004Tk-00 for ipv6@ietf.org; Thu, 04 Dec 2003 11:43:04 -0500
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hB4GgUAt000945; Thu, 4 Dec 2003 08:42:30 -0800 (PST)
Received: from rdroms-w2k01.cisco.com ([161.44.65.206]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AEK59844; Thu, 4 Dec 2003 11:42:28 -0500 (EST)
Message-Id: <4.3.2.7.2.20031204113748.01e0c710@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 04 Dec 2003 11:42:24 -0500
To: Pekka Savola <pekkas@netcore.fi>
From: Ralph Droms <rdroms@cisco.com>
Subject: RE: Node Req: Issue31: DHCPv6 text (ignore previous mails)
Cc: john.loughney@nokia.com, narten@us.ibm.com, Bob.Hinden@nokia.com, ipv6@ietf.org
In-Reply-To: <Pine.LNX.4.44.0312041319340.3443-100000@netcore.fi>
References: <DADF50F5EC506B41A0F375ABEB320636D44B6B@esebe023.ntc.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: ipv6-admin@ietf.org
Errors-To: ipv6-admin@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Id: IP Version 6 Working Group (ipv6) <ipv6.ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>

No, there are not really two versions of DHCPv6 - all of the various message
exchanges and modes of operation are defined in RFC 3315.
draft-ietf-dhc-dhcpv6-stateless-02.txt is an aid to the implementation of
DHCP that provides other configuration information but not address assignment.

It might clarify the text a little to refer to "a node that uses DHCP for
address assignment" and "a node that uses DHCP to obtain other configuration
information"; I think references to "stateless DHCPv6" are confusing.

- Ralph

At 01:25 PM 12/4/2003 +0200, Pekka Savola wrote:
>[...]
>Also, there are basically two versions of "DHCP": the one specified in
>RFC3315, and the "stateless DHCP", in IESG review at the moment.  It
>is not clear to which you're referring to here.
>
>--
>Pekka Savola                 "You each name yourselves king, yet the
>Netcore Oy                    kingdom bleeds."
>Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>
>
>
>--------------------------------------------------------------------
>IETF IPv6 working group mailing list
>ipv6@ietf.org
>Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>--------------------------------------------------------------------


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email