IETF Logo Mail Archive

Re: [dhcwg] draft-ietf-dhc-packetcable-04.txt

Ralph Droms <rdroms@cisco.com> Mon, 23 December 2002 15:22 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06367 for <dhcwg-archive@odin.ietf.org>; Mon, 23 Dec 2002 10:22:20 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBNFPqR17614 for dhcwg-archive@odin.ietf.org; Mon, 23 Dec 2002 10:25:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBNFPqv17610 for <dhcwg-web-archive@optimus.ietf.org>; Mon, 23 Dec 2002 10:25:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06311 for <dhcwg-web-archive@ietf.org>; Mon, 23 Dec 2002 10:21:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBNFNcv17568; Mon, 23 Dec 2002 10:23:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBNFM3v17549 for <dhcwg@optimus.ietf.org>; Mon, 23 Dec 2002 10:22:03 -0500
Received: from rtp-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06246 for <dhcwg@ietf.org>; Mon, 23 Dec 2002 10:18:01 -0500 (EST)
Received: from funnel.cisco.com (localhost [127.0.0.1]) by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gBNFLbvi028449; Mon, 23 Dec 2002 10:21:37 -0500 (EST)
Received: from rdroms-w2k.cisco.com (dhcp-161-44-149-137.cisco.com [161.44.149.137]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA29215; Mon, 23 Dec 2002 10:21:01 -0500 (EST)
Message-Id: <4.3.2.7.2.20021223101647.0204aed0@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 23 Dec 2002 10:20:59 -0500
To: Thomas Narten <narten@us.ibm.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-packetcable-04.txt
Cc: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>, 'Paul Duffy' <paduffy@cisco.com>, dhcwg@ietf.org
In-Reply-To: <200212211556.gBLFu6i07518@cichlid.adsl.duke.edu>
References: <Message from "Woundy, Richard" <Richard_Woundy@cable.comcast.com> <6732623D2548D61193C90002A5C88DCC01EBD00A@entmaexch02.broadband.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>

As a way of getting more timely coordination between CableLabs and the 
IETF, would it be possible to involve the IETF earlier in the process of 
developing an option?  That is, as soon as CableLabs identifies the need 
for a new sub-option, publish an Internet-Draft describing that sub-option 
and bring it to the IETF/DHCWG.  Development can take place in parallel - 
Internet-Drafts are cheap - so that the WG has a chance to review the new 
option and can be prepared to bring it to last call as soon as the 
CableLabs change control process has the new specs in place.

- Ralph

At 10:56 AM 12/21/2002 -0500, Thomas Narten wrote:
> > I wish there was a way to balance IETF's needs to review new
> > suboptions, and CableLabs needs to define new suboptions in a timely
> > fashion.
>
>I agree. I am still under the assumption that this is achievable.




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

v2.23.0 | Report a Bug | By Email