Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-13.txt> (An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC

"Heatley, Nick" <nick.heatley@ee.co.uk> Tue, 07 October 2014 09:30 UTC

Return-Path: <nick.heatley@ee.co.uk>
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 6EC791ACCDC; Tue, 7 Oct 2014 02:30:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_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 0reDh64Tkp_q; Tue, 7 Oct 2014 02:30:49 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.111]) by ietfa.amsl.com (Postfix) with ESMTP id 7F0E21A1B60; Tue, 7 Oct 2014 02:30:48 -0700 (PDT)
Received: from [194.106.220.51:48014] by server-7.bemta-14.messagelabs.com id 2F/1E-13362-7C2B3345; Tue, 07 Oct 2014 09:30:47 +0000
X-Env-Sender: nick.heatley@ee.co.uk
X-Msg-Ref: server-8.tower-92.messagelabs.com!1412674246!19123008!1
X-Originating-IP: [193.36.79.210]
X-StarScan-Received:
X-StarScan-Version: 6.12.2; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16817 invoked from network); 7 Oct 2014 09:30:46 -0000
Received: from unknown (HELO aphex) (193.36.79.210) by server-8.tower-92.messagelabs.com with SMTP; 7 Oct 2014 09:30:46 -0000
Received: from UK31S005EXS02.EEAD.EEINT.CO.UK (Not Verified[10.246.208.27]) by aphex with MailMarshal (v6, 8, 2, 9371) id <B5433b5580001>; Tue, 07 Oct 2014 10:41:45 +0100
Received: from UK30S005EXS06.EEAD.EEINT.CO.UK ([fe80::314c:b96c:4a9a:8a79]) by UK31S005EXS02.EEAD.EEINT.CO.UK ([2002:1ef6:d01b::1ef6:d01b]) with mapi id 14.03.0195.001; Tue, 7 Oct 2014 10:30:34 +0100
From: "Heatley, Nick" <nick.heatley@ee.co.uk>
To: Lorenzo Colitti <lorenzo@google.com>, IETF Discussion <ietf@ietf.org>
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-13.txt> (An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
Thread-Index: AQHP3lgstOYuetH+dkamfUnp7cN2RpwioU0AgAG2U0A=
Date: Tue, 07 Oct 2014 09:30:33 +0000
Message-ID: <6536E263028723489CCD5B6821D4B21303BDD125@UK30S005EXS06.EEAD.EEINT.CO.UK>
References: <20141002154553.11969.98465.idtracker@ietfa.amsl.com> <CAKD1Yr2d4f-eJvCbSrdZ7e=m4oCXVhABnT-cVxe16WncqRn9tA@mail.gmail.com>
In-Reply-To: <CAKD1Yr2d4f-eJvCbSrdZ7e=m4oCXVhABnT-cVxe16WncqRn9tA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.246.208.5]
Content-Type: multipart/alternative; boundary="_000_6536E263028723489CCD5B6821D4B21303BDD125UK30S005EXS06EE_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/WK36zUKbw-Sjvlo2fL0eBwXOh28
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-13.txt> (An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
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: Tue, 07 Oct 2014 09:30:51 -0000

2. I stand by my earlier assessment that this document's requirements are over-broad, and in fact so broad as to harm adoption. There may well be operators or device implementers that seeing with such a high number of requirements may shy away in terror and think that deploying IPv6 in a mobile network is an impossibly high amount of work. That said, given that this document says clearly that it is not a standard, and that compliance is not required, the harm it does will be limited.

There may well be operators and device implementers that see the many individual “IPv6” RFCs and shy away. Transitioning technologies are still perceived as issues for the network.
If this cross-operator document states what is required on terminals to work in all major/predictable IPv6 scenarios, then it is giving such people a view of what a “healthy and robust” terminal implementation would consist of. If they are able to deliver on these requirements then they can supply a terminal ready for all business areas /all operator network scenarios.
(It certainly stops the feedback I’ve had from certain corners “that no other operators are asking for IPv6”, and “what you are asking for is a single operator roadmap which we won’t do”. That has been the reality here). So I don’t see how a consolidated demand-side view from operators who are really trying to introduce IPv6  in mobile can harm adoption in any way.
Regards,
Nick

From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Lorenzo Colitti
Sent: 06 October 2014 08:30
To: IETF Discussion
Cc: v6ops@ietf.org WG; IETF-Announce
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-13.txt> (An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC



NOTICE AND DISCLAIMER
This e-mail (including any attachments) is intended for the above-named person(s).  If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose.  
 
We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you. 

EE Limited
Registered in England and Wales
Company Registered Number: 02382161
Registered Office Address: Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9BW