[182007] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Hotels/Airports with IPv6

daemon@ATHENA.MIT.EDU (Ca By)
Thu Jul 9 11:37:04 2015

X-Original-To: nanog@nanog.org
In-Reply-To: <A3470511-BA93-46A1-99C4-DAAD8E46E869@beckman.org>
Date: Thu, 9 Jul 2015 08:35:55 -0700
From: Ca By <cb.list6@gmail.com>
To: Mel Beckman <mel@beckman.org>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

On Thursday, July 9, 2015, Mel Beckman <mel@beckman.org> wrote:

> I working on a large airport WiFi deployment right now. IPv6 is "allowed
> for in the future" but not configured in the short term. With less than
> 10,000 ephemeral users, we don't expect users to demand IPv6 until most
> mobile devices and apps come ready to use IPv6 by default.
>
>
1. Users will never demand ipv6. They demand google and facebook. So that
road goes nowhere

2.  What data do you have that most devices and apps are not default-on /
ready for ipv6.  My guess is most devices carried by airport users
will accept and use ipv6 address, and most used destinations (google, fb,
netflix, wikipedia, ....) use ipv6

CB



>  -mel beckman
>
> > On Jul 9, 2015, at 7:53 AM, Jared Mauch <jared@puck.nether.net
> <javascript:;>> wrote:
> >
> > It=E2=80=99s my understanding that many captive portals have trouble wi=
th IPv6
> traffic and this is a blocker for places.
> >
> > I=E2=80=99m wondering what people who deploy captive portals are doing =
with
> these things?
> >
> > https://tools.ietf.org/html/draft-wkumari-dhc-capport
> >
> > seems to be trying to document the method to signal to clients how to
> authenticate.  I was having horrible luck with Boingo yesterday at RDU
> airport with their captive portal and deauthenticating me so just went to
> cellular data, so wondering if IPv4 doesn=E2=80=99t work well what works =
for IPv6.
> >
> > Thanks,
> >
> > - Jared
>

home help back first fref pref prev next nref lref last post