Re: [BEHAVE] Where is the definition of IPv6 only hostforNAT64/DNS64

<mohamed.boucadair@orange-ftgroup.com> Tue, 21 July 2009 08:07 UTC

Return-Path: <mohamed.boucadair@orange-ftgroup.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 3346B28C198 for <behave@core3.amsl.com>; Tue, 21 Jul 2009 01:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 FKmjltayS5Fj for <behave@core3.amsl.com>; Tue, 21 Jul 2009 01:07:01 -0700 (PDT)
Received: from R-MAIL1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id F27E028C1A2 for <behave@ietf.org>; Tue, 21 Jul 2009 01:07:00 -0700 (PDT)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Tue, 21 Jul 2009 10:06:56 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 21 Jul 2009 10:06:14 +0200
Message-ID: <08BA2C59E081884DB2AAE4A0BE9D6DC13FA682@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <01f501ca070d$dd6fa050$c4f0200a@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [BEHAVE] Where is the definition of IPv6 only hostforNAT64/DNS64
Thread-Index: AcoGycLOtvM5nnSnRwGG3vz82bIa8wAQ1JkQALL9uQA=
References: <1d38a3350907130810r55dc1789k501ff1643de9d517@mail.gmail.com><E4561B14EE2A3E4E9D478EBFB5416E1B0F4F5A@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com><1d38a3350907160130i5a3ef3fbrc5ec8b9303f78773@mail.gmail.com><162a01ca063e$774ceeb0$c4f0200a@cisco.com><1d38a3350907170331t6acc1503m2de7be848a106232@mail.gmail.com> <01f501ca070d$dd6fa050$c4f0200a@cisco.com>
From: mohamed.boucadair@orange-ftgroup.com
To: dwing@cisco.com, denghui02@gmail.com
X-OriginalArrivalTime: 21 Jul 2009 08:06:56.0005 (UTC) FILETIME=[36C79350:01CA09DA]
Cc: behave@ietf.org, dthaler@microsoft.com
Subject: Re: [BEHAVE] Where is the definition of IPv6 only hostforNAT64/DNS64
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: Tue, 21 Jul 2009 08:07:08 -0000

 
Dear Dan, all,

See inline

Cheers,
Med


-----Message d'origine-----
De : behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la part de Dan Wing
Envoyé : vendredi 17 juillet 2009 20:39
À : 'Hui Deng'
Cc : behave@ietf.org; 'Dave Thaler'
Objet : Re: [BEHAVE] Where is the definition of IPv6 only hostforNAT64/DNS64


> >
> > Most, if not all, of the mobile providers are anticipating
> IPv6-only handsets
> > on their LTE/"4G" networks.  Some companies, some
> universities, and some
> > wireline service providers, in an effort to reduce the
> operational complexity
> > of the end hosts and their network, want to run a
> single-stack network with
> > IPv6.  Those handsets and those hosts would still need to
> contact servers on
> > the IPv4 Internet.
> ==> China Mobile is leading IPv6 transition work item in 3GPP, acting 
> as a rapporteur.
> I personally deeply involve in this work, but until today, I haven't 
> heard about IPv6 only handset requirement proposed.

Dual-stack handset, running on the mobile operator's network, means the mobile operator:

  * operates two networks (IPv4 and IPv6).  For both IP address
    families you need routing tables, ACLs, DHCP, and training
  * operates a stateful NAT44 for the subscribers to access 
    the IPv4 Internet

Med: This can be true in some configurationss. But, other solutions may be envisaged to offer both IPv4 and IPv6 connectivty services to end-user with ***IPv6-only*** network and ***stateless*** IPv4-IPv6 interworking. See http://tools.ietf.org/html/draft-boucadair-behave-ipv6-portrange-01#section-6.6.1. A ds-lite compliant solution can also be envisaged http://tools.ietf.org/html/draft-boucadair-dslite-interco-v4v6-01. 


IPv6-only handset means the mobile operator:

  * operates one network (IPv6)
  * operates a stateful NAT64 for the subscribers to access 
    the IPv4 Internet