[dhcwg] New draft: IPv6 Host Configuration of Recursive DNS Server

juha.wiljakka@nokia.com Thu, 03 June 2004 10:47 UTC

Received: from megatron.ietf.org (megatron.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29956; Thu, 3 Jun 2004 06:47:04 -0400 (EDT)
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVpWI-0007Ci-2Q; Thu, 03 Jun 2004 06:32:22 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVksJ-00074W-EP for dhcwg@megatron.ietf.org; Thu, 03 Jun 2004 01:34:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24593 for <dhcwg@ietf.org>; Thu, 3 Jun 2004 01:34:31 -0400 (EDT)
From: juha.wiljakka@nokia.com
Received: from ietf-mx.ietf.org ([] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVks2-0004PW-AM for dhcwg@ietf.org; Thu, 03 Jun 2004 01:34:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVkqe-0003qX-00 for dhcwg@ietf.org; Thu, 03 Jun 2004 01:33:04 -0400
Received: from mgw-x2.nokia.com ([]) by ietf-mx with esmtp (Exim 4.12) id 1BVkpm-0003Pr-00; Thu, 03 Jun 2004 01:32:10 -0400
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com []) by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i535W5v22772; Thu, 3 Jun 2004 08:32:05 +0300 (EET DST)
X-Scanned: Thu, 3 Jun 2004 08:31:58 +0300 Nokia Message Protector V1.3.30 2004040916 - RELEASE
Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i535VwBh003648; Thu, 3 Jun 2004 08:31:58 +0300
Received: from mgw-int1.ntc.nokia.com ( by esdks003.ntc.nokia.com 000u5HkY; Thu, 03 Jun 2004 08:31:56 EEST
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com []) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i535VtH27646; Thu, 3 Jun 2004 08:31:55 +0300 (EET DST)
Received: from esebe005.NOE.Nokia.com ([]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Thu, 3 Jun 2004 08:31:38 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 03 Jun 2004 08:31:37 +0300
Message-ID: <245DBCAEEC4F074CB77B3F984FF9834F020CE3D7@esebe005.ntc.nokia.com>
Thread-Topic: IPv6 Host Configuration of Recursive DNS Server
Thread-Index: AcRJB7WgdazXpx0ASMSxnG9HUoRN4QAIXcJg
To: ipv6@ietf.org, v6ops@ops.ietf.org, dhcwg@ietf.org
X-OriginalArrivalTime: 03 Jun 2004 05:31:38.0054 (UTC) FILETIME=[0AB99660:01C4492C]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Cc: paul@etri.re.kr
Subject: [dhcwg] New draft: IPv6 Host Configuration of Recursive DNS Server
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi all,

(Firstly, my apologies for cross-posting)

Forwarding Paul's e-mail also on IPv6, v6ops and dhc lists. Your comments on the draft are appreciated on the dnsop mailing list  dnsop@lists.uoregon.edu  (no cross-posting, please).

	-Juha W.-

-----Original Message-----
From: dnsop-v6conf-bounces@nominum.com
[mailto:dnsop-v6conf-bounces@nominum.com]On Behalf Of ext Jaehoon Paul
Sent: 03 June, 2004 04:10
To: dnsop@lists.uoregon.edu
Cc: IPv6 DNS Configuration
Subject: IPv6 Host Configuration of Recursive DNS Server

Hello DNSOP members,

As you know, a new draft has been published for IPv6 Host Configuration of DNS Server Information Approaches:

For a long time, DNS Discovery has been discussed at both IPv6 and DNSOP working groups.
The long discussion seems to be resolved through this draft.

In this draft, three approaches are suggested: (a) RA option, (b) DHCPv6 option, and
(c) Well-known anycast addresses for Recursive DNS Servers.
We, authors, used "DNS Configuration" instead of "DNS Discovery" because recursive DNS server address is 
only configured in IPv6 host, not generating DNS server address like in IPv6 address autoconfiguration.

This draft focuses on describing the attributes of three approaches and suggesting four applicable scenarios:
(a) ISP network, (b) Enterprise network, (c) 3GPP network, (d) Unmanaged network.

Through your review and comments, this will be published as Informational RFC according to our milestones.
IMHO, if necessary, the drafts of two other approaches except DHCPv6 option will be developed into separate RFCs.


IPv6 DNS Configuration Design Team.

Jaehoon Paul Jeong (Research Engineer)
TEL. +82-42-860-1664
Mobile +82-16-711-1765
161 Gajeong-dong Yuseong-gu, Daejeon 305-350, Korea
NGI Standardization Research Team/PEC/ETRI
Homepage: http://www.adhoc.6ants.net/~paul

dhcwg mailing list