Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-device-profile-17.txt - C_REC#9 464XLAT
<mohamed.boucadair@orange.com> Fri, 13 February 2015 06:49 UTC
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDBE51A09C9 for <v6ops@ietfa.amsl.com>; Thu, 12 Feb 2015 22:49:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hyTJstW3_72w for <v6ops@ietfa.amsl.com>; Thu, 12 Feb 2015 22:49:25 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A49981A0AF1 for <v6ops@ietf.org>; Thu, 12 Feb 2015 22:49:24 -0800 (PST)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 5076418C4D1; Fri, 13 Feb 2015 07:49:22 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.16]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id A958A23815B; Fri, 13 Feb 2015 07:49:21 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.231]) by OPEXCLILH05.corporate.adroot.infra.ftgroup ([10.114.31.16]) with mapi id 14.03.0224.002; Fri, 13 Feb 2015 07:49:21 +0100
From: mohamed.boucadair@orange.com
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-mobile-device-profile-17.txt - C_REC#9 464XLAT
Thread-Index: AQHQRuDkZAjCWymvpku8SqF2CiTh9ZzuH5Wg
Date: Fri, 13 Feb 2015 06:49:20 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300490A7DD@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <20150212124226.3282.9774.idtracker@ietfa.amsl.com> <54DCD464.3000907@gmail.com>
In-Reply-To: <54DCD464.3000907@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.16.112421
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/wf6EuDTLt8_ysACM_fAL3_xmmEo>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-device-profile-17.txt - C_REC#9 464XLAT
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2015 06:49:28 -0000
Hi Alex, The intent of this reco is to address broken IPv4-only applications over an IPv6-only connectivity. Ideally applications running on the device should be AF-independent. The draft relies on the IPv6 node requirements RFC that mandates the supports of IPv6. Also, the I-D calls out applications that are provided by the vendor of the device: == APP_REC#2: Applications provided by the mobile device vendor must be independent of the underlying IP address family. == Wouldn't this reco addresses your concern? Thank you. Cheers, Med -----Message d'origine----- De : v6ops [mailto:v6ops-bounces@ietf.org] De la part de Alexandru Petrescu Envoyé : jeudi 12 février 2015 17:27 À : v6ops@ietf.org Objet : Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-device-profile-17.txt - C_REC#9 464XLAT Hello, Thank you for this new version of the draft. I have a doubt with respect to the 464XLAT requirement: > C_REC#9: In order to ensure IPv4 service continuity in an IPv6-only > deployment context, the cellular host should implement the > Customer Side Translator (CLAT, [RFC6877]) function which > is compliant with [RFC6052][RFC6145][RFC6146]. > > CLAT function in the cellular host allows for IPv4-only > application and IPv4-referals to work on an IPv6-only > connectivity. CLAT function requires a NAT64 capability > [RFC6146] in the core network. > > The IPv4 Service Continuity Prefix used by CLAT is > defined in [RFC7335]. I think this requirement leads to a situation where the network operator deploys IPv6-native-only and IPv4 as an add-on partial feature. On one hand, it is encouraging to see native IPv6 and no IPv4. On another hand, _partial_ IPv4 support is a temptation which deceives in the end - it leads to turn off IPv6 and come back to good ol' IPv4 and no IPv6. The 464XLAT is partial IPv4 support: does not offer full IPv4 connectivity to the smartphone. It is not possible to address the smartphone by its IPv4 address - DNS is required; this makes it impossible to make a VPN tunnel, or Mobile IP. One can not a deploy a wireless IPv4 router along the road in a remote area, for example. This leads to a situation where the operator requires end user to switch to another APN which is less IPv6. I think it is not a happy situation. I would suggest to qualify this requirement by another requirement. This initial requirement would state that _first_, before any v4-v6 conversion mechanism is considered, both the network and the end user MUST implement a native IPv4 stack and a native IPv6 stack (not say 'dual' stack, which is much overloaded). We dont want to block IPv4 use when IPv6 arrives. Alex 12/02/2015 13:42, internet-drafts@ietf.org a écrit : > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the IPv6 Operations Working Group of the IETF. > > Title : An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices > Authors : David Binet > Mohamed Boucadair > Ales Vizdal > Gang Chen > Nick Heatley > Ross Chandler > Filename : draft-ietf-v6ops-mobile-device-profile-17.txt > Pages : 18 > Date : 2015-02-12 > > Abstract: > This document defines a profile that is a superset of that of the > connection to IPv6 cellular networks defined in the IPv6 for Third > Generation Partnership Project (3GPP) Cellular Hosts document. This > document defines an IPv6 profile that a number of operators recommend > in order to connect 3GPP mobile devices to an IPv6-only or dual-stack > wireless network (including 3GPP cellular network and IEEE 802.11 > network) with a special focus on IPv4 service continuity features. > > Both hosts and devices with capability to share their WAN (Wide Area > Network) connectivity are in scope. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/ > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-v6ops-mobile-device-profile-17 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-mobile-device-profile-17 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops > > _______________________________________________ v6ops mailing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
- [v6ops] I-D Action: draft-ietf-v6ops-mobile-devic… internet-drafts
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… mohamed.boucadair
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Heatley, Nick
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… mohamed.boucadair
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Heatley, Nick
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Heatley, Nick
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… mohamed.boucadair
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Heatley, Nick
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Ca By
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Ca By
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Metzler, Dan J
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Erik Kline
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… mohamed.boucadair
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Tore Anderson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Heatley, Nick
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Kossut Tomasz - Hurt
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Tore Anderson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… mohamed.boucadair
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Kossut Tomasz - Hurt
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Metzler, Dan J
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… mohamed.boucadair
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… jouni korhonen
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… jouni korhonen
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Kossut Tomasz - Hurt
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Alexandru Petrescu