Re: [dhcwg] dhc WG last call on draft-ietf-dhc-bcmcv4-option-00.txt

Barr Hibbs <bhibbs@infoblox.com> Mon, 14 February 2005 16:51 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20969 for <dhcwg-web-archive@ietf.org>; Mon, 14 Feb 2005 11:51:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0jmY-0006iR-Q1 for dhcwg-web-archive@ietf.org; Mon, 14 Feb 2005 12:13:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0jKS-0006lO-5W; Mon, 14 Feb 2005 11:44:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0jJl-0006fJ-E8 for dhcwg@megatron.ietf.org; Mon, 14 Feb 2005 11:43:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20258 for <dhcwg@ietf.org>; Mon, 14 Feb 2005 11:43:21 -0500 (EST)
Received: from cerberus.infoblox.com ([128.242.99.209] helo=infoblox.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0jeZ-0006Vz-3M for dhcwg@ietf.org; Mon, 14 Feb 2005 12:04:59 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by infoblox.com (Postfix) with ESMTP id 201DEDCC04E for <dhcwg@ietf.org>; Mon, 14 Feb 2005 08:41:53 -0800 (PST)
Received: from infoblox.com ([127.0.0.1]) by localhost (cerberus [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21593-01 for <dhcwg@ietf.org>; Mon, 14 Feb 2005 08:41:53 -0800 (PST)
Received: from hermes.infoblox.com (hermes.infoblox.com [205.158.171.211]) by infoblox.com (Postfix) with ESMTP id DC4B0DCC042 for <dhcwg@ietf.org>; Mon, 14 Feb 2005 08:41:52 -0800 (PST)
Received: from infoblox.com ([205.158.171.199]) by hermes.infoblox.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Mon, 14 Feb 2005 08:42:48 -0800
Message-ID: <4210D571.3050009@infoblox.com>
Date: Mon, 14 Feb 2005 08:44:33 -0800
From: Barr Hibbs <bhibbs@infoblox.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dhcwg@ietf.org
Subject: Re: [dhcwg] dhc WG last call on draft-ietf-dhc-bcmcv4-option-00.txt
References: <4.3.2.7.2.20050209155308.02c26f00@flask.cisco.com>
In-Reply-To: <4.3.2.7.2.20050209155308.02c26f00@flask.cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Feb 2005 16:42:48.0458 (UTC) FILETIME=[378196A0:01C512B4]
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at infoblox.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Content-Transfer-Encoding: 7bit
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Content-Transfer-Encoding: 7bit

I support advancing the draft after addressing the issues 
listed below.

--Barr


General matters:

(Ralph) this is an example of an option that is being 
proposed for both DHCPv4 and DHCPv6.  Would it be good 
editorial policy to request that editors of option drafts in 
general follow the convention:

--use "DHCP" when something applies, without modification, 
to both DHCPv4 and DHCPv6, else
--use either "DHCPv4" or "DHCPv6" as appropriate?


Spelling and/or grammatical errors:

"Abstract:

"This document defines new options for Broadcast and 
Multicast Service controller discovery in an IP network. 
Broadcast service is being developed for 3G wireless 
networks.  Users of the service interact with a controller 
in the network to derive informations"

---"informations" should be "information"

"that are required to receive broadcast service.  Dynamic 
Host Configuration Protocol can be used to configure the 
controller"

---"controller" should be "controller's"

"IPv4 addresses or fully qualified domain names in the 
user's devices.  This document defines the related options 
and option codes."


"1.  Motivation

"Dynamic Host Configuration Protocol [RFC2131] can be used 
to configure various non-IP address type of parameters."

---change "various non-IP address type of parameters" to 
"various parameters"

"These parameters are required for normal operation of 
various services that are offered over an IP network.

"Broadcast and multicast service (BCMCS) is one such service 
that is currently being standardized in various mobile 
wireless standard bodies such as 3GPP, 3GPP2 and OMA.  A 
description of the BCMCS, for example, in 3GPP2 can be found 
in [BCMCS]."

---define the acronyms "3GPP," "3GPP2," and "OMA"

"DHCP is being used in 3GPP2, for example, to assist with 
the discovery of the BCMCS Controller in a mobile operators"

---change "operators" to "operator's"

"IP network.  The BCMCS includes a controller component that 
is responsible for managing the service via interaction with 
the users and other network entities."

"As described in [BCMCS], the users of the service are 
required to know the IPv4 address of the controller entity 
so that they can download all the necessary information"

---change "all the necessary information" to "all necessary 
information"

"about a desired broadcast program.  In a roaming 
environment static configuration of the controller IPv4 address"

---change "controller" to "controller's"

"becomes unrealistic.  Therefore, DHCP is considered to be a 
method to dynamically configure the controller IPv4 address 
or the fully qualified domain name of the controller in the 
3G wireless networks."

"In order to allow the users to discover the broadcast 
controllers, the clients request for appropriate option 
codes from the DHCP servers using Parameter Request List 
option."

---reword the sentence: "In order to allow the users to 
discover the broadcast controllers, the clients request 
options from DHCP servers using the Parameter Request List 
option (option number 55)."


"4.  Broadcast Service Controller Options

"This section defines the configuration option for the 
controller of Broadcast Service."

---change "configuration option for the controller of 
Broadcast Service" to "configuration option for the 
broadcast service controller."

"The Configuration Option contains the IPv4 address or the 
fully qualified domain names of the broadcast service 
controller."

---change "Configuration Option" to "configuration option"


functionality:

"4.  Broadcast Service Controller Options

"The option MAY contain multiple domain names, but these 
domain names SHOULD be used to construct SRV lookups as 
specified in [BCMCS], rather than querying for different A 
records.  The client MUST try the records in the order 
listed, applying the mechanism described in [BCMCS] for each 
entry."

---I think the client "SHOULD" try the records in the order 
listed, rather than "MUST"


"5.  Security Considerations"

(Ralph) Should it be the editorial policy of the DHC to ask 
that I-D editors not only state the risks that they imagine 
if their draft is accepted, but also offer proposed solutions?



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