Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt

Ted Lemon <Ted.Lemon@nominum.com> Mon, 24 February 2003 22:30 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 RAA28771 for <dhcwg-archive@odin.ietf.org>; Mon, 24 Feb 2003 17:30:30 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1OMdEr30742 for dhcwg-archive@odin.ietf.org; Mon, 24 Feb 2003 17:39:14 -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 h1OMdEp30739 for <dhcwg-web-archive@optimus.ietf.org>; Mon, 24 Feb 2003 17:39:14 -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 RAA28768 for <dhcwg-web-archive@ietf.org>; Mon, 24 Feb 2003 17:29:59 -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 h1OMbdp30694; Mon, 24 Feb 2003 17:37:39 -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 h1OMaGp29912 for <dhcwg@optimus.ietf.org>; Mon, 24 Feb 2003 17:36:16 -0500
Received: from toccata.fugue.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28706 for <dhcwg@ietf.org>; Mon, 24 Feb 2003 17:27:01 -0500 (EST)
Received: from nominum.com (az-ben-pm3-2-13.ppp.theriver.com [206.25.50.13]) by toccata.fugue.com (8.11.6/8.6.11) with ESMTP id h1OMRYN17837; Mon, 24 Feb 2003 16:27:35 -0600 (CST)
Date: Mon, 24 Feb 2003 15:30:56 -0700
Subject: Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v551)
Cc: dhcwg@ietf.org
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <200302241912.h1OJCIPV016363@marajade.sandelman.ottawa.on.ca>
Message-Id: <A4021FBA-4847-11D7-8498-00039317663C@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> Often, seeminly unreasonable configurations are the result of trying
> to patch around a problem elsewhere.

I.e., they're not something with which a standards body need 
necessarily concern itself.   ;')

To be less provocative, my point is that if we are using DHCPv6, we 
probably are expecting that the IPv6 infrastructure we are using works. 
   If not, why are we trying to use it?   If it's broken, isn't the 
right answer to fix it?   I'm not saying you shouldn't kludge around 
problems like this when you're trying to get other work done, but when 
I kludge around an infrastructure problem, what I normally do is some 
kind of ugly hack that I wouldn't want to see in a standard anyway.

Since Ralph has already declared rough consensus on this point, I think 
there's no point in discussing it further anyway.   :'}

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