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

Pekka Savola <pekkas@netcore.fi> Fri, 21 February 2003 11:21 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 GAA26308 for <dhcwg-archive@odin.ietf.org>; Fri, 21 Feb 2003 06:21:08 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1LBSA814506 for dhcwg-archive@odin.ietf.org; Fri, 21 Feb 2003 06:28:10 -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 h1LBSAp14503 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 21 Feb 2003 06:28:10 -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 GAA26237 for <dhcwg-web-archive@ietf.org>; Fri, 21 Feb 2003 06:20:37 -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 h1LBQkp14244; Fri, 21 Feb 2003 06:26:46 -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 h1L6Tkp16919 for <dhcwg@optimus.ietf.org>; Fri, 21 Feb 2003 01:29:46 -0500
Received: from netcore.fi (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10548 for <dhcwg@ietf.org>; Fri, 21 Feb 2003 01:22:18 -0500 (EST)
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id h1L6Pvm20135; Fri, 21 Feb 2003 08:25:57 +0200
Date: Fri, 21 Feb 2003 08:25:57 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: Alain Durand <Alain.Durand@Sun.COM>
cc: Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org, ipng@sunroof.eng.sun.com, namedroppers@ops.ietf.org
Subject: Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt
In-Reply-To: <EB7A94BC-4530-11D7-BCB3-00039376A6AA@sun.com>
Message-ID: <Pine.LNX.4.44.0302210820240.20008-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
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>

On Thu, 20 Feb 2003, Alain Durand wrote:
> On Thursday, February 20, 2003, at 12:03  PM, Ralph Droms wrote:
> > If it's unclear, then we should edit the document to explicitly 
> > identify the addresses as IPv6 addresses.
> >
> > This option is intended to return IPv6 configuration information.  
> > IPv4 addresses for DNS resolvers should be provided through DHCPv4...

I symphatize with this -- there are some uses to have DHCPv6 return IPv4
addresses too -- but the result would just make the dnsconfig option more
complex for little benefit.  Let's face it: if you deploy DHCPv6, you
really should have long since deployed IPv6-enabled nameservers too.

So, I think clarifying the scope to do only IPv6 seems like the best 
option by far.
 
> Now, let's say that this is the case for DHCP, what should a node that
> act both as a DHCPv4 and DHCPv6 client do when it will be returned two
> lists of recursive DNS serves, one IPv4 via DHCPv4 and one IPv6 via
> DHCPv6. Which one should take priority?

Implementation decision, but I guess typically the results of the 
latest query take precedence.  I don't see a problem here, myself.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

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