[167168] in North American Network Operators' Group
Re: AT&T UVERSE Native IPv6, a HOWTO
daemon@ATHENA.MIT.EDU (Owen DeLong)
Mon Dec 2 22:07:36 2013
From: Owen DeLong <owen@delong.com>
In-Reply-To: <op.w7hvgey1tfhldh@rbeam.xactional.com>
Date: Mon, 2 Dec 2013 19:03:59 -0800
To: Ricky Beam <jfbeam@gmail.com>
Cc: NANOG List <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Dec 2, 2013, at 18:20 , Ricky Beam <jfbeam@gmail.com> wrote:
> On Mon, 02 Dec 2013 20:27:36 -0500, Owen DeLong <owen@delong.com> =
wrote:
>>> They could be do much worse... if you throw out SLAAC, your =
network(s) can be smaller than /64. I don't want to give them any =
ideas, but Uverse could use their monopoly on routers to make your lan a =
DHCP only /120.
>>=20
>> I think if they did that, they'd do more to evaporate Uverse =
customers than to change the world of IPv6 routing at this point.
>=20
> I'd like to see the results of such an experiment. I suspect 90% of =
their users wouldn't even notice. (given how many don't even realize =
IPv6 is on, until some site(s) run dog slow until they're told (how) to =
turn IPv6 off.)
>=20
> Not counting MAC users, because they cannot do DHCPv6 without 3rd =
party software.
My Macs seem to do DHCPv6 just fine here without third party software, =
so I'm not sure what you are talking about.
>=20
> Nobody really cared with they limited what RFC1918 space you could =
use. (not sure they're still doing that.)
Not sure what you mean here since RFC-1918 is IPv4 only.
Owen
