IETF Logo Mail Archive

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

Ross Chandler <ross@eircom.net> Fri, 30 January 2015 19:51 UTC

Return-Path: <ross@eircom.net>
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 4D2D81A1BBD for <v6ops@ietfa.amsl.com>; Fri, 30 Jan 2015 11:51:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 qRPK8aAeRMQ8 for <v6ops@ietfa.amsl.com>; Fri, 30 Jan 2015 11:51:10 -0800 (PST)
Received: from mail19.svc.cra.dublin.eircom.net (mail19.svc.cra.dublin.eircom.net [159.134.118.218]) by ietfa.amsl.com (Postfix) with SMTP id 1BB5E1A1BDA for <v6ops@ietf.org>; Fri, 30 Jan 2015 11:50:33 -0800 (PST)
Received: (qmail 70435 messnum 326912 invoked from network[213.94.190.12/avas01.vendorsvc.cra.dublin.eircom.net]); 30 Jan 2015 19:50:31 -0000
Received: from avas01.vendorsvc.cra.dublin.eircom.net (213.94.190.12) by mail19.svc.cra.dublin.eircom.net (qp 70435) with SMTP; 30 Jan 2015 19:50:31 -0000
Received: from [192.168.1.1] ([86.43.35.194]) by avas01.vendorsvc.cra.dublin.eircom.net with Cloudmark Gateway id mKqU1p00C4BK5ly01KqXdT; Fri, 30 Jan 2015 19:50:31 +0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Ross Chandler <ross@eircom.net>
In-Reply-To: <20150130180456.GP34798@Space.Net>
Date: Fri, 30 Jan 2015 19:50:22 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D4F2458-B559-4F9E-A142-D1C0880C9A79@eircom.net>
References: <B7D61F30-BAC4-4BE0-A5FD-1D4BD4652E55@employees.org> <20150129201251.GD34798@Space.Net> <787AE7BB302AE849A7480A190F8B933004902668@OPEXCLILM23.corporate.adroot.infra.ftgroup> <20150130103924.GG34798@Space.Net> <787AE7BB302AE849A7480A190F8B933004902889@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CAKD1Yr2WQfbDstchk4J0hcCz2_X23nijd71QytU5RpuV=Q3Wjg@mail.gmail.com> <FFD91DE61362694C94B174BB03CFDCDD0102408FA8AC@HE113605.emea1.cds.t-internal.com> <54CBB2BB.9010608@foobar.org> <20150130164126.GO34798@Space.Net> <8909_1422637053_54CBB7FD_8909_6553_1_5adce3e7-c0d1-4493-b88f-a20a0d4e3c9b@OPEXCLILH03.corporate.adroot.infra.ftgroup> <20150130180456.GP34798@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/EXIRXtiPLkLOY8uhxrCRgh6_VdM>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "draft-ietf-v6ops-mobile-device-profile.all@tools.ietf.org" <draft-ietf-v6ops-mobile-device-profile.all@tools.ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
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, 30 Jan 2015 19:51:15 -0000

> On 30 Jan 2015, at 18:04, Gert Doering <gert@space.net> wrote:
> 
> This is a global world, and (maybe except for the chinese market), handset
> vendors ship globally -

I know of one Android based vendor that isn’t shipping IPv6 support in Europe yet (they plan to) for devices known to work with IPv6.
We take a regional image from them at present.

> so I bet that an Android handset that works well
> in T-Mobile USA's and Verizon Wireless' network has enough IPv6 support
> to work on your network as well…

I just tested bug fixes from another vendor to make 464xlat work with IPv4 tethering when a shared handset data & tethering APN is used.
The software developed I assume to meet the requirements of T-Mobile US didn’t work  for the above case although that case works in stock android.

> OTOH, I have a number of Telco-branded devices here that can *not* do
> IPv6, even if the original vendor firmware *does* IPv6.  

There’s an original vendor that lets APN protocol be edited to IPv6 but the devices don’t include the necessary support.

Another vendor hasn’t said that they’ll support 464xlat and it doesn’t look like they’ve any plans to.

BR
Ross

v2.23.0 | Report a Bug | By Email