Re: [sunset4] An IPv4 sunset problem (?)

Simon Perreault <simon.perreault@viagenie.ca> Wed, 22 August 2012 16:56 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: sunset4@ietfa.amsl.com
Delivered-To: sunset4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6541721F85B1 for <sunset4@ietfa.amsl.com>; Wed, 22 Aug 2012 09:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.529
X-Spam-Level:
X-Spam-Status: No, score=-2.529 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mIm2Ldm7bHrn for <sunset4@ietfa.amsl.com>; Wed, 22 Aug 2012 09:56:12 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id E997D21F84C8 for <sunset4@ietf.org>; Wed, 22 Aug 2012 09:56:11 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:6ca5:e542:5b44:7b06]) by jazz.viagenie.ca (Postfix) with ESMTPSA id EE501425F4; Wed, 22 Aug 2012 12:56:10 -0400 (EDT)
Message-ID: <50350F2A.70607@viagenie.ca>
Date: Wed, 22 Aug 2012 12:56:10 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0
MIME-Version: 1.0
To: mohamed.boucadair@orange.com
References: <5035007C.2070809@viagenie.ca> <94C682931C08B048B7A8645303FDC9F36E52298D9D@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E52298D9D@PUEXCB1B.nanterre.francetelecom.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: "sunset4@ietf.org" <sunset4@ietf.org>
Subject: Re: [sunset4] An IPv4 sunset problem (?)
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: sunset4 working group discussion list <sunset4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sunset4>, <mailto:sunset4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sunset4>
List-Post: <mailto:sunset4@ietf.org>
List-Help: <mailto:sunset4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sunset4>, <mailto:sunset4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 16:56:12 -0000

Le 2012-08-22 12:54, mohamed.boucadair@orange.com a écrit :
> This issue has been already documented in depth in http://tools.ietf.org/html/draft-ietf-behave-nat64-learn-analysis-03.

This corresponds to the first solution I described. It requires that all 
hosts be modified to be able to discover the NAT64 prefix. This is often 
impractical.

Thanks,
Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca