IETF Logo Mail Archive

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

Ted Lemon <Ted.Lemon@nominum.com> Fri, 21 February 2003 17:48 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 MAA08857 for <dhcwg-archive@odin.ietf.org>; Fri, 21 Feb 2003 12:48:39 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1LHtnD08438 for dhcwg-archive@odin.ietf.org; Fri, 21 Feb 2003 12:55:49 -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 h1LHtnp08435 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 21 Feb 2003 12:55:49 -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 MAA08825 for <dhcwg-web-archive@ietf.org>; Fri, 21 Feb 2003 12:48:08 -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 h1LHsFp08390; Fri, 21 Feb 2003 12:54:15 -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 h1LHr5p08294 for <dhcwg@optimus.ietf.org>; Fri, 21 Feb 2003 12:53:05 -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 MAA08579 for <dhcwg@ietf.org>; Fri, 21 Feb 2003 12:45:24 -0500 (EST)
Received: from nominum.com (a21.pm3-67.theriver.com [206.25.48.213]) by toccata.fugue.com (8.11.6/8.6.11) with ESMTP id h1LHk3N26412; Fri, 21 Feb 2003 11:46:03 -0600 (CST)
Date: Fri, 21 Feb 2003 10:48:44 -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: Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org, ipng@sunroof.eng.sun.com, namedroppers@ops.ietf.org
To: Robert Elz <kre@munnari.OZ.AU>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <24074.1045835772@munnari.OZ.AU>
Message-Id: <B89DDCB8-45C4-11D7-A12D-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

I'm not sure why you would have a deployed DHCPv6 server and not deploy 
a DNS resolver that listens to requests on an IPv6 socket.   Can 
anybody give a rationale for this?   Has anybody done this?   Was it a 
problem?

In principle, there is nothing that would prevent you from configuring 
your DHCPv6 server to return an encapsulated IPv4 address, but as 
various people have said, this might produce a not-useful result.

I think that the idea of having a DNS resolver priority list is a 
reasonable answer to the problem of "what do we do if we have both IPv4 
and IPv6 addresses for resolvers," but I also think that it's a 
complicated answer, and I do not believe that the problem it solves is 
a compelling one.   It adds significant special-case code to the DHCP 
client, and I don't think it produces a useful benefit.

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

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