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

Lorenzo Colitti <lorenzo@google.com> Tue, 07 October 2014 13:56 UTC

Return-Path: <lorenzo@google.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 316B81ACD90 for <v6ops@ietfa.amsl.com>; Tue, 7 Oct 2014 06:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.65
X-Spam-Level:
X-Spam-Status: No, score=-0.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, URIBL_RHS_DOB=1.514] autolearn=unavailable
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 ALyZZwWyCh30 for <v6ops@ietfa.amsl.com>; Tue, 7 Oct 2014 06:56:01 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 254521ACDA7 for <v6ops@ietf.org>; Tue, 7 Oct 2014 06:55:15 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id rl12so5204154iec.23 for <v6ops@ietf.org>; Tue, 07 Oct 2014 06:55:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=lU2xfue5oFiu6ugf70Un0qv7Nfr13yw1PqhcZ8zd+gA=; b=UyfRuT2oEYN/UtMmtEeXZJKMnEiJ82vsTFB7jRC9I5FyfRWGcRrEVa40NXcvBwkdnb /+AcHjE8GiyQOeIxO6AAsX5J6DS1ljPfrGT4cD8Qzwi7dJbI4B46Ds9bOyPFOMFz1pmm Yse5Iqj4nhRCWuqkmr0PKIxMWyXurl26N/8HBD8V5/sKPRVzq1iGMeq0nk1kihWgWFfp S4/XK1cRDNBeu6/N78RqdsSpdKHgxFa1ejiQqm2kN2xmt2noP4jJLODfRcTK4MMbenB3 7YnWIUE9L9wtFAIZ6b3K15VwEyr8FXSPQPMO8sTY9xQu1d26hcPZ+8SQmOqge2bhWnsU eNIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=lU2xfue5oFiu6ugf70Un0qv7Nfr13yw1PqhcZ8zd+gA=; b=TEHXuIfenswivK5Pi1m9qLCvNzF7AjS6+xmFN9KQ6LZnkvKY7ckNiq1mJQhEovQGQb LFFPVUMmjLFlDq/LrI3aE0e9smiQctfqVtb3oQ4u1eZxHMh5zdz4OFRQJGaCOHCj2W5i Gz6TmFRhHMONEXxSjfa66sJUatF2f9C+DpkcPyQpfp9tS1ji4qYKtto9/1dUeANFSmPU UCrse59sxHvNGcnQecSPOf3K2bA769fgIhCPvhBPgNyATlwAFI9OzurL0X2zW7DGFio5 UrVKo3ZEaY4lY0RigVPVeej356g+qLMGU5lGAW3SkL+ioeT6gvujdigjVjc1EyPctrxI iHHg==
X-Gm-Message-State: ALoCoQm9x87UTwVlI45HQjzVCY7T3G2D9n2IDaoqAfoYeqcDvwtErfg3wPNZjchEpN/WQ+N5vpDT
X-Received: by 10.42.61.137 with SMTP id u9mr5086142ich.54.1412690114391; Tue, 07 Oct 2014 06:55:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.24.144 with HTTP; Tue, 7 Oct 2014 06:54:54 -0700 (PDT)
In-Reply-To: <6BFD1641-B861-4FBF-852D-E1AF48B97973@eircom.net>
References: <20141002154553.11969.98465.idtracker@ietfa.amsl.com> <CAKD1Yr2d4f-eJvCbSrdZ7e=m4oCXVhABnT-cVxe16WncqRn9tA@mail.gmail.com> <6536E263028723489CCD5B6821D4B21303BDD125@UK30S005EXS06.EEAD.EEINT.CO.UK> <CAKD1Yr0j6c9-Xs27VXqHas_DQjV30iF3fp4AVXKGPs_UXY0+5w@mail.gmail.com> <6BFD1641-B861-4FBF-852D-E1AF48B97973@eircom.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 07 Oct 2014 22:54:54 +0900
Message-ID: <CAKD1Yr0OBWMmjhjdM3KiYzTjZ+btkG=Ax2=jey=TVw8foiA8wg@mail.gmail.com>
To: Ross Chandler <ross@eircom.net>
Content-Type: multipart/alternative; boundary="20cf302237e7726f050504d58c24"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/znNTGCMG6VXZE-dLlWr_ZLD9gOc
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@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 13:56:02 -0000

On Tue, Oct 7, 2014 at 10:45 PM, Ross Chandler <ross@eircom.net> wrote:

> Show me an operator whose rollout is genuinely blocked on terminal
> features and I will believe you. But word from everyone I've talked to is
> that terminal features are not the blocker. Operators such as Verizon
> Wireless and T-Mobile in the US have deployed tens of millions of
> IPv6-capable devices, and none of those devices (and, I'd argue, no
> commercial devices, anywhere) implement all the features in this profile.
> The vast majority only support a handful.
>
> If Apple iOS supported IPv6-only/464xlat and all mobile devices had better
> support for problem roaming cases then I might think this might not provide
> a needed signal but it would still be useful to have a document listing
> desired features.
>

I agree with you that these two are problems, and that solving them would
improve the state (and the amount of) IPv6 in mobile networks. It would be
good to have discussions and publish documents on real issues that actually
affect deployment. But the way to do so is not to bury those real issues
into a laundry list of requirements. (Not to mention that this document
classes 464xlat as "should".)


> The majority of work implementing the appropriate subset of the features
> is with the mobile device vendor. There’s a growing list of operators to
> look at that are doing it under restricted circumstances. Items from the
> list could help operators broaden the scope of their IPv6 deployments.
>

Other than the two features you mention above, which ones are likely to
have an impact? Perhaps this document should focus more on those.