Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roaming-analysis-02.txt

Dave Michaud <Dave.Michaud@rci.rogers.com> Thu, 07 August 2014 13:16 UTC

Return-Path: <Dave.Michaud@rci.rogers.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 590C71B2A3D for <v6ops@ietfa.amsl.com>; Thu, 7 Aug 2014 06:16:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-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 eKanKN196tcQ for <v6ops@ietfa.amsl.com>; Thu, 7 Aug 2014 06:16:21 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0208.outbound.protection.outlook.com [207.46.163.208]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A2231B2AD6 for <v6ops@ietf.org>; Thu, 7 Aug 2014 06:16:16 -0700 (PDT)
Received: from BLUPR04MB596.namprd04.prod.outlook.com (10.141.202.147) by BLUPR04MB008.namprd04.prod.outlook.com (10.255.210.28) with Microsoft SMTP Server (TLS) id 15.0.995.14; Thu, 7 Aug 2014 13:16:07 +0000
Received: from BLUPR04MB596.namprd04.prod.outlook.com (10.141.202.147) by BLUPR04MB596.namprd04.prod.outlook.com (10.141.202.147) with Microsoft SMTP Server (TLS) id 15.0.1005.10; Thu, 7 Aug 2014 13:16:05 +0000
Received: from BLUPR04MB596.namprd04.prod.outlook.com ([10.141.202.147]) by BLUPR04MB596.namprd04.prod.outlook.com ([10.141.202.147]) with mapi id 15.00.1005.008; Thu, 7 Aug 2014 13:16:05 +0000
From: Dave Michaud <Dave.Michaud@rci.rogers.com>
To: Ca By <cb.list6@gmail.com>, Tore Anderson <tore@fud.no>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roaming-analysis-02.txt
Thread-Index: AQHPsj8hdINvZr24nUuvFzCdc8KDrJvFHcZg
Date: Thu, 07 Aug 2014 13:16:05 +0000
Message-ID: <f6347a8cb7cf49f19bc994efc6b66a25@BLUPR04MB596.namprd04.prod.outlook.com>
References: <256EAE0B-5C11-42C7-BCA1-CEC7EE6713A7@cisco.com> <53DFD634.4020304@fud.no> <DE860EBC-171E-46E7-A3B6-5E8B79A453CC@cisco.com> <53DFEC6C.3010707@gmail.com> <CAD6AjGRUWxT5XiNxMi_S5VgYtGMLb_FVHXN-ZfGpcY=geix15g@mail.gmail.com> <53E06AC9.9010908@fud.no> <CAD6AjGTwt-20gXs=RUH5zbhT+g3HKrvXHX3FnShjF1srqU21Fw@mail.gmail.com> <94146541-768B-4853-A011-7558655C361C@eircom.net> <53E11795.7060305@fud.no> <alpine.DEB.2.02.1408060856080.7929@uplift.swm.pp.se> <53E1D951.8030200@fud.no> <3f59106bc21840dfb144c7933215294f@srvhk403.rdm.cz> <53E27522.4070901@fud.no> <84A403BD-7E93-4D99-8C11-FB7F91B68154@eircom.net> <0CEE83E4-FA58-4D85-B753-1F218540C624@eircom.net> <53E30E74.7050502@fud.no> <CAD6AjGTjYTzDRC_UbmmwiafAYch-VH=_sOaMWu+tMOQNrcEOCQ@mail.gmail.com>
In-Reply-To: <CAD6AjGTjYTzDRC_UbmmwiafAYch-VH=_sOaMWu+tMOQNrcEOCQ@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [162.208.80.15]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:;
x-forefront-prvs: 029651C7A1
x-forefront-antispam-report: SFV:NSPM; SFS:(189002)(199002)(24454002)(377454003)(55674003)(19580395003)(19580405001)(83322001)(101416001)(46102001)(106356001)(81542001)(106116001)(19273905006)(85306004)(19625215002)(19300405004)(93886004)(15202345003)(107046002)(105586002)(33646002)(15975445006)(99286002)(19617315012)(95666004)(74316001)(76576001)(20776003)(64706001)(4396001)(80022001)(21056001)(66066001)(76176999)(81342001)(50986999)(76482001)(54356999)(87936001)(77982001)(86362001)(16236675004)(85852003)(83072002)(99396002)(2656002)(74502001)(74662001)(24736002)(108616003); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR04MB596; H:BLUPR04MB596.namprd04.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:3; LANG:en;
Content-Type: multipart/alternative; boundary="_000_f6347a8cb7cf49f19bc994efc6b66a25BLUPR04MB596namprd04pro_"
MIME-Version: 1.0
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:
X-OriginatorOrg: rci.rogers.com
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/t8jy32W9RaiEFE6vJt76elPmMeA
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roaming-analysis-02.txt
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: Thu, 07 Aug 2014 13:16:28 -0000
X-List-Received-Date: Thu, 07 Aug 2014 13:16:28 -0000

IPv4v6 is broken when roaming, that is a fact and I have a huge list of providers that are broken in that scenario.

As for IPv6 while roaming, it has been supported for a long time but there is still a fair share of operators who for various reasons don’t allow it.

When I’m abroad, I always make a point to test all operators on IPv6-only and always see a lot of failure. This becomes especially apparent if the home operator performs some steering of roaming targeted to an operator that doesn’t allow IPv6.

That’s why in the meantime, we are doing IPv6 at home and IPv4 while roaming (with the APN configured to support both on the core network).

Dave Michaud

From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Ca By
Sent: Thursday, August 07, 2014 8:57 AM
To: Tore Anderson
Cc: IPv6 Ops WG
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roaming-analysis-02.txt


On Aug 6, 2014 10:29 PM, "Tore Anderson" <tore@fud.no<mailto:tore@fud.no>> wrote:
>
> * Ross Chandler
>
> >> It might be that when the UE visits a network that doesn’t allow
> >> IPv6 in the user-plane Android behaviour is kicking in.
> >>
> >> I’ve been told that Android treats all APNs as “roughly equal”.
> >>
> >> If the new IPv6-only-without-IPv4-fallback APN fails then Android
> >> might be trying the IPv4 one.
> >
> > If this is what’s going on in Telenor case the plus is it maximises
> > the number of roaming partners that come up with IPv6 but at the
> > possible cost of indeterminism on which APN the UE settles on using
> > when it gets back home.
>
> I'm fairly certain there is no such indeterminism.
>
> Basically the UEs get set up to request IPv6 PDP type both home and when
> roaming. So when they establish a data bearer they get IPv6 (+464XLAT)
> no matter where in the world they are, or they get no data bearer at all
> (if there's some sort of problem somewhere).
>
> That Telenor feels confident in doing it in this manner is very good
> news, I think. It reminds me of the World IPv6 Launch, actually - where
> it was decided that the bugs and issues that had previously made it
> unsafe to deploy IPv6 on a global scale (as opposed to a select few
> known good networks, corresponding well to "the home PLMN only" in the
> mobile case), has been sufficiently solved so that IPv6 can be made
> generally available instead.
>
> I guess now it's up to Cameron and Michał to follow suit. ;-)
>
> Tore
>
>

I agree, for my own phone, i roam internationally with no issue on ipv6.

CB _______________________________________________
> v6ops mailing list
> v6ops@ietf.org<mailto:v6ops@ietf.org>
> https://www.ietf.org/mailman/listinfo/v6ops




________________________________
This communication is confidential. We only send and receive email on the basis of the terms set out at www.rogers.com/web/content/emailnotice<http://www.rogers.com/web/content/emailnotice>



Ce message est confidentiel. Notre transmission et réception de courriels se fait strictement suivant les modalités énoncées dans l’avis publié à www.rogers.com/aviscourriel <http://www.rogers.com/aviscourriel>
________________________________