[BEHAVE] Two minor comments for draft-wing-behave-dns64-config-02
Xu Xiaohu <xuxh@huawei.com> Wed, 03 March 2010 07:14 UTC
Return-Path: <xuxh@huawei.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0CB063A8C3F for <behave@core3.amsl.com>; Tue, 2 Mar 2010 23:14:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.454
X-Spam-Level:
X-Spam-Status: No, score=-0.454 tagged_above=-999 required=5 tests=[AWL=2.145, BAYES_00=-2.599]
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 bx1MdxwvKCjB for <behave@core3.amsl.com>; Tue, 2 Mar 2010 23:14:39 -0800 (PST)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id A2A0F3A8C3A for <behave@ietf.org>; Tue, 2 Mar 2010 23:14:38 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYP003J22R0WB@szxga02-in.huawei.com> for behave@ietf.org; Wed, 03 Mar 2010 15:13:49 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYP0001W2R02F@szxga02-in.huawei.com> for behave@ietf.org; Wed, 03 Mar 2010 15:13:48 +0800 (CST)
Received: from HUAWEIE75F8F11 ([10.111.13.9]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KYP0096V2QY8A@szxml04-in.huawei.com> for behave@ietf.org; Wed, 03 Mar 2010 15:13:48 +0800 (CST)
Date: Wed, 03 Mar 2010 15:13:46 +0800
From: Xu Xiaohu <xuxh@huawei.com>
To: 'Dan Wing' <dwing@cisco.com>
Message-id: <00b401cabaa1$10c976a0$090d6f0a@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="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: Acq6oRB/KZVcHoX8QGuSqhmPiCfnjg==
Cc: behave@ietf.org
Subject: [BEHAVE] Two minor comments for draft-wing-behave-dns64-config-02
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2010 07:14:41 -0000
Hi Dan,
Two minor comments are as follows:
o If separate networks operate DHCPv4 and DHCPv6 (e.g., as with
Dual-Stack Lite where the ISP operates _DHCPv4_ and the customer
premise router operates _DHCPv6_), it is likely impossible for the
DHCPv4 and DHCPv6 servers to communicate necessary information
with each other.
Shouldn't the above two marked terms exchange their places?
o To avoid unnecessary traffic through a translator, it is desirable to
configure IPv4-only and dual-stack hosts with a 'normal' DNS
recursive resolver.
I wonder whether it is necessary to mention the IPv4-only host here since an
IPv4-only host will not perform an AAAA query in normal cases. Even it does,
the obtained AAAA RR will not be used in communications. Am I wrong?
Best wishes,
Xiaohu