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

Parviz Yegani <pyegani@cisco.com> Thu, 03 February 2005 22:12 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 RAA26844 for <dhcwg-web-archive@ietf.org>; Thu, 3 Feb 2005 17:12:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwpW6-00019f-4M for dhcwg-web-archive@ietf.org; Thu, 03 Feb 2005 17:32:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwoVF-00080O-9B; Thu, 03 Feb 2005 16:27:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cwo5Q-0002Jv-Ki for dhcwg@megatron.ietf.org; Thu, 03 Feb 2005 16:00: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 QAA08315 for <dhcwg@ietf.org>; Thu, 3 Feb 2005 16:00:22 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwoO3-00043r-0S for dhcwg@ietf.org; Thu, 03 Feb 2005 16:19:40 -0500
Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-4.cisco.com with ESMTP; 03 Feb 2005 12:59:58 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from pyegani-w2k02.cisco.com (sjc-vpn6-431.cisco.com [10.21.121.175]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j13Kxl83015052; Thu, 3 Feb 2005 12:59:48 -0800 (PST)
Message-Id: <4.3.2.7.2.20050203123756.03e1b588@franklin.cisco.com>
X-Sender: pyegani@franklin.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 03 Feb 2005 12:59:46 -0800
To: Ralph Droms <rdroms@cisco.com>
From: Parviz Yegani <pyegani@cisco.com>
Subject: Re: [dhcwg] draft-chowdhury-dhc-bcmcv[46]-option-01.txt
In-Reply-To: <4.3.2.7.2.20050203094011.02c07608@flask.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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
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: 0fa76816851382eb71b0a882ccdc29ac

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