IETF Logo Mail Archive

[v6ops] DNSv6 Proxy !

"Rajiv Asati (rajiva)" <rajiva@cisco.com> Tue, 21 May 2013 13:14 UTC

Return-Path: <rajiva@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BECB821F8609 for <v6ops@ietfa.amsl.com>; Tue, 21 May 2013 06:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6zkDv0QvQ+2N for <v6ops@ietfa.amsl.com>; Tue, 21 May 2013 06:14:28 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id EFCE121F9772 for <v6ops@ietf.org>; Tue, 21 May 2013 06:14:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=910; q=dns/txt; s=iport; t=1369142067; x=1370351667; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=4WCmGo1IGrB1uu2H+3tIr4KvfcLASEIa1J0UMlZ9WoQ=; b=kJQ92nJnvT0h15CGxkqAH4GoAq9DvghYyg/cRxK9E9tSB1UnqiMGtUdC VkC2KE/PBIyTIK2Aw9Mp3jqtUqU16C53ry8OwS8IC4ZPhybhC0NFtDVpp gk1TX7E97Ng55MjUNEzZzk3BnmapEa6He2eAMVZEhKxAP8LTcfUeTqTkW I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMGABtym1GtJXHA/2dsb2JhbABZgwgwgnS+X4EIFm0HgiEBBDpRASoUQiUCBBuIBQyaZKEAjV+BETiCc2EDmGGQF4MPgXE1
X-IronPort-AV: E=Sophos;i="4.87,714,1363132800"; d="scan'208";a="213109600"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-6.cisco.com with ESMTP; 21 May 2013 13:14:26 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r4LDEQ2t023594 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <v6ops@ietf.org>; Tue, 21 May 2013 13:14:26 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.154]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Tue, 21 May 2013 08:14:26 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: DNSv6 Proxy !
Thread-Index: AQHOViQm+Pd3mqdCS0GWLskNYM77vpkPrrGA
Date: Tue, 21 May 2013 13:14:25 +0000
Message-ID: <B14A62A57AB87D45BB6DD7D9D2B78F0B116ACE79@xmb-rcd-x06.cisco.com>
In-Reply-To: <B14A62A57AB87D45BB6DD7D9D2B78F0B116ACDFD@xmb-rcd-x06.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [10.82.233.176]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0BB20D99A449AB468C5ADD9AEA14F5BD@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [v6ops] DNSv6 Proxy !
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 13:14:33 -0000

I just realized that neither RFC6204, nor the bis draft
(http://tools.ietf.org/html/draft-ietf-v6ops-ipv6-cpe-router-bis-01#section
-5.1) have added any specifics for what IPv6 address should the CPE router
use while executing the DNS proxy function (if enabled).

Should it use the IPv6 address assigned to its WAN interface (which is to
be used for CPE management, really) via DHCPv6 IA_NA or SLAAC, or the
address assigned to its LAN interface via DHCPv6 PD ?

I happen to have an affinity to using the latter. Perhaps, a discussion is
worth here.

(Please ignore the previous email, which was a premature send)

Cheers,
Rajiv


PS: Just noticed a nit in the section 5.1, btw:

//If the service provider specifies one
or more DNS resolvers in DHCP configuration options, the CE
router SHOULD forward all non-local DNS queries unchanged to
those servers.

//

s/server/resolver

v2.23.0 | Report a Bug | By Email