Re: IPv6 DNS resolvers issue (Re: Why have we gotten away from running code?)

Margaret Wasserman <margaret@thingmagic.com> Mon, 15 August 2005 12:57 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4eXB-0003QL-D5; Mon, 15 Aug 2005 08:57:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4eX8-0003QG-0v for ietf@megatron.ietf.org; Mon, 15 Aug 2005 08:57:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01316 for <ietf@ietf.org>; Mon, 15 Aug 2005 08:57:40 -0400 (EDT)
Received: from [204.9.221.21] (helo=thingmagic.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E4f6D-0006QU-HC for ietf@ietf.org; Mon, 15 Aug 2005 09:34:00 -0400
Received: from [66.30.121.250] (account margaret HELO [86.255.28.102]) by thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 476700; Mon, 15 Aug 2005 08:50:32 -0400
Mime-Version: 1.0
Message-Id: <p062007a6bf26411c33e0@[86.255.28.102]>
In-Reply-To: <92DF04FB8C078F6F55BA3754@gloppen.hjemme.alvestrand.no>
References: <200508062307.TAA18855@ietf.org> <F7B171F5-52DD-4AAB-BFD1-CCD4203D652B@muada.com> <amwtmukvbd.fsf@nutcracker.it.su.se> <36EFCD98-9BA9-4F9E-A0B7-939972C315E3@muada.com> <BA59FC46-E6EC-4E46-A234-62B5F08482E0@let.de> <42FA13FB.3030109@garbagedump.com> <iluy879695l.fsf@latte.josefsson.org> <p062305b6bf1fe1251e4c@[150.254.225.113]> <42FB18CE.3040800@zurich.ibm.com> <12F82091-4ECD-45DE-9C68-0FB25F744C38@muada.com> <42FB5C32.7040105@motorola.com> <92DF04FB8C078F6F55BA3754@gloppen.hjemme.alvestrand.no>
Date: Mon, 15 Aug 2005 08:57:09 -0400
To: Harald Tveit Alvestrand <harald@alvestrand.no>, Alexandru Petrescu <alexandru.petrescu@motorola.com>, Iljitsch van Beijnum <iljitsch@muada.com>
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: IPv6 DNS resolvers issue (Re: Why have we gotten away from running code?)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

People may also want to read RFC 3646 which defines DHCPv6 options to 
configure a DNS resolver.

We have considered _other_ ways to automatically configure a DNS 
resolver in IPv6, but we haven't managed to reach consensus on any of 
those proposals yet.

Margaret

At 9:55 AM +0200 8/15/05, Harald Tveit Alvestrand wrote:
>Since nobody's mentioned the draft name yet, and we generally tell 
>people "go read the drafts"....
>
>  draft-ietf-dnsop-ipv6-dns-configuration-06.txt
>
>Or - "there are 3 options. We can't pick one".
>
>The document was approved by the IESG in July (but seems to be 
>waiting for an IESG note).
>
>                      Harald
>
>--On torsdag, august 11, 2005 16:09:54 +0200 Alexandru Petrescu 
><alexandru.petrescu@motorola.com> wrote:
>
>>  ljitsch van Beijnum wrote:
>>>  On 11-aug-2005, at 11:22, Brian E Carpenter wrote:
>>>
>>>>  However, what may well be missing in the mix
>>>>  is input from people who actually deploy and operate our stuff, and
>>>>  live with its limitations and quirks every day. We need to understand
>>>>  the indirect consequences of our choices: not "can it be coded and  will
>>>>  it interoperate?" but "will it drive service providers and users
>>>>  crazy?"
>>>
>>>  Lack of a way to configure DNS resolvers automatically in IPv6
>>>  continues to drive me crazy.
>>
>>  I'm not sure I get it... DHCP distributes DNS resolvers, right?   I'm
>>  not sure whether the DHCPv4 can distribute DNS IPv6 resolver addresses
>>  or is that restricted to DHCPv6.  Would be nice if both did, just like
>>  both dig/v4 and dig/v6 return both v4 and v6 addresses.  I think PPP
>>  over IPv6 doesn't do it.
>
>
>
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf


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