[158330] in North American Network Operators' Group
RE: Big day for IPv6 - 1% native penetration
daemon@ATHENA.MIT.EDU (david.binet@orange.com)
Wed Nov 28 08:34:21 2012
From: <david.binet@orange.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, "nanog@nanog.org" <nanog@nanog.org>
Date: Wed, 28 Nov 2012 14:33:50 +0100
In-Reply-To: <alpine.DEB.2.00.1211280752330.27834@uplift.swm.pp.se>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Hi,
> -----Message d'origine-----
> De : Mikael Abrahamsson [mailto:swmike@swm.pp.se]=20
> Envoy=E9 : mercredi 28 novembre 2012 07:57
> =C0 : nanog@nanog.org
> Objet : Re: Big day for IPv6 - 1% native penetration
>=20
> On Tue, 27 Nov 2012, Cameron Byrne wrote:
>=20
> > Verizon in the USA does have iOS on ipv6. Afaik, the=20
> network must ask=20
> > for it the same way all Android Samsung devices on t-mobile=20
> now have=20
> > ipv6 as a user option because it is part of the=20
> requirements for the oems.
>=20
> I have been trying to locate someone within Apple for months=20
> now to speak about IPv6 on their mobile devices. The wall of=20
> silence is impressive.
>=20
> The android manufacturers at last respond, even though it's=20
> not always the answer I want :P
Mobile operators have some difficulties to get some IPv6 terminals.It is th=
e reason why we have proposed an IETF draft to define some IPv6 profile for=
mobile terminals (https://datatracker.ietf.org/doc/draft-binet-v6ops-cellu=
lar-host-requirements/)
IMHO it is strategic to get a document that specifies such profile. It is i=
mportant that such draft becomes a WG document so all support for such draf=
t on IETF v6ops ML is welcome.=20
Such document will not replace discussions we may have with vendors but it =
is for sure a useful contribution to our common objective.=20
>=20
> > Win phone 8 has a menu option for ipv6 but I don't think it=20
> works ....
>=20
> Yeah, it's like the Galaxy Nexus which has IPv4v6 in the menu=20
> but if you use it it asks for an IPv4 PDP context and when it=20
> gets it, it falls over and needs to be rebooted.
>=20
> > I have been v6-only on mobile for 2 years now, and I feel=20
> fine. I am=20
> > sending this email using a v6-only note2... dogfooding it. Yet, the=20
> > rotten apples spoil the bunch as the saying goes... and=20
> hence 464xlat.
>=20
> Any progress with this, to get this into mainline?
>=20
> Then again, I feel we'll have proper IPv4v6 PDP context=20
> before there is any worthwile 464XLAT deployment, but for the=20
> long tail I would like to have 464XLAT in all devices.
>=20
> --=20
> Mikael Abrahamsson email: swmike@swm.pp.se
>=20
>=20
___________________________________________________________________________=
______________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.
