[dhcwg] RE: draft-chowdhury-dhc-bcmcv4-option-00.txt

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

Received: from megatron.ietf.org (megatron.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03680; Tue, 3 Aug 2004 01:47:21 -0400 (EDT)
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BrryW-0007Uz-Ln; Tue, 03 Aug 2004 01:36:36 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BrrwT-0006IR-LA 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 BAA02914 for <dhcwg@ietf.org>; Tue, 3 Aug 2004 01:34:29 -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 1BrrzT-0003hz-8Z 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:14 +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 i735Xv78013817; Mon, 2 Aug 2004 22:33:57 -0700 (PDT)
Received: from volzw2k (rtp-vpn3-154.cisco.com []) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AKO31703; Tue, 3 Aug 2004 01:33:54 -0400 (EDT)
From: Bernie Volz <volz@cisco.com>
To: chowdury@nortelnetworks.com, pyegani@cisco.com, Lila.Madour@ericsson.com
Date: Tue, 03 Aug 2004 01:33:37 -0400
Organization: Cisco
Message-ID: <000401c4791b$77efd220$3e858182@amer.cisco.com>
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, Build 10.0.5709
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: "'DHC WG (E-mail)'" <dhcwg@ietf.org>
Subject: [dhcwg] RE: draft-chowdhury-dhc-bcmcv4-option-00.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: 7bit

While preparing for the DHC WG meeting, I found these issues with

Option-Request-Option is used when it should be Parameter Request List

In section 2, informative is misspelled (inforamtive).

Client is misspelled (as cleint).

It is likely a bad idea to specify DNS compression. But this may be
something best discussed during the WG meeting or on the mailing list.

With the current design, it is only possible for ONE type of encoding to be
used (since multiple instances of the option are concatenated). So, you
might consider moving the encoding byte before EVERY entry in the list. So,
one could have:

Section 5 says "DHCPv6" when it should say DHCPv4. A reference in this
security issues section to RFC 3118 might also be appropriate? See some of
the other existing drafts for what you might add?

You might word the IANA Consideration section as:

   IANA is requested to assign a DHCPv4 option code for the Broadcast
Service Controller Domain Name list
   option, in accordance with RFC 2939.

I'm also wondering whether IANA needs to maintain a list of the encoding
types? But, hopefully not.

- Bernie

dhcwg mailing list