Re: [dhcwg] draft-chowdhury-dhc-bcmcv[46]-option-01.txt

AC Mahendran <mahendra@qualcomm.com> Fri, 04 February 2005 02:53 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 VAA22603 for <dhcwg-web-archive@ietf.org>; Thu, 3 Feb 2005 21:53:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cwttv-00013B-6I for dhcwg-web-archive@ietf.org; Thu, 03 Feb 2005 22:12:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwtZ4-0001nV-39; Thu, 03 Feb 2005 21:51:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwtPk-0007oj-4M for dhcwg@megatron.ietf.org; Thu, 03 Feb 2005 21:41:44 -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 VAA21203 for <dhcwg@ietf.org>; Thu, 3 Feb 2005 21:41:42 -0500 (EST)
Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwtiQ-0000dZ-Ms for dhcwg@ietf.org; Thu, 03 Feb 2005 22:01:03 -0500
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j142f9eD000050; Thu, 3 Feb 2005 18:41:09 -0800 (PST)
Received: from MAHENDRA.qualcomm.com (mahendra.qualcomm.com [129.46.74.166]) by neophyte.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j142f55J007324; Thu, 3 Feb 2005 18:41:06 -0800 (PST)
Message-Id: <6.1.2.0.2.20050203183553.03d57d30@qcmail1.qualcomm.com>
X-Sender: mahendra@qcmail1.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Thu, 03 Feb 2005 18:41:13 -0800
To: Parviz Yegani <pyegani@cisco.com>, Ralph Droms <rdroms@cisco.com>
From: AC Mahendran <mahendra@qualcomm.com>
Subject: Re: [dhcwg] draft-chowdhury-dhc-bcmcv[46]-option-01.txt
In-Reply-To: <4.3.2.7.2.20050203123756.03e1b588@franklin.cisco.com>
References: <p06200711be27e72f24e4@[192.168.2.2]> <4.3.2.7.2.20050203084733.02c14e60@flask.cisco.com> <4.3.2.7.2.20050203084733.02c14e60@flask.cisco.com> <4.3.2.7.2.20050203123756.03e1b588@franklin.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-PMX-Version: 4.7.0.111621
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: Margaret Wasserman <margaret@thingmagic.com>, narten@us.ibm.com, Stig Venaas <Stig.Venaas@uninett.no>, dhcwg@ietf.org
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: b5d20af10c334b36874c0264b10f59f1

I agree with Parviz that using the VIVSO options is complicated and 
requires upgrades to existing DHCP servers. Since wireless carriers want to 
deploy these broadcast services soon, 3GPP2's preference is to use RFC 
2132-style options.

Thanks,
AC

At 12:59 PM 2/3/2005, Parviz Yegani wrote:
>At 09:43 AM 2/3/2005 -0500, Ralph Droms wrote:
>>Margaret - these drafts are sort of falling into a crack.  I don't know of
>>another WG that can evaluate the requirements.  The information and option
>>format is trivial and the WG can review them.
>
>Agree, the options defined in these two drafts are no different from any other
>DHCP options introduced so far.
>
>>The WG responded to 3GPP2 to
>>prefer VIVSO, and 3GPP2 came back to express preference for RFC 2132-style
>>options.
>
>The 3GPP2 specification (to be published soon) is based on these drafts. 
>Adopting
>these options will have minimal (or no) impact on current implementations. 
>I'm not sure
>if there is any advantage on pursuing the VIVSO approach from a deployment 
>perspective.
>
>>The dhc WG chairs have not been able to get any additional
>>justification from 3GPP2, and we have been getting pressure to move forward
>>quickly.  Seems at this point a WG last call is a good way to "call the
>>question" and get the discussion started so the various issues can be aired.
>
>What additional justification you need from 3GPP2 given that the proposed 
>options
>have minimal impact on the current implementations plus it's in line with 
>other DHCP
>extensions. These are used for broadcast/multicast services which are 
>currently being
>standardized by other SDOs like 3GPP and OMA.
>
>-Parviz
>
>
>
>>- Ralph
>>
>>
>>At 09:38 AM 2/3/2005 -0500, Margaret Wasserman wrote:
>>
>>>You know, I am still a bit confused about these drafts...
>>>
>>>Do you (Ralph and Stig) actually think that there is appropriate 
>>>expertise in the DHCP WG to review these drafts?  If not, where is the 
>>>group that actually needs these options (the subject matter experts) and 
>>>have they reviewed the drafts?
>>>
>>>I realize that 3GPP wants DHCP options to configure BCMCV (whatever that 
>>>is), but that doesn' t mean (IMO) that we can or should completely 
>>>bypass the usual DHCP WG process...
>>>
>>>Margaret
>>>
>>>
>>>At 8:49 AM -0500 2/3/05, Ralph Droms wrote:
>>>>As we have been asked to expedite our review of these drafts for the
>>>>upcoming 3GPP2 standard, we need to have a WG last call on both drafts.  If
>>>>there are no objections, I will start a last call for each draft starting
>>>>2005-02-07.
>>>>
>>>>- Ralph
>>>>
>>>>_______________________________________________
>>>>dhcwg mailing list
>>>>dhcwg@ietf.org
>>>>https://www1.ietf.org/mailman/listinfo/dhcwg
>>
>>_______________________________________________
>>dhcwg mailing list
>>dhcwg@ietf.org
>>https://www1.ietf.org/mailman/listinfo/dhcwg
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/dhcwg


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