Re: [BEHAVE] I-D Action: draft-wing-behave-dhcpv6-reconfigure-00.txt

"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Sun, 06 November 2011 10:25 UTC

Return-Path: <tireddy@cisco.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94B3521F8494 for <behave@ietfa.amsl.com>; Sun, 6 Nov 2011 02:25:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.598
X-Spam-Level:
X-Spam-Status: No, score=-8.598 tagged_above=-999 required=5 tests=[AWL=2.001, 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 8iEKLSe56Zy7 for <behave@ietfa.amsl.com>; Sun, 6 Nov 2011 02:25:38 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id B055721F848E for <behave@ietf.org>; Sun, 6 Nov 2011 02:25:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=tireddy@cisco.com; l=2227; q=dns/txt; s=iport; t=1320575137; x=1321784737; h=mime-version:content-transfer-encoding:subject:date: message-id:references:from:to:cc; bh=0bYIU7r0RjV1IQdlb1niokXn3FxTqCLV4Da6qxz6Wxk=; b=SDHuOc1N7aFTkYTqahxWoo4m0T5g8B2WB0SQHRjzPu4k9OX0YJEzpuCM bd5NYCYKGFcEKRJOsYbYbYIaO74lvMKudsrz0en3CdWXlGpho3EJYMIJ9 LCTQuLu3ja+2J/4YeXTDc0R4g6tDOl1UOO+7JCwz1KFom6abBMx2pRDFq E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAPpftk5Io8UR/2dsb2JhbAA4CqoSgQWBcgEBAQEDEgEdCj8OAgIBCBEDAQILBhgGARoGLggBAQQBCggIGp1rAZ0zAoV4gk5jBIgJkVKFBIc2
X-IronPort-AV: E=Sophos;i="4.69,464,1315180800"; d="scan'208";a="59267354"
Received: from bgl-core-2.cisco.com ([72.163.197.17]) by ams-iport-2.cisco.com with ESMTP; 06 Nov 2011 10:25:34 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pA6APXFx012706; Sun, 6 Nov 2011 10:25:33 GMT
Received: from xmb-bgl-41b.cisco.com ([72.163.129.217]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 6 Nov 2011 15:55:33 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 06 Nov 2011 15:55:32 +0530
Message-ID: <454A16E4DA86094EB66BB2C1DBBBC018061954AA@XMB-BGL-41B.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [BEHAVE] I-D Action: draft-wing-behave-dhcpv6-reconfigure-00.txt
Thread-Index: Acya8yvU1ifJQkOLH0CqHvi+iEm3tAAA/pbgAF2+j7A=
References: <20111102005048.1D2F6166A615@drugs.dv.isc.org> <CAD9E231.12668%praspati@cisco.com>
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: marka@isc.org, behave@ietf.org
X-OriginalArrivalTime: 06 Nov 2011 10:25:33.0363 (UTC) FILETIME=[6A7A3030:01CC9C6E]
Cc: "Prashanth Patil (praspati)" <praspati@cisco.com>, "Dan Wing (dwing)" <dwing@cisco.com>
Subject: Re: [BEHAVE] I-D Action: draft-wing-behave-dhcpv6-reconfigure-00.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 06 Nov 2011 10:25:38 -0000

The advantage with the proposal suggested in the draft is that it
requires no changes to host and DNS64 server. The idea is to provide a
framework where, based on changes in host or network characteristics,
Relay agents can dynamically inform the DHCPv6 server to update the host
with new/updated configuration information. In addition, the concept of
informing the DHCPv6 server by the network could be extended to other
use cases as well.
Just like EDNS0 draft-boucadair-behave-dns-a64-02 proposes a model where
A64 record for IPv4-Embedded IPv6 address is used so as to distinguish
from native IPv6 address using AAAA records. Our proposed draft  ensures
that, as per RFC 3484, IPv6 address list (not IPv4-embedded IPv6)
followed by IPv4 addresses are provided so that native IPv6 is given
higher priority over IPv4. Since IPv4-embedded IPv6 addresses are not
provided - there is no need for destination address selection algorithm
to pick IPv4 over IPv4-embedded IPv6 addresses, which would require the
policy table to be updated with network's IPv6/IPv4 translator's prefix
or well-known prefix 64:FF9B::/96 as the lowest Precedence in the
address selection rules.

--Tiru.

------ Forwarded Message
From: Mark Andrews <marka@isc.org>
Date: Wed, 02 Nov 2011 11:50:47 +1100
To: Dan Wing <dwing@cisco.com>
Cc: 'Brian E Carpenter' <brian.e.carpenter@gmail.com>, 'Prashanth Patil'
<praspati@cisco.com>, <behave@ietf.org>
Subject: Re: [BEHAVE] I-D Action:
draft-wing-behave-dhcpv6-reconfigure-00.txt


The best way to identify a mapped response is for the DNS64 server
to flag it and as *every* IPv6 node is supposed to be EDNS capable
a EDNS option can be used to signal this.

getaddrinfo would just filter DNS64 responses when it is asking for
both address families.  Dual stack applications would just see the
IPv4 addresses.  IPv6 only apps would see the mapped addresses.

Recursive servers talking to forwarders would set the option on
AAAA queries and record the respone along with any AAAA records.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

------ End of Forwarded Message