Re: [Softwires] draft-guo-softwire-6rd-ipv6-config-00
Xu Xiaohu <xuxh@huawei.com> Thu, 22 July 2010 01:13 UTC
Return-Path: <xuxh@huawei.com>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB2553A6A7B for <softwires@core3.amsl.com>; Wed, 21 Jul 2010 18:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.608
X-Spam-Level: *
X-Spam-Status: No, score=1.608 tagged_above=-999 required=5 tests=[AWL=1.418, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K6PWl7NalWcM for <softwires@core3.amsl.com>; Wed, 21 Jul 2010 18:13:00 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 49E643A6A7C for <softwires@ietf.org>; Wed, 21 Jul 2010 18:12:59 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L5X00E5NQ234G@szxga04-in.huawei.com> for softwires@ietf.org; Thu, 22 Jul 2010 09:13:15 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L5X00HMJQ23Z6@szxga04-in.huawei.com> for softwires@ietf.org; Thu, 22 Jul 2010 09:13:15 +0800 (CST)
Received: from x41208c ([10.110.98.89]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5X0007XQ23M0@szxml04-in.huawei.com> for softwires@ietf.org; Thu, 22 Jul 2010 09:13:15 +0800 (CST)
Date: Thu, 22 Jul 2010 09:14:20 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <C86C7484.3004D%yiu_lee@cable.comcast.com>
To: "'Lee, Yiu'" <Yiu_Lee@Cable.Comcast.com>, softwires@ietf.org
Message-id: <003901cb293b$3690ce20$59626e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="gb2312"
Content-transfer-encoding: quoted-printable
Thread-index: Acso3FjsBOgV7Fw5OkKfL2c7aFWtngAWy2fA
Subject: Re: [Softwires] draft-guo-softwire-6rd-ipv6-config-00
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jul 2010 01:13:01 -0000
Hi Yiu, Your observation is correct. DNS Proxy [RFC5625] together with IPv6 Router Advertisement Option for DNS [RFC5006] can still be used in case that DNS server is the only configuration information which is needed by the IPv6-only hosts. One minor benefit of the DHCPv4 option for IPv6 DNS server (see Section 4) over the DNS proxy approach is: the 6rd domain operator could deploy separate DNS servers for A RR resolution and AAAA RR resolution respectively. Anyway, it is the DHCPv4 option for DHCPv6 servers (see Section 3) that we are mainly focusing on in this draft. With this new DHCPv4 option, the IPv6 only hosts could obtain other configuration information besides DNS servers, such as SIP servers and NTP servers. Best wishes, Xiaohu > -----邮件原件----- > 发件人: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] 代 表 > Lee, Yiu > 发送时间: 2010年7月21日 21:55 > 收件人: softwires@ietf.org > 主题: [Softwires] draft-guo-softwire-6rd-ipv6-config-00 > > Hi Dayong and Xiaohu, > > I got a question for Section 4. Is there any particular reason why the > 6RD-CE or the IPv6 must know the IPv6 address of a DNS server? The 6RD-CE > can act as a DNS proxy advertise itself as DNS server in RA to the v6 host. > Then the 6RD-CE proxies the v6 dns messages from the v6 host to a v4 DNS > server in the network. > > Thanks, > Yiu >