IETF Logo Mail Archive

Re: [dhcwg] I-D ACTION:draft-ietf-dhc-3315id-for-v4-02.txt + LAST CALL Comments

Ted Lemon <mellon@fugue.com> Sat, 10 April 2004 03:56 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08178 for <dhcwg-archive@odin.ietf.org>; Fri, 9 Apr 2004 23:56:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC9bG-00054E-If for dhcwg-archive@odin.ietf.org; Fri, 09 Apr 2004 23:56:10 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3A3uAON019477 for dhcwg-archive@odin.ietf.org; Fri, 9 Apr 2004 23:56:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC9bG-000544-3z for dhcwg-web-archive@optimus.ietf.org; Fri, 09 Apr 2004 23:56:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08136 for <dhcwg-web-archive@ietf.org>; Fri, 9 Apr 2004 23:56:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BC9bC-0004CV-00 for dhcwg-web-archive@ietf.org; Fri, 09 Apr 2004 23:56:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BC9Zv-00042E-00 for dhcwg-web-archive@ietf.org; Fri, 09 Apr 2004 23:54:49 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BC9YG-0003lA-00 for dhcwg-web-archive@ietf.org; Fri, 09 Apr 2004 23:53:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC9YD-0004r3-S1; Fri, 09 Apr 2004 23:53:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC9Y2-0004qW-Qo for dhcwg@optimus.ietf.org; Fri, 09 Apr 2004 23:52:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07994 for <dhcwg@ietf.org>; Fri, 9 Apr 2004 23:52:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BC9Xz-0003gz-00 for dhcwg@ietf.org; Fri, 09 Apr 2004 23:52:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BC9We-0003T1-00 for dhcwg@ietf.org; Fri, 09 Apr 2004 23:51:25 -0400
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 1BC9VJ-0003HP-00 for dhcwg@ietf.org; Fri, 09 Apr 2004 23:50:01 -0400
Received: from [192.168.1.101] (pcp08421798pcs.orovly01.az.comcast.net [69.139.223.225]) by toccata.fugue.com (Postfix) with ESMTP id C604E1C1415; Fri, 9 Apr 2004 22:43:03 -0500 (CDT)
In-Reply-To: <002c01c41e4c$bd8d0520$6401a8c0@amer.cisco.com>
References: <002c01c41e4c$bd8d0520$6401a8c0@amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <1BEB42C0-8AA2-11D8-AE87-000A95D9C74C@fugue.com>
Content-Transfer-Encoding: 7bit
Cc: rbhibbs@pacbell.net, 'Dhcwg' <dhcwg@ietf.org>
From: Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] I-D ACTION:draft-ietf-dhc-3315id-for-v4-02.txt + LAST CALL Comments
Date: Fri, 09 Apr 2004 20:49:46 -0700
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Apr 9, 2004, at 9:07 AM, Bernie Volz wrote:
> I would be against this because it will take significantly longer
> (revising 2131/2132 will take a while to get through the IETF process).

Yup, I agree with Bernie on this.   I don't think we should think of 
the RFC2131/2132 revision something that's going to happen quickly.   
Of course we should try to do it in a timely fashion, but we shouldn't 
expect that we will definitely succeed.   Look at how hard it's been to 
make leasequery, a fairly straightforward extension, happen.   :'/



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

v2.30.2 | Report a Bug | By Email | System Status