[dhcwg] issues with draft-grochla-80211-dhcp-option-00
Alfred Hönes <ah@TR-Sys.de> Wed, 22 September 2010 12:47 UTC
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C31EE3A6B0C for <dhcwg@core3.amsl.com>; Wed, 22 Sep 2010 05:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.736
X-Spam-Level:
X-Spam-Status: No, score=-97.736 tagged_above=-999 required=5 tests=[AWL=1.013, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fCSxXa4JOxCf for <dhcwg@core3.amsl.com>; Wed, 22 Sep 2010 05:47:32 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id E005E3A6AFE for <dhcwg@ietf.org>; Wed, 22 Sep 2010 05:47:31 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA204409531; Wed, 22 Sep 2010 14:45:31 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id OAA25958; Wed, 22 Sep 2010 14:45:29 +0200 (MESZ)
From: Alfred Hönes <ah@TR-Sys.de>
Message-Id: <201009221245.OAA25958@TR-Sys.de>
To: kgrochla@proximetry.com
Date: Wed, 22 Sep 2010 14:45:29 +0200
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset="hp-roman8"
Content-Transfer-Encoding: 8bit
Cc: dhcwg@ietf.org
Subject: [dhcwg] issues with draft-grochla-80211-dhcp-option-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Sep 2010 12:47:33 -0000
I have two fundamental concerns and found several minor issues with draft-grochla-80211-dhc-option-00 : a) The scope of the proposed options is _very_ restricted. Given the scarcity of DHCPv4 option numbers and the intimate relationship to IEEE 802.11, wouldn't it be a much cleaner solution to use vendor-specific options for this purpose (under an IEEE owned vendor ID) than further reducing the DHCPv4 option code name space -- the latter should preferably be reserved for options with a more general applicability? Such specification would perhaps need support from IEEE 802.11, but could be published as an Informational RFC. b) The option formats for DHCPv6 and DHCPv4 differ in a substantial way. Firstly, the option codes are drawn from independent namespaces of different bit size (single-octet vs. 16-bit option code fields) and the option-length fields have both different width and different semantics. Further, the processing rules are different in a subtle way (e.g. concatenation in DHCPv4). Therefore, options for DHCPv4 and DHCPv6 need to be specified independently, and for the independent option code name spaces independent IANA assignment requests need to be included. Further, the ways to request delivery of options is different in v6 from v4 and needs to be spelled out differently. The syntax of the information elements should be specified, in order to allow proper treatment in mechanisms to configure DHCP servers intended to serve this option (the current draft only describes the option-code and option-length fields for the DHCPv6 case). Minor issues: Please ... - perform an in-depth grammar check of the text (with a particular focus on the use of articles and on singular/plural mismatches); - avoid such silly phrases as "DHCP protocol" -- where the "P" already stands for "protocol". - Where you say "[to] relay on", I suspect you mean "[to] rely upon". - Finally, I suggest to use the current I-D boilerplate text for the front page "Status of this Memo" -- including the placement of the Abstract in front of that boilerplate text. Kind regards, Alfred Hönes. -- +------------------------+--------------------------------------------+ | TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. | | Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 | | D-71254 Ditzingen | E-Mail: ah@TR-Sys.de | +------------------------+--------------------------------------------+
- [dhcwg] issues with draft-grochla-80211-dhcp-opti… Alfred Hönes
- Re: [dhcwg] issues with draft-grochla-80211-dhcp-… Ted Lemon
- Re: [dhcwg] issues with draft-grochla-80211-dhcp-… Glen Zorn
- [dhcwg] extending the DHCPv4 option space, VSO us… Alfred Hönes
- Re: [dhcwg] issues with draft-grochla-80211-dhcp-… Ted Lemon
- Re: [dhcwg] extending the DHCPv4 option space, VS… Ted Lemon
- Re: [dhcwg] issues with draft-grochla-80211-dhcp-… Donald Eastlake
- Re: [dhcwg] extending the DHCPv4 option space, VS… Glen Zorn
- Re: [dhcwg] issues with draft-grochla-80211-dhcp-… Ted Lemon
- Re: [dhcwg] extending the DHCPv4 option space, VS… Alfred Hönes
- Re: [dhcwg] extending the DHCPv4 option space, VS… Ted Lemon
- Re: [dhcwg] extending the DHCPv4 option space, VS… Thomas Narten