Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt
Ralph Droms <rdroms@cisco.com> Fri, 21 February 2003 12:55 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 HAA28198 for <dhcwg-archive@odin.ietf.org>; Fri, 21 Feb 2003 07:55:38 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1LD2gK20720 for dhcwg-archive@odin.ietf.org; Fri, 21 Feb 2003 08:02:42 -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 h1LD2gp20717 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 21 Feb 2003 08:02:42 -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 HAA28193 for <dhcwg-web-archive@ietf.org>; Fri, 21 Feb 2003 07:55:06 -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 h1LD19p20654; Fri, 21 Feb 2003 08:01:09 -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 h1LD07p20578 for <dhcwg@optimus.ietf.org>; Fri, 21 Feb 2003 08:00:07 -0500
Received: from rtp-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28127 for <dhcwg@ietf.org>; Fri, 21 Feb 2003 07:52:31 -0500 (EST)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by rtp-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h1LCuKNh003586; Fri, 21 Feb 2003 07:56:21 -0500 (EST)
Received: from rdroms-w2k.cisco.com (dhcp-161-44-149-251.cisco.com [161.44.149.251]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id HAA13252; Fri, 21 Feb 2003 07:56:20 -0500 (EST)
Message-Id: <4.3.2.7.2.20030221074927.03e89ed8@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 21 Feb 2003 07:56:20 -0500
To: dhcwg@ietf.org, ipng@sunroof.eng.sun.com, namedroppers@ops.ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt
In-Reply-To: <3A56AD0A-4567-11D7-A383-00039376A6AA@sun.com>
References: <Pine.LNX.4.44.0302210820240.20008-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>
Regarding unpredictable, difficult to debug behavior (see end of quoted text)... Shouldn't the host receive the same answer to a DNS query, regardless of the resolver to which the query is sent? If so, the order in which resolvers are used by the host shouldn't matter. What is done today in the deployed IPv6 world in a host that has both an IPv6 stack and an IPv4 stack, and a manually configured list of DNS resolvers? Is it allowed to mix together IPv6 and IPv4 addresses for resolvers? Is that configuration actually used? Does the host have two lists: one for IPv6 and one for IPv4? Suppose the host only has an IPv6 stack but both IPv6 and IPv4 addresses in its list of DNS resolvers? I'm hoping we can get some real-world deployment experience injected into the conversation... - Ralph At 10:39 PM 2/20/2003 -0800, Alain Durand wrote: >On Thursday, February 20, 2003, at 10:25 PM, Pekka Savola wrote: > >>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. > > >Some may scream at this idea, but couldn't we pass an IPv4-mapped address >in there? The DHCPv6 client could recognize this special format >to mean this is actually a v4 address? > > >> >>>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. > >Unpredictable behavior. Difficult to debug. > > - Alain. > > >-- >to unsubscribe send a message to namedroppers-request@ops.ietf.org with >the word 'unsubscribe' in a single line as the message text body. >archive: <http://ops.ietf.org/lists/namedroppers/> _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] WG last call on draft-ietf-dhc-dhcpv6-opt… Ralph Droms
- [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6… Pekka Savola
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Ralph Droms
- [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6… Peter Koch
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Robert Elz
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… JINMEI Tatuya / 神明達哉
- [dhcwg] WG last call on draft-ietf-dhc-dhcpv6-opt… Ralph Droms
- [dhcwg] WG last call on draft-ietf-dhc-dhcpv6-opt… Ralph Droms
- [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6… Alain Durand
- [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6… Ralph Droms
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Ralph Droms
- Re: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6… Ted Lemon
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Alain Durand
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Alain Durand
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Pekka Savola
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Pekka Savola
- [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6… JINMEI Tatuya / 神明達哉
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Ralph Droms
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Robert Elz
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Ted Lemon
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Alain Durand
- [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6… Rob Austein
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Mika Liljeberg
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Pekka Savola
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Mika Liljeberg
- [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6… Mika Liljeberg
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Bill Manning
- IPv4-mapped API [Re: [dhcwg] Re: WG last call on … Mika Liljeberg
- [dhcwg] RE: WG last call on draft-ietf-dhc-dhcpv6… juha.wiljakka
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Ralph Droms
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Michael Richardson
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… Ted Lemon
- Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dh… David Terrell