Re: [v4v6interim] The NAT64 prefix
Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 01 October 2008 21:08 UTC
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7FA03A68A1; Wed, 1 Oct 2008 14:08:14 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EE673A6767 for <v4v6interim@core3.amsl.com>; Wed, 1 Oct 2008 14:08:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level:
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 X2Q8NM+ZAmAV for <v4v6interim@core3.amsl.com>; Wed, 1 Oct 2008 14:08:12 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by core3.amsl.com (Postfix) with ESMTP id A6F183A68E6 for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 14:08:12 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id n4so376647wag.5 for <v4v6interim@ietf.org>; Wed, 01 Oct 2008 14:08:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=UErRPPMAibzogxwUHdrxnRZhmv3SCLTJII28eTSKaX8=; b=d0zgonKMugqLAQLq7Zv8HW7Wqo1+v+yWPBLe8ODhKhx0DGTFE4RfUAnHC1gFGZQNCV UNIU0Ef87KJtEmeBuj8WvctjnjxDa8+GX2uRyX5mvztMw4XbkeIcdaROZ0TFPv+67Wje //Q4pqK7Tx47m9yVWVJCz/wxblfH6cQOFqmEg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=uiWKuXwwlR+V9+CslKtLWQecf6DmgnxgtAqCJVcFo5dZrHLZ0o6nyYQAoPvANK4l6E ZLkpJNizNhw79twzL6R5ImE1tSiM99sqPPNkg2QdEXBJPsT3IRsGlchzahHSznm4ssIF 6Uigcv6/sGD4A+og1iVVb+kaRyCZbckCeKk+I=
Received: by 10.114.182.1 with SMTP id e1mr9856765waf.143.1222895316320; Wed, 01 Oct 2008 14:08:36 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id l37sm1748563waf.23.2008.10.01.14.08.33 (version=SSLv3 cipher=RC4-MD5); Wed, 01 Oct 2008 14:08:35 -0700 (PDT)
Message-ID: <48E3E6D0.2050100@gmail.com>
Date: Thu, 02 Oct 2008 10:08:32 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
In-Reply-To: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6 coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org
Iljitsch, On 2008-10-02 05:24, Iljitsch van Beijnum wrote: > There are several advantages of having a well known prefix for > NAT-PT/NAT64 or even DS-lite. For the former, synthetic AAAA records are > no longer necessary and can be ignored by updated hosts, for the latter > there is no longer any need have a configuration mechanism. Upgraded > IPv6 hosts can simply start sending packets to IPv4 destinations to the > translator when they detect that they don't have actual IPv4 > connectivity, rather than depend on external entities to provide > configuration information, in AAAA records or explicitly. An additional > benefit would be that NAT64 could even support IPv4 applications this way. > > On the other hand, there are operational benefits to having a > configurable prefix: this makes it possible to direct traffic that is to > be translated to a specific translator without routing contortions. > > What I suggest is that we do both. We present a well known prefix of a > combined NAT-PT/NAT64/DS-lite translator to transport protocols and > applications, but we allow packets destined for that prefix to have > their destination address rewritten into a specific prefix. Because the > packets are translated later anyway, this causes no problems. Also, if > we allow longest match first rules for the well known to specific prefix > translation table, this makes it very easy to support private > translators for RFC 1918 destinations along with global translators for > global IPv4 destinations. I agree with all that, but it's important to add a very strong set of operational recommendations on how the two prefixes are advertised in both internal and external routing. Exactly as with 6to4 and Teredo relays, if the prefixes are announced outside the appropriate scope, all sorts of undesirable traffic patterns (and black holes) will result. Brian _______________________________________________ v4v6interim mailing list v4v6interim@ietf.org https://www.ietf.org/mailman/listinfo/v4v6interim
- Re: [v4v6interim] The NAT64 prefix Hiroshi MIYATA
- [v4v6interim] The NAT64 prefix Iljitsch van Beijnum
- Re: [v4v6interim] The NAT64 prefix Arifumi Matsumoto
- Re: [v4v6interim] The NAT64 prefix Fred Baker
- Re: [v4v6interim] The NAT64 prefix Hiroshi MIYATA
- Re: [v4v6interim] The NAT64 prefix Fred Baker
- Re: [v4v6interim] The NAT64 prefix Arifumi Matsumoto
- Re: [v4v6interim] The NAT64 prefix Hiroshi MIYATA
- Re: [v4v6interim] The NAT64 prefix Hiroshi MIYATA
- Re: [v4v6interim] The NAT64 prefix Brian E Carpenter
- Re: [v4v6interim] The NAT64 prefix Hiroshi MIYATA
- Re: [v4v6interim] The NAT64 prefix Iljitsch van Beijnum
- Re: [v4v6interim] The NAT64 prefix Arifumi Matsumoto
- Re: [v4v6interim] The NAT64 prefix Fred Baker
- Re: [v4v6interim] The NAT64 prefix Brian E Carpenter