Re: [dhcwg] Internet Drafts to be reviewed by the dhc WG

Ted Lemon <mellon@fugue.com> Thu, 01 April 2004 00:10 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 TAA21843 for <dhcwg-archive@odin.ietf.org>; Wed, 31 Mar 2004 19:10:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8pmA-000547-TJ for dhcwg-archive@odin.ietf.org; Wed, 31 Mar 2004 19:09:43 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3109gWw019472 for dhcwg-archive@odin.ietf.org; Wed, 31 Mar 2004 19:09:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8pmA-00053z-Fg for dhcwg-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 19:09:42 -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 TAA21827 for <dhcwg-web-archive@ietf.org>; Wed, 31 Mar 2004 19:09:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B8pm7-0004I3-00 for dhcwg-web-archive@ietf.org; Wed, 31 Mar 2004 19:09:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B8plC-0004G1-00 for dhcwg-web-archive@ietf.org; Wed, 31 Mar 2004 19:08:43 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B8pkc-0004EK-00 for dhcwg-web-archive@ietf.org; Wed, 31 Mar 2004 19:08:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8pkY-0004It-CH; Wed, 31 Mar 2004 19:08:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8pkD-000496-J6 for dhcwg@optimus.ietf.org; Wed, 31 Mar 2004 19:07:41 -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 TAA21740 for <dhcwg@ietf.org>; Wed, 31 Mar 2004 19:07:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B8pkA-0004DD-00 for dhcwg@ietf.org; Wed, 31 Mar 2004 19:07:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B8pjG-0004Ba-00 for dhcwg@ietf.org; Wed, 31 Mar 2004 19:06:43 -0500
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 1B8pic-0004A3-00 for dhcwg@ietf.org; Wed, 31 Mar 2004 19:06:02 -0500
Received: from [10.0.1.2] (24-148-56-150.c3-0.snb-ubr1.chi-snb.il.cable.rcn.com [24.148.56.150]) by toccata.fugue.com (Postfix) with ESMTP id 612B61B95E8 for <dhcwg@ietf.org>; Wed, 31 Mar 2004 18:00:48 -0600 (CST)
Mime-Version: 1.0 (Apple Message framework v613)
In-Reply-To: <000201c41776$e52df2b0$d0412ca1@amer.cisco.com>
References: <000201c41776$e52df2b0$d0412ca1@amer.cisco.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <5B2E935C-8370-11D8-BF4A-000A95D9C74C@fugue.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] Internet Drafts to be reviewed by the dhc WG
Date: Wed, 31 Mar 2004 18:05:59 -0600
To: "<dhcwg@ietf.org> <dhcwg@ietf.org>" <dhcwg@ietf.org>
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 Mar 31, 2004, at 5:21 PM, Bernie Volz wrote:
> I think the WG should take up the issue of how best to handle options
> that want to specify either or both domain names and IPv6 addresses.

I would rephrase this.   The working group in the past has taken up the 
issue of *whether* to send IP addresses or domain names, and we've 
historically decided to send IP addresses, so that the client isn't 
required to contain a resolver.   Supporting (and requiring all clients 
to support) both options is expensive.   So if the wg needs to discuss 
this again, I think the question should be whether to make it possible 
to send domain names instead of IP addresses, before we answer the 
question of how to do it.

If we don't reopen that question, I would suggest that we advise the 
midcom folks to always send an IP address, and never a domain name, and 
to not have two different options.   Otherwise, as you say, they have 
to specify how to choose, and whether it's okay to only send the domain 
name, and that whole can of worms.


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