[173637] in North American Network Operators' Group

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

Re: Carrier Grade NAT

daemon@ATHENA.MIT.EDU (Owen DeLong)
Wed Jul 30 01:26:19 2014

X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <20140729231327.A63D91B017C9@rock.dv.isc.org>
Date: Tue, 29 Jul 2014 22:22:24 -0700
To: Mark Andrews <marka@isc.org>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


On Jul 29, 2014, at 4:13 PM, Mark Andrews <marka@isc.org> wrote:

>=20
> In message <20140729225352.GO7836@hezmatt.org>, Matt Palmer writes:
>> On Wed, Jul 30, 2014 at 09:28:53AM +1200, Tony Wicks wrote:
>>> 2. IPv6 is nice (dual stack) but the internet without IPv4 is not a =
viable
>>> thing, perhaps one day, but certainly not today (I really hate =
clueless
>>> people who shout to the hills that IPv6 is the "solution" for =
today's
>>> internet access)
>>=20
>> Do you have IPv6 deployed and available to your entire customer base, =
so
>> that those who want to use it can do so?  To my way of thinking, =
CGNAT is
>> probably going to be the number one driver of IPv6 adoption amongst =
the
>> broad customer base, *as long as their ISP provides it*.
>=20
> Add to that over half your traffic will switch to IPv6 as long as
> the customer has a IPv6 capable CPE.  That's a lot less logging you
> need to do from day 1.

That would be nice, but I=92m not 100% convinced that it is true.

Though it will be an increasing percentage over time.

Definitely a good way of reducing the load on your CGN, with the =
additional benefit
that your network is part of the solution rather than part of the =
problem.

>=20
>>> 3. 99.99% of customers don't notice they are transiting CGNAT, it =
just
>>> works.
>>=20
>> More precisely: you don't hear from 99.99% of customers, regardless =
of
>> whether or not they notice problems that are caused by CGNAT.  People =
put up
>> with some *really* bad stuff sometimes without mentioning it to their
>> service provider.
>=20
> Like modems that introduce 2 second queuing delays the moment you
> have a upstream transfer like a icloud backup.  Buffer @!#$!@#$!
> bloat!

Among other things.

99.99% of customers don=92t now how to isolate the fault of such a thing =
to their ISP or how to properly complain about it in my experience. For =
the 0.01% who do, 99% of them don=92t know how to get past the ISP=92s =
first-line =93let=92s reboot your modem and when you call back =
afterwards, you won=92t be my problem any more=94.

Owen


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