[118126] in North American Network Operators' Group

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

Re: IPv6 internet broken, Verizon route prefix length policy

daemon@ATHENA.MIT.EDU (Seth Mattinen)
Mon Oct 12 22:14:12 2009

Date: Mon, 12 Oct 2009 19:13:04 -0700
From: Seth Mattinen <sethm@rollernet.us>
To: nanog@nanog.org
In-Reply-To: <20091013015850.GA79898@ussenterprise.ufp.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Leo Bicknell wrote:
> 
> Worse, the problem is being made worse at an alarming rate.  MPLS
> VPN's are quicky replacing frame relay, ATM, and leased line circuits
> adding MPLS lables and VPN/VRF routes to edge routers.  Various
> RIR's are pushing "PI for all" in IPv6 based on addressing availbility.
> Some networks are actually finally using multicast for IPTV services,
> generating much larger number of entries than the global multicast table
> would otherwise indicate.
> 

It's not the RIR's fault. IPv6 wasn't designed with any kind of workable
site multihoming. The only goal seems to have been to limit /32's to an
"ISP" but screw you if you aren't one. There was no alternative and it's
been how long now? PI, multihoming, multicast, etc. is reality because
the internet is now Very Serious Business for many, many people.

Yes, I know there's hacks like SHIM6 and I don't wish to go OT into a
debate about them, so I'll just say that if there had been a viable
alternative to multihoming as we know it I think it would have been
given a go before policy got pushed to the RIR's to allow IPv6 PI.

~Seth


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