RE: [dhcwg] Title for draft-ietf-dhc-dhcpv6-stateless-03.txt

"Bernie Volz" <volz@metrocast.net> Fri, 02 January 2004 16:59 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15642 for <dhcwg-archive@odin.ietf.org>; Fri, 2 Jan 2004 11:59: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 1AcSdZ-0007HN-8H for dhcwg-archive@odin.ietf.org; Fri, 02 Jan 2004 11:59:01 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i02Gx1ar027978 for dhcwg-archive@odin.ietf.org; Fri, 2 Jan 2004 11:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcSdZ-0007HB-4I for dhcwg-web-archive@optimus.ietf.org; Fri, 02 Jan 2004 11:59:01 -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 LAA15617 for <dhcwg-web-archive@ietf.org>; Fri, 2 Jan 2004 11:58:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AcSdX-0001Qb-00 for dhcwg-web-archive@ietf.org; Fri, 02 Jan 2004 11:58:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AcSb3-0001LG-00 for dhcwg-web-archive@ietf.org; Fri, 02 Jan 2004 11:56:28 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AcSZm-0001Gm-00 for dhcwg-web-archive@ietf.org; Fri, 02 Jan 2004 11:55:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcSZi-00079x-Pa; Fri, 02 Jan 2004 11:55:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcSYk-00079G-Vg for dhcwg@optimus.ietf.org; Fri, 02 Jan 2004 11:54:03 -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 LAA15454 for <dhcwg@ietf.org>; Fri, 2 Jan 2004 11:53:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AcSYj-0001Db-00 for dhcwg@ietf.org; Fri, 02 Jan 2004 11:54:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AcSWn-00018b-00 for dhcwg@ietf.org; Fri, 02 Jan 2004 11:52:04 -0500
Received: from pan.gwi.net ([207.5.128.165]) by ietf-mx with esmtp (Exim 4.12) id 1AcSUr-00011S-00 for dhcwg@ietf.org; Fri, 02 Jan 2004 11:50:01 -0500
Received: from BVolz (d-216-195-132-224.metrocast.net [216.195.132.224]) by pan.gwi.net (8.12.6p3/8.12.6) with ESMTP id i02GnmGn095230; Fri, 2 Jan 2004 11:49:57 -0500 (EST) (envelope-from volz@metrocast.net)
From: Bernie Volz <volz@metrocast.net>
To: 'Ralph Droms' <rdroms@cisco.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] Title for draft-ietf-dhc-dhcpv6-stateless-03.txt
Date: Fri, 02 Jan 2004 11:49:59 -0500
Message-ID: <000001c3d150$7881fec0$6401a8c0@BVolz>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <4.3.2.7.2.20040102104312.01e3c220@flask.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
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>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Ralph:

I don't have any objection to changing the document name to "Stateless
DHCPv6 Server". 

I would suggest that perhaps section 4 have an explicit reference to RFC
3315 and DHCPv6:

4. Basic Requirements for Implementation of DHCP

      Several sections of the DHCPv6 specification [1] provide background
                                  ^^               ^^^
      information or define parts of the specification that are common
      to all implementations:

Note that in most places you refer to RFC 3315 as "DHCPv6 specification" and
not DHCP specification.

Also, you should review your use of DHCP vs. DHCPv6 throughout. In section
2, you state "Throughout this document, "DHCP" refers to DHCP for IPv6." But
DHCPv6 is used fairly frequently. Personally, I'd prefer that "DHCPv6" be
used instead of just "DHCP". But, whichever you decide, I think it important
that the usage is consistent.

- Bernie


-----Original Message-----
From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org] On Behalf Of Ralph
Droms
Sent: Friday, January 02, 2004 10:58 AM
To: dhcwg@ietf.org
Subject: [dhcwg] Title for draft-ietf-dhc-dhcpv6-stateless-03.txt

The IESG is reviewing draft-ietf-dhc-dhcpv6-stateless-03.txt, "A Guide to
Implementing Stateless DHCPv6 Service".  There is a request to change the
title to simply "Stateless DHCPv6 Service", because the document defines a
subset of RFC 3315, rather than giving a guide to implementing RFC 3315.

I am concerned that there has been confusion in the past that
draft-ietf-dhc-dhcpv6-stateless-03.txt is simply a reference into RFC 3315,
and that draft-ietf-dhc-dhcpv6-stateless-03.txt does *not* describe a new
protocol.  If the WG is confident that the change won't add to the potential
for confusion and there are no other objections, I'll change the title of
draft-ietf-dhc-dhcpv6-stateless-03.txt to "Stateless DHCPv6 Service"

- Ralph


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




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