[dhcwg] RE: draft-daniel-dhc-dhcpv4-tep-conf-01.txt

"Bernie Volz" <volz@cisco.com> Tue, 03 August 2004 05:44 UTC

Received: from megatron.ietf.org (megatron.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03468; Tue, 3 Aug 2004 01:44:38 -0400 (EDT)
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BrryV-0007Uf-T4; Tue, 03 Aug 2004 01:36:35 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BrrwT-0006IP-0l for dhcwg@megatron.ietf.org; Tue, 03 Aug 2004 01:34:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02911 for <dhcwg@ietf.org>; Tue, 3 Aug 2004 01:34:28 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrrzS-0003hr-OB for dhcwg@ietf.org; Tue, 03 Aug 2004 01:37:36 -0400
Received: from sj-core-5.cisco.com ( by sj-iport-3.cisco.com with ESMTP; 02 Aug 2004 22:36:10 +0000
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com []) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i735Xr78013774; Mon, 2 Aug 2004 22:33:54 -0700 (PDT)
Received: from volzw2k (rtp-vpn3-154.cisco.com []) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AKO31700; Tue, 3 Aug 2004 01:33:50 -0400 (EDT)
From: Bernie Volz <volz@cisco.com>
To: soohong.park@samsung.com
Date: Tue, 03 Aug 2004 01:33:37 -0400
Organization: Cisco
Message-ID: <000201c4791b$7567eec0$3e858182@amer.cisco.com>
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.5709
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: quoted-printable
Cc: "'DHC WG (E-mail)'" <dhcwg@ietf.org>, olnrao@samsung.com, syam@samsung.com
Subject: [dhcwg] RE: draft-daniel-dhc-dhcpv4-tep-conf-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable


While preparing for the IETF meeting, I have these comments on the
draft-daniel-dhc-dhcpv4-tep-conf-01.txt draft.

It's probably best to remove the "reserved" byte from the two options in
this draft unless you expect to use this field sometime in the future.

Trying to align the remaining fields is really useless since there is no
guarentee that the option byte will be aligned on any particular boundry
(other than on a byte boundry). The client and server will just have to
pack/unpack the data. And, saving the one byte from the option could be
useful (as DHCPv4 is often restricted to fairly small packet sizes).

And, it might be best to move the prefix-length field to before the IPv6
address (keeping them together). 

The DHCP messages used in this draft are the DHCPv6 ones - not the DHCPv4
ones. You really want to use DHCPDISCOVER, DHCPOFFER, DHCPACK and the like
for the message names!

I also don't understand the need for the OPTION_CTEP_REQ option. Either you
need to explain this better in the draft (what, for example would the client
fill in in this option) or remove it - why can't the client just simply
request this option in a Parameter Request List option?

- Bernie

dhcwg mailing list