[182219] in North American Network Operators' Group
Re: Hotels/Airports with IPv6
daemon@ATHENA.MIT.EDU (Mel Beckman)
Mon Jul 13 12:04:39 2015
X-Original-To: nanog@nanog.org
From: Mel Beckman <mel@beckman.org>
To: "A.L.M.Buxey@lboro.ac.uk" <A.L.M.Buxey@lboro.ac.uk>
Date: Mon, 13 Jul 2015 15:59:52 +0000
In-Reply-To: <20150713155430.GC27032@lboro.ac.uk>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Of course. The question is, is a highly visible public wifi network the pla=
ce to hammer out problems? My customer decided no.
-mel beckman
> On Jul 13, 2015, at 8:54 AM, "A.L.M.Buxey@lboro.ac.uk" <A.L.M.Buxey@lboro=
.ac.uk> wrote:
>=20
> Hi,
>> I've done fairly extensive testing, and IPv6 support, while pretty solid=
on the carrier side, is still iffy on WiFi. Both iOS and Android have vari=
ous reliability problems with IPv6 and WiFi, mostly related to acquiring a =
DNS address or maintaining a connection while roaming. Combine that with le=
ss-than-fully-baked IPv6 on some enterprise WiFi platforms, and it's easy t=
o see that deploying WiFi IPv6 today is at least a challenge, and definitel=
y a risk.=20
>>=20
>> Android, for example, doesn't yet support DHCPv6 on WiFi (it's not neede=
d on the carrier side, which does DNS intercept), and intermittently looses=
its unicast address on some hardware devices (notably tablets, in my exper=
ience). Even when android gets DHCPv6, or these hardware problems get solve=
d, there will be several years of legacy devices in the field to contend wi=
th. =20
>=20
> we had problems with IPv4 in the early days - people still adopted it. wi=
thout adoption, the bugs/issues with clients dont
> get addressed.=20
>=20
> alan
