Re: [BEHAVE] draft-korhonen-edns0-synthesis-flag splitted and updated
"Dan Wing" <dwing@cisco.com> Mon, 04 October 2010 18:38 UTC
Return-Path: <dwing@cisco.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 991083A6DA6 for <behave@core3.amsl.com>; Mon, 4 Oct 2010 11:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 3+gnFNcREljD for <behave@core3.amsl.com>; Mon, 4 Oct 2010 11:38:47 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 426983A7056 for <behave@ietf.org>; Mon, 4 Oct 2010 11:37:48 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAOa7qUyrR7Ht/2dsb2JhbACVXoxocakEnCmFRwSEUQ
X-IronPort-AV: E=Sophos;i="4.57,279,1283731200"; d="scan'208";a="367876637"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-1.cisco.com with ESMTP; 04 Oct 2010 18:37:28 +0000
Received: from dwingWS (dhcp-171-70-217-148.cisco.com [171.70.217.148]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o94IbSRB009453; Mon, 4 Oct 2010 18:37:28 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Cameron Byrne' <cb.list6@gmail.com>, teemu.savolainen@nokia.com
References: <18034D4D7FE9AE48BF19AB1B0EF2729F5F03931906@NOK-EUMSG-01.mgdnok.nokia.com> <AANLkTimR+jE9kcf3axDaqGA3-iY1K3AM__pCvs710WEB@mail.gmail.com>
In-Reply-To: <AANLkTimR+jE9kcf3axDaqGA3-iY1K3AM__pCvs710WEB@mail.gmail.com>
Date: Mon, 04 Oct 2010 11:37:28 -0700
Message-ID: <067601cb63f3$324e0dd0$96ea2970$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acth5nX71grk028/QwWTXC7ddzFHrgCC3HVg
Content-Language: en-us
Cc: behave@ietf.org
Subject: Re: [BEHAVE] draft-korhonen-edns0-synthesis-flag splitted and updated
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: Mon, 04 Oct 2010 18:38:49 -0000
> -----Original Message----- > From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On > Behalf Of Cameron Byrne > Sent: Friday, October 01, 2010 9:01 PM > To: teemu.savolainen@nokia.com > Cc: behave@ietf.org > Subject: Re: [BEHAVE] draft-korhonen-edns0-synthesis-flag splitted and > updated > > On Fri, Sep 24, 2010 at 8:26 AM, <teemu.savolainen@nokia.com> wrote: > > Hi Behave, > > > > We updated and split draft-korhonen-edns0-synthesis-flag into two. > > > > Now there is: > > > > draft-korhonen-edns0-synthesis-flag-01.txt that describes a EDNS0 > *option* for communicating the address format used by DNS64 in the > synthesis. This replaces the previous proposal of using EDNS0 flag > bits. This requires support from DNS64. > > > > draft-savolainen-heuristic-nat64-discovery (sorry I forgot "behave" > on the name) that describes solution where host queries AAAA record of > known IPv4-only name and then heuristically tries to resolve the > address format used by the DNS64. This does not require any support > from DNS64. > > > > I think draft-savolainen-heuristic-nat64-discovery is a very good > effort and should solve many of the IPv4 referral issues. > > Do you think it makes sense to add guidance that a /96 is the > preferred Pref64 and that aids in extracting the IPv4 address? /96 is > also the size of the WKP. I imagine that the extraction process has > to iterates to find the IPv4 address, so providing some guidance about > the use of /96 can assist in a quicker match? Any address discovery mechanism needs to support all address formats described in draft-ietf-behave-address-format. Otherwise, we would effectively profile (limit) draft-ietf-behave-address-format. The address formats described in draft-ietf-behave-address-format include a non-/96 prefix because CERNET2 made a conscious and deliberate operational decision to use a prefix other than /96 in their network. Other operators may reach that same decision. It's too early to say, as there are only a few IPv6-only networks. To aid draft-savolainen-heuristic-nat64-discovery with finding a prefix other than /96, it could perform multiple AAAA queries in order to find the prefix. In the /96 case, it can perform its work with one DNS query. -d
- [BEHAVE] draft-korhonen-edns0-synthesis-flag spli… teemu.savolainen
- Re: [BEHAVE] draft-korhonen-edns0-synthesis-flag … Cameron Byrne
- Re: [BEHAVE] draft-korhonen-edns0-synthesis-flag … teemu.savolainen
- Re: [BEHAVE] draft-korhonen-edns0-synthesis-flag … Dan Wing