[186823] in North American Network Operators' Group
Re: Another Big day for IPv6 - 10% native penetration
daemon@ATHENA.MIT.EDU (Owen DeLong)
Tue Jan 5 03:49:42 2016
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <alpine.DEB.2.02.1601050904110.29581@uplift.swm.pp.se>
Date: Tue, 5 Jan 2016 00:48:36 -0800
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
> On Jan 5, 2016, at 00:09 , Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
>=20
> On Mon, 4 Jan 2016, Jared Mauch wrote:
>=20
>> I for one welcome the iOS update that brings v6 APN native access to =
my phone, or at least v4v6 APN setting.
>=20
> That's not how it's done on Apple, they (together with the operator) =
control the APN settings. There are several mobile networks that run =
IPv4v6 on iOS (all LTE enabled devices support this) for almost a year =
(I believe it was iOS 8.3 in March 2015 that started to support this for =
more general 3GPP providers).
>=20
> But getting IPv4v6 bearer working in a mobile network is non-trivial =
and it still brings the CGN mess, so a lot of mobile providers prefer to =
use IPv6 only with translation to reach IPv4 sites. That's where Cameron =
is coming from, and it's perfectly understanable mode of operation.
Except that the only mode of translation Cameron is willing to support =
is the one which isn=E2=80=99t available in iOS, so we have a religious =
war between T-Mo and Apple where T-Mo says =E2=80=9CSupport 464Xlat or =
suffer=E2=80=9D and Apple says =E2=80=9CNo, you support one of the =
mechanisms already supported in iOS=E2=80=9D.
> Apple seems to be working to make IPv6 only+AFTR happen and I have =
good hopes that they'll succeed in 2016.
Good that one of them is finally backing down on the previous stupidity, =
but for a variety of reasons, I wish it had been T-mo.
Owen
