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

Mika Liljeberg <mika.liljeberg@welho.com> Sat, 22 February 2003 12:22 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 HAA09675 for <dhcwg-archive@odin.ietf.org>; Sat, 22 Feb 2003 07:22:30 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1MCU3312459 for dhcwg-archive@odin.ietf.org; Sat, 22 Feb 2003 07:30:03 -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 h1MCU3p12456 for <dhcwg-web-archive@optimus.ietf.org>; Sat, 22 Feb 2003 07:30:03 -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 HAA09670 for <dhcwg-web-archive@ietf.org>; Sat, 22 Feb 2003 07:21: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 h1MCSSp12423; Sat, 22 Feb 2003 07:28:28 -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 h1MB6Zp08271 for <dhcwg@optimus.ietf.org>; Sat, 22 Feb 2003 06:06:35 -0500
Received: from devil.pp.htv.fi (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08676 for <dhcwg@ietf.org>; Sat, 22 Feb 2003 05:58:33 -0500 (EST)
Received: from devil.pp.htv.fi (localhost [127.0.0.1]) by devil.pp.htv.fi (8.12.7/8.12.7/Debian-2) with ESMTP id h1MB31aj027243; Sat, 22 Feb 2003 13:03:01 +0200
Received: (from liljeber@localhost) by devil.pp.htv.fi (8.12.7/8.12.7/Debian-2) id h1MB30t3027242; Sat, 22 Feb 2003 13:03:00 +0200
X-Authentication-Warning: devil.pp.htv.fi: liljeber set sender to mika.liljeberg@welho.com using -f
Subject: RE: [dhcwg] Re: WG last call ondraft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt
From: Mika Liljeberg <mika.liljeberg@welho.com>
To: BELOEIL Luc FTRD/DMI/CAE <luc.beloeil@rd.francetelecom.com>
Cc: Alain Durand <Alain.Durand@Sun.COM>, Pekka Savola <pekkas@netcore.fi>, Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org, ipng@sunroof.eng.sun.com, namedroppers@ops.ietf.org
In-Reply-To: <C691E039D3895C44AB8DFD006B950FB41BCD63@lanmhs50.rd.francetelecom.fr>
References: <C691E039D3895C44AB8DFD006B950FB41BCD63@lanmhs50.rd.francetelecom.fr>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1045911780.27180.5.camel@devil>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2
Date: Sat, 22 Feb 2003 13:03:00 +0200
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

On Fri, 2003-02-21 at 11:07, BELOEIL Luc FTRD/DMI/CAE wrote: 
> > 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?

I think this is a good idea.

> I feel ill at ease with such a solution. How your DHCPv6 client, running
> a node, is aware that there is an IPv4 stack enable on that same node ?
> If it is not, v4-mapped addresses could be harmfull, couldn't they ?

Not really. Why would a network administrator advertise IPv4 DNS servers
on a network with IPv6 only nodes?

Even if there are some IPv6 only nodes on the network, the host resolver
on those nodes will simply try to use the IPv4-mapped address and fail,
and move on the the next one as it would do with any malfunctioning DNS
server.

I don't think the DHCP client has to care whether IPv4 is enabled on the
node (although it could attempt to check that). All it has to do is
configure the DNS addresses and let the host resolver take it from
there.

	MikaL

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