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

Marc Blanchet <marc.blanchet@viagenie.ca> Wed, 22 August 2012 16:59 UTC

Return-Path: <marc.blanchet@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 3FA9E21F8630 for <sunset4@ietfa.amsl.com>; Wed, 22 Aug 2012 09:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level:
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=-0.533, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 2TbQEjTfZZ0v for <sunset4@ietfa.amsl.com>; Wed, 22 Aug 2012 09:59:05 -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 8072621F8629 for <sunset4@ietf.org>; Wed, 22 Aug 2012 09:59:05 -0700 (PDT)
Received: from [IPv6:2620::230:c000:957f:fb4a:6ce6:24d8] (unknown [IPv6:2620:0:230:c000:957f:fb4a:6ce6:24d8]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 64D4B4161B; Wed, 22 Aug 2012 12:58:58 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="iso-8859-1"
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E52298D9D@PUEXCB1B.nanterre.francetelecom.fr>
Date: Wed, 22 Aug 2012 12:58:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4162EB5D-6A40-4C23-A53B-1C1BA7D4CF5F@viagenie.ca>
References: <5035007C.2070809@viagenie.ca> <94C682931C08B048B7A8645303FDC9F36E52298D9D@PUEXCB1B.nanterre.francetelecom.fr>
To: mohamed.boucadair@orange.com
X-Mailer: Apple Mail (2.1278)
Cc: Simon Perreault <simon.perreault@viagenie.ca>, "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:59:06 -0000

Le 2012-08-22 à 12:54, <mohamed.boucadair@orange.com> a écrit :

> Hi Simon,
> 
> This issue has been already documented in depth in http://tools.ietf.org/html/draft-ietf-behave-nat64-learn-analysis-03.
> 

maybe, but for a document (gap analysis) that should state potential issues when turning IPv4 off in a network, I think that issue (two sets of stacks in an IPv6-only network with NAT64)  is relevant to be listed.  

Maybe it is a short paragraph that points to the others (such as the one you are referencing to), so we avoid multiple discussions. I leave it to the editors to review the referenced texts and write whatever is appropriate.

Marc.

> I'm not sure if there is a value to re-discuss this point in the gap analysis document.
> 
> Cheers,
> Med
> 
> 
>> -----Message d'origine-----
>> De : sunset4-bounces@ietf.org 
>> [mailto:sunset4-bounces@ietf.org] De la part de Simon Perreault
>> Envoyé : mercredi 22 août 2012 17:54
>> À : sunset4@ietf.org
>> Objet : [sunset4] An IPv4 sunset problem (?)
>> 
>> Sunsetters,
>> 
>> Recently there has been discussion in v6ops about a problem 
>> that arises 
>> when a network infrastructure featuring NAT64+DNS64 is used by 
>> IPv6-only 
>> as well as dual-stack hosts. The problem is that you want the 
>> IPv6-only 
>> hosts to use the DNS64 but not the dual-stack hosts.
>> 
>> This is a well-known problem that has been discussed in behave and for 
>> which there is a solution that involves the hosts 
>> (draft-ietf-behave-nat64-discovery-heuristic), and another 
>> that involves 
>> only the network (provision different DNS resolver addresses to 
>> IPv6-only and dual-stack hosts). Those solutions may not apply in many 
>> cases: the first solution requires that all hosts be modified, 
>> while the 
>> second solution requires that one be able to differentiate IPv6-only 
>> from dual-stack hosts.
>> 
>> Question for the WG: should this be discussed in 
>> draft-ietf-sunset4-gapanalysis? If so, we would appreciate additional 
>> input. Additional solution ideas would also be appreciated...
>> 
>> 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
>> _______________________________________________
>> sunset4 mailing list
>> sunset4@ietf.org
>> https://www.ietf.org/mailman/listinfo/sunset4
>> 
> _______________________________________________
> sunset4 mailing list
> sunset4@ietf.org
> https://www.ietf.org/mailman/listinfo/sunset4