RE: [dhcwg] Stateless DHCPv6 service

"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Wed, 09 April 2003 02:18 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12368 for <dhcwg-archive@odin.ietf.org>; Tue, 8 Apr 2003 22:18:54 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h392Nq421705 for dhcwg-archive@odin.ietf.org; Tue, 8 Apr 2003 22:23:52 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h392Nq821702 for <dhcwg-web-archive@optimus.ietf.org>; Tue, 8 Apr 2003 22:23:52 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12348 for <dhcwg-web-archive@ietf.org>; Tue, 8 Apr 2003 22:18:21 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h392Id821491; Tue, 8 Apr 2003 22:18:39 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h392FR821373 for <dhcwg@optimus.ietf.org>; Tue, 8 Apr 2003 22:15:27 -0400
Received: from imr1.ericy.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11990 for <dhcwg@ietf.org>; Tue, 8 Apr 2003 22:09:57 -0400 (EDT)
Received: from mr5.exu.ericsson.se (mr5u3.ericy.com [208.237.135.124]) by imr1.ericy.com (8.12.9/8.12.9) with ESMTP id h392CTqj008354; Tue, 8 Apr 2003 21:12:29 -0500 (CDT)
Received: from eamrcnt761.exu.ericsson.se (eamrcnt761.exu.ericsson.se [138.85.133.39]) by mr5.exu.ericsson.se (8.12.9/8.12.9) with ESMTP id h392CSqp006673; Tue, 8 Apr 2003 21:12:29 -0500 (CDT)
Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2656.59) id <W7YA0WHY>; Tue, 8 Apr 2003 21:12:29 -0500
Message-ID: <A1DDC8E21094D511821C00805F6F706B06F6C015@eamrcnt715.exu.ericsson.se>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] Stateless DHCPv6 service
Date: Tue, 08 Apr 2003 21:10:34 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2FE3D.346EE25C"
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>

Ralph:

The document looks very good. Here are some corrections & nits for you:

In 1. Introduction, "through some other mechanism" ... other than what? [DHCP].

In 2. Terminology, add a "[1]" after "DHCP specification"?

In 5. Implementation of Stateless DHCP, 2nd paragraph, there is no such thing as
a "DUID Option". Replace with Client Identifier Option.

In 5.2 Options required for stateless DHCP service, add "Server Identifier" option
to the first list of options. The server always returns this in a Reply to identify
itself.

In 5.3 Options used for configuration information, add the references to the
documents. [3], [3], and [4] respectively.

In 5.4 Other options used in stateless DHCP, the Vendor-Specific Information can be
sent by clients to servers as well (it isn't just for server to client).

Also in this section, the Client DUID is Client Identifier. And, it is echoed back
by the server if the client supplied it (so the statement "servers never send this
option" is wrong - they send it if the client sent it).

And, perhaps a warning to implementators that other options may be sent by a server
which they may wish to ignore (such as Server Unicast and other configuration data
options).

In 7. Security Considerations, the 3rd paragraph is wrong. We don't allow a client
to send an Information-Request option with anything but its link-local address and
the destination is always a multicast.

This document is also silent with respect to Reconfigure. As no Reconfigure-Accept
is sent, Reconfigure will not be supported. However, clients MAY support this
feature if they wish. You probably chose to ignore this to keep it fairly simple.

- Bernie

-----Original Message-----
From: Ralph Droms [mailto:rdroms@cisco.com]
Sent: Sunday, April 06, 2003 9:07 AM
To: dhcwg@ietf.org
Subject: [dhcwg] Stateless DHCPv6 service


Now that the DHCPv6 base specification is at PS, and the DNS and time configuration option specs have passed WG last call, I have published "A Guide to Implementing Stateless DHCPv6 Service" as a dhc WG document, draft-ietf-dhc-dhcpv6-stateless-00.txt.

This revision of the document has been reviewed by Pekka Savola and Christian Huitema, and includes changes based on their input.  Based on the interest in this specification, I would like to progress it quickly.  Unless there are objections, I will start a WG last call for the specification in a week or so.

- Ralph

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