IETF Logo Mail Archive

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

Ralph Droms <rdroms@cisco.com> Fri, 02 January 2004 16:11 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14048 for <dhcwg-archive@odin.ietf.org>; Fri, 2 Jan 2004 11:11:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcRst-0005jW-Il for dhcwg-archive@odin.ietf.org; Fri, 02 Jan 2004 11:10:47 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i02GAlFK022032 for dhcwg-archive@odin.ietf.org; Fri, 2 Jan 2004 11:10:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcRst-0005jH-Di for dhcwg-web-archive@optimus.ietf.org; Fri, 02 Jan 2004 11:10:47 -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 LAA14032 for <dhcwg-web-archive@ietf.org>; Fri, 2 Jan 2004 11:10:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AcRsl-00074f-00 for dhcwg-web-archive@ietf.org; Fri, 02 Jan 2004 11:10:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AcRpa-0006wj-00 for dhcwg-web-archive@ietf.org; Fri, 02 Jan 2004 11:07:25 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AcRmj-0006s3-00 for dhcwg-web-archive@ietf.org; Fri, 02 Jan 2004 11:04:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcRmL-0005Ig-Bv; Fri, 02 Jan 2004 11:04:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcRmA-0005IV-LA for dhcwg@optimus.ietf.org; Fri, 02 Jan 2004 11:03:50 -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 LAA13916 for <dhcwg@ietf.org>; Fri, 2 Jan 2004 11:03:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AcRm3-0006q5-00 for dhcwg@ietf.org; Fri, 02 Jan 2004 11:03:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AcRjS-0006mj-00 for dhcwg@ietf.org; Fri, 02 Jan 2004 11:01:05 -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 1AcRhA-0006jJ-00 for dhcwg@ietf.org; Fri, 02 Jan 2004 10:58:40 -0500
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i02Fw7VM009352 for <dhcwg@ietf.org>; Fri, 2 Jan 2004 07:58:08 -0800 (PST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn1-195.cisco.com [10.21.96.195]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AEZ18704; Fri, 2 Jan 2004 10:58:06 -0500 (EST)
Message-Id: <4.3.2.7.2.20040102104312.01e3c220@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 02 Jan 2004 10:58:04 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] Title for draft-ietf-dhc-dhcpv6-stateless-03.txt
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>

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

v2.23.0 | Report a Bug | By Email