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

Ralph Droms <rdroms@cisco.com> Thu, 03 February 2005 14:58 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 JAA28961 for <dhcwg-web-archive@ietf.org>; Thu, 3 Feb 2005 09:58:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwijQ-0000As-K9 for dhcwg-web-archive@ietf.org; Thu, 03 Feb 2005 10:17:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwiMS-00086J-OR; Thu, 03 Feb 2005 09:53:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwiDF-00068r-J0 for dhcwg@megatron.ietf.org; Thu, 03 Feb 2005 09:44:05 -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 JAA27669 for <dhcwg@ietf.org>; Thu, 3 Feb 2005 09:44:04 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwiVp-00089U-O5 for dhcwg@ietf.org; Thu, 03 Feb 2005 10:03:19 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 03 Feb 2005 09:43:34 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j13EhVQL022590; Thu, 3 Feb 2005 09:43:31 -0500 (EST)
Received: from rdroms-w2k01.cisco.com ([161.44.65.140]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AOV07657; Thu, 3 Feb 2005 09:43:30 -0500 (EST)
Message-Id: <4.3.2.7.2.20050203094011.02c07608@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 03 Feb 2005 09:43:27 -0500
To: Margaret Wasserman <margaret@thingmagic.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] draft-chowdhury-dhc-bcmcv[46]-option-01.txt
In-Reply-To: <p06200711be27e72f24e4@[192.168.2.2]>
References: <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: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: narten@us.ibm.com, dhcwg@ietf.org, Stig Venaas <Stig.Venaas@uninett.no>
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: cab78e1e39c4b328567edb48482b6a69

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.  The WG responded to 3GPP2 to
prefer VIVSO, and 3GPP2 came back to express preference for RFC 2132-style
options.  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.

- 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