Re: [dhcwg] Dual-stack hosts using DHCP as dhc WG charter item

Ted Lemon <mellon@fugue.com> Mon, 15 March 2004 22:38 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 RAA03813 for <dhcwg-archive@odin.ietf.org>; Mon, 15 Mar 2004 17:38:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B30j7-00038n-B9 for dhcwg-archive@odin.ietf.org; Mon, 15 Mar 2004 17:38:29 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2FMcTOn012059 for dhcwg-archive@odin.ietf.org; Mon, 15 Mar 2004 17:38:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B30j6-00038Q-QM for dhcwg-web-archive@optimus.ietf.org; Mon, 15 Mar 2004 17:38:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03729 for <dhcwg-web-archive@ietf.org>; Mon, 15 Mar 2004 17:38:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B30j4-000786-00 for dhcwg-web-archive@ietf.org; Mon, 15 Mar 2004 17:38:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B30hu-0006xA-00 for dhcwg-web-archive@ietf.org; Mon, 15 Mar 2004 17:37:15 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B30gs-0006lw-00 for dhcwg-web-archive@ietf.org; Mon, 15 Mar 2004 17:36:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B30gp-0002aK-Af; Mon, 15 Mar 2004 17:36:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B30gH-0002VC-Ad for dhcwg@optimus.ietf.org; Mon, 15 Mar 2004 17:35:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03300 for <dhcwg@ietf.org>; Mon, 15 Mar 2004 17:35:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B30gE-0006fP-00 for dhcwg@ietf.org; Mon, 15 Mar 2004 17:35:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B30ei-0006LL-00 for dhcwg@ietf.org; Mon, 15 Mar 2004 17:33:57 -0500
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 1B30bW-0005w6-00 for dhcwg@ietf.org; Mon, 15 Mar 2004 17:30:38 -0500
Received: from [66.93.187.232] (dsl093-187-232.chi2.dsl.speakeasy.net [66.93.187.232]) by toccata.fugue.com (Postfix) with ESMTP id C29DF1B2230; Mon, 15 Mar 2004 16:25:02 -0600 (CST)
In-Reply-To: <4.3.2.7.2.20040315161655.028ffcf8@flask.cisco.com>
References: <4.3.2.7.2.20040315161655.028ffcf8@flask.cisco.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <5D9A3DC6-76D0-11D8-8D56-000A95D9C74C@fugue.com>
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
From: Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] Dual-stack hosts using DHCP as dhc WG charter item
Date: Mon, 15 Mar 2004 16:30:30 -0600
To: Ralph Droms <rdroms@cisco.com>
X-Mailer: Apple Mail (2.612)
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

Isn't the problem with the nis draft a question of whether it really 
needs that section that says in what packet types the option is 
allowed?

Personally, I think we should advance the drafts unchanged - I don't 
see how a solution to the dual-stack issue is going to work if it 
requires that all the existing option drafts be changed, and 
furthermore I don't really see a reason why we'd do it that way even if 
it were an option.

I think it might be worth discussing whether or not there's a better 
way to handle the "this option allowed in packets of type X" 
boilerplate, though, without holding this draft hostage to the 
discussion.


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