IETF Logo Mail Archive

RE: [dhcwg] Reminder! dhc WG last call on draft-ietf-dhc-3315id-for-v4-01

"Richard Barr Hibbs" <rbhibbs@pacbell.net> Fri, 16 April 2004 04:16 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 AAA25405 for <dhcwg-archive@odin.ietf.org>; Fri, 16 Apr 2004 00:16:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEKkh-0007i0-Br for dhcwg-archive@odin.ietf.org; Fri, 16 Apr 2004 00:14:55 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3G4EtmT029626 for dhcwg-archive@odin.ietf.org; Fri, 16 Apr 2004 00:14:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEKeo-0006rO-Fx for dhcwg-web-archive@optimus.ietf.org; Fri, 16 Apr 2004 00:08:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25252 for <dhcwg-web-archive@ietf.org>; Fri, 16 Apr 2004 00:08:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BEKel-0001mS-Vk for dhcwg-web-archive@ietf.org; Fri, 16 Apr 2004 00:08:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BEKdq-0001jb-00 for dhcwg-web-archive@ietf.org; Fri, 16 Apr 2004 00:07:51 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BEKdZ-0001gP-00 for dhcwg-web-archive@ietf.org; Fri, 16 Apr 2004 00:07:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEKYE-0005lQ-VF; Fri, 16 Apr 2004 00:02:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEKV3-0004dN-Tq for dhcwg@optimus.ietf.org; Thu, 15 Apr 2004 23:58:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24851 for <dhcwg@ietf.org>; Thu, 15 Apr 2004 23:58:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BEKV1-00016i-IQ for dhcwg@ietf.org; Thu, 15 Apr 2004 23:58:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BEKU7-00013j-00 for dhcwg@ietf.org; Thu, 15 Apr 2004 23:57:47 -0400
Received: from smtp805.mail.sc5.yahoo.com ([66.163.168.184]) by ietf-mx with smtp (Exim 4.12) id 1BEKTB-00010m-00 for dhcwg@ietf.org; Thu, 15 Apr 2004 23:56:50 -0400
Received: from unknown (HELO BarrH63p601) (rbhibbs@pacbell.net@64.170.116.97 with login) by smtp805.mail.sc5.yahoo.com with SMTP; 16 Apr 2004 03:56:49 -0000
Reply-To: rbhibbs@pacbell.net
From: Richard Barr Hibbs <rbhibbs@pacbell.net>
To: dhcwg@ietf.org
Subject: RE: [dhcwg] Reminder! dhc WG last call on draft-ietf-dhc-3315id-for-v4-01
Date: Thu, 15 Apr 2004 21:04:50 -0700
Message-ID: <EJEFKKCLDBINLKODAFMDGECBDCAA.rbhibbs@pacbell.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
In-Reply-To: <4.3.2.7.2.20040412114206.02b471d8@flask.cisco.com>
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I support advancing this draft, but have a couple of minor
suggestions that I believe the authors should consider.

(1) Section 1.0 Applicability, second sentence:  "DHCPv4
servers implementations...." SHOULD read "DHCPv4 server
implementations...."

(2) Section 2.1 Client identities are ephemeral, last
sentence:  "...domain name as published through the DHCP
server" probably SHOULD read "...domain name as published
through the DHCPv4 server" as this paragraph is discussing
an issue with RFC 2132.  In other places in the draft DHCPv4
and DHCPv6 were separately identified where appropriate, and
jointly identified as DHCP when appropriate.

(3) Section 4.3 Changes from RFC2131, last sentence, "...is
replaced by the text, 'The client MUST explicitly provide a
client identifier through the "client identifier" option'"
would be improved by the addition of the following wording,
"...and MUST use the SAME client identifier for ALL
messages."

--Barr


> -----Original Message-----
> From: Ralph Droms
> Sent: Monday, 12 April 2004 08:52
>
> This message is a reminder of the WG last call on
> "Node-Specific Client Identifiers for DHCPv4"
> <draft-ietf-dhc-3315id-for-v4-01>.  The last call
> will conclude at 5PM on 4/16/04.
>


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

v2.23.0 | Report a Bug | By Email