Ipv6 Routing (from hell)
Michael Taht
m at teklibre.com
Fri Mar 28 01:31:00 CET 2008
Steve Bertrand wrote:
> ...sorry about the long post. I didn't expect for it to go this way,
> I'm just a little out of sorts that I don't have many IPv6 people I
> can relate to.
>
>> Folks are debating about giving such networks one routing slot
>> already (see the PI discussions), doing PI and BGP on those networks
>> either results in internal congestion (announcing a /48 on all
>> ingress points and forwarding the traffic all the way through the
>> mesh to the destination) or deaggregating to possibly hundreds of
>> routing slots for optimized ingress in reasonably sized networks.
>
> Even on the smallest of ISP networks, this would be an administrative
> nightmare.
>
>> And remind you, we are usually talking about dozens of el-cheapo 20
>> EUR consumer DSL connections to different ISPs in those meshing
>> networks, there is just no way of getting native IPv6 with BGP on there.
>
> We are a small ISP in southern Ontario Canada, and even with our
> 100Mbps LANx connection, can not get native IPv6 from our upstream.
> The temporary solution for the el-cheapos (as you put it) is obviously
> tunneling, but the real fix and long term solution is a massive
> collective vocal "we want IPv6!!" by all of the DSL consumers to their
> ISPs.
>
A very open and interesting discussion about the difficulties of rolling
out IPv6 ADSL services to consumers from a large ISP's standpoint is at:
http://forums.whirlpool.net.au/forum-replies-archive.cfm/928341.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20080328/55c312e0/attachment.sig>
More information about the ipv6-ops
mailing list