[179445] in North American Network Operators' Group

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

Re: Galaxy S6 is IPv6 on all US National Mobile carriers

daemon@ATHENA.MIT.EDU (Jared Mauch)
Mon Apr 13 22:01:26 2015

X-Original-To: nanog@nanog.org
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAL9jLab0cd3q_ToV0sS=J06pCQZ5Lqv0dwr8Op9C2_Pc74=wYg@mail.gmail.com>
Date: Mon, 13 Apr 2015 21:59:44 -0400
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org


> On Apr 13, 2015, at 9:48 PM, Christopher Morrow =
<morrowc.lists@gmail.com> wrote:
>=20
> that 'clearly' reddit could have cloudflare serve the endpoint from an
> ipv6 address, and thus populate a AAAA in reddit.com's domain.
>=20
> maybe it's not that simple.

Well, it usually really is but just like automation, ipv6 isn=E2=80=99t =
something that
many people have broad experiences with, and don=E2=80=99t cut+paste =
quite as well as
one would hope.  There are also *Way* too many people who memorize IP =
addresses
out there that have a harder time trying to store 128-bits in their =
memory vs
32-bits.

They also don=E2=80=99t want to lose track of where that IPv4 packet =
came from, so don=E2=80=99t
want a reverse proxy doing protocol tcp6 -> tcp4 mucking for them.

eg: ATT wireless/mobility could have their proxy connect() to an ipv6 =
address vs
ipv4 which my phone transits when on their network and the qname returns =
AAAA.
This was my favorite thing when running a transparent proxy on my home =
network,
it could turn all the traffic from hosts that might not naturally think =
of doing
modprobe ipv6 and turned them into IPv6 requests.

For those wondering, nearly 62% of VZ Wireless traffic is IPv6.

http://www.worldipv6launch.org/measurements/

- Jared=

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