Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call

<> Fri, 30 January 2015 09:39 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id AAFF61A8A82 for <>; Fri, 30 Jan 2015 01:39:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Uj2ggLog3s3v for <>; Fri, 30 Jan 2015 01:39:36 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 199001A8A79 for <>; Fri, 30 Jan 2015 01:39:36 -0800 (PST)
Received: from (unknown [xx.xx.xx.201]) by (ESMTP service) with ESMTP id 4F25B1B834F; Fri, 30 Jan 2015 10:39:34 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown []) by (ESMTP service) with ESMTP id E385D3840B3; Fri, 30 Jan 2015 10:39:33 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([]) by OPEXCLILH05.corporate.adroot.infra.ftgroup ([]) with mapi id 14.03.0224.002; Fri, 30 Jan 2015 10:39:33 +0100
From: <>
To: Lorenzo Colitti <>
Thread-Topic: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
Thread-Index: AQHQPGaXse6f3Vmd8kuuI7VBYw52SZzYYoBg
Date: Fri, 30 Jan 2015 09:39:33 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B9330049026BC@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <> <> <787AE7BB302AE849A7480A190F8B9330049024FB@OPEXCLILM23.corporate.adroot.infra.ftgroup> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B9330049026BCOPEXCLILM23corp_"
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2015.1.30.70618
Archived-At: <>
Cc: "" <>, "" <>, V6 Ops List <>
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 30 Jan 2015 09:39:39 -0000


Please see inline.


De : Lorenzo Colitti []
Envoyé : vendredi 30 janvier 2015 09:27
Cc : Fred Baker (fred); V6 Ops List;;; joel jaeggli
Objet : Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call

On Fri, Jan 30, 2015 at 4:35 PM, <<>> wrote:
1. The wording "required features to connect 3GPP mobile devices to an IPv6-only or dual-stack wireless network" is factually incorrect. The vast majority of these recommendations are not required to connect to such networks, and are many are not even implemented by many popular mobile operating systems - which manage to connect just fine. After long discussions, that text was removed in -06. Why was it readded?

[Med] This text was redited as a side effect of implementing the request from the IESG to position this document as a superset of existing RFCs.  The recommendations are not only about IPv6 but also, as indicated in the same sentence you quoted, “features to deliver IPv4 connectivity service over an IPv6-only transport”.

But that doesn't change the fact that the statement is incorrect. The vast majority of those features are not "required to connect". As for the feature required to deliver IPv4 connectivity service over IPv6-only transport, only one feature (out of the dozes in this draft) is required for that - 464xlat.

If you want to turn this into a document of features that are required to connect, I support that... but that would mean that the majority of recommendations should be removed, because they're not required.

[Med] We already discussed this point several times. No need to repeat this discussion once again.

Also - this document passed WG and IETF last call with the understanding that it explicitly did *not* define an IETF-approved device profile, but only a profile "that a number of operators recommend". That text was in the document as recently as -14, but it was removed.

Making this documean IETF-approved device profile is a substantial change and has much broader implications than what the WG and IETF had consensus on. Adding that text was essential to overcome the objections of those in the WG that felt that it is not the place of an operational WG, or indeed of the IETF, to place the RFC seal of approval on a device profile document (or, as Brian puts it, "on somebody's procurement spec").

That text should be restored.

[Med] Your point about the process is fair. I have no problem to restore that text if this is what the WG wants. This is really the kind fo feedback I’m looking for.  Unless I heard any objection from the WG, that text will be restored.

2. Previous versions of the document, including the version that passed IETF last call, contained the text:

   This document is not a standard, and conformance with it is not
   required in order to claim conformance with IETF standards for IPv6.
   The support of the full set of features may not be required in some
   deployment contexts.  The authors believe that the support of a
   subset of the features included in this protocol may lead to degraded
   level of service in some deployment contexts.

That text remains accurate and that statement is still necessary. Why was it removed? It has been in the document since -06, and the words "this document is not a standard" have been in this document since -01.

[Med] It was removed as per a request from the IESG (A. Farrel).

Adrian, why did you request that this text be removed?

The text that passed last call went out of its way to state it was not a standard, and that compliance with it was not required.  This text helped defuse substantial objections within the WG and the IETF that pointed out that only a fraction of these features are actually necessary to deploy, and called attention to the harm to IPv6 deployment that would occur if mobile operators and device manufacturers believed that all these features needed to be implemented before deployment could occur.

[Med] Lorenzo, the document does not states ALL features MUST be implemented. Just like any other recommendation document, there are several support levels. As far as I’m concerned, I have no objection to include that text if the IESG is OK with it.

3. I object to the statement "One of the major hurdles encountered by mobile operators is the availability of non-broken IPv6 implementation in mobile devices." I submit that if it were true, then we would observe no IPv6 deployment in mobile networks... but publicly-available data - e.g., - shows that multiple operators have deployed IPv6 to up to 30-65% of their footprint, using the same commercially-available devices that are used by customers of other operators. So claiming that "broken IPv6 implementations in mobile devices" are a major hurdle is at best incomplete and at worst incorrect.

[Med] That sentence was there since we edited the individual version of the document. Of course, current implementations perform better that when we edited the -00 of the document. Still, the feedback we had from our device team is that there are still a lot to be done.

But you see, the problem with that is that it's just the opinion of your device team. For example, if instead you asked the device teams of Verizon Wireless and T-Mobile, they might well say that the features that are necessary to deploy IPv6 are already supported just fine (with the possible exception of 464xlat on iOS) - and that's why they deployed IPv6 to 30-65% of their devices.
[Med] This is US-centric, but anyway you already raised this point several times: some answers are provided here or I can add that in the Europe for instance, operators do not control the device used by  the customer, hence the need to have a profile.

The IETF should not document matters of opinion.
[Med] Agree.

It should make technical statements that are supported by evidence.
[Med] ISOC organized several IPv6 mobile workshops that revealed that operators participated a those workshop agree devices are a hurdle for their IPv6 deployments. I don’t have public pointers for the prez mad during the workshop but you can get in touch with ISOC if you need so.

The available evidence does not support the statement that "IPv6 deployment is blocked because mobile device implementations are broken"; in fact, the existence of large mobile deployments proves that statement wrong.
[Med] Not sure to understand the causality effect here.