- Mar 27, 2006
Throw in some Singapore too ;-)The peering isn't the issue, we have V6 peering sessions up wherever we can and where a peer supports it. It's just not really going anywhere to a customer.
For that, we have to deploy OSPFv3 on our entire network, which is something on our "to-do" list. Setting up more route reflectors to support BGP/V6 is also on the list, which is also part of the picture.
It's not so much a peering issue, as enabling V6 on our entire core, right up to the access networks, which is on our list of priority things to-do. Deploying IPv6 pools on each and every access router we have is also on the list.
Trust me, it's not an insignificant task.
V6 basically means running another network on top of your current fabric, which means revisiting everything, every router, every point-to-point link, every subnet, and every IP pool. I have already devised a cunning plan to script/deploy this in a phased fashion, effectively mirroring our IPv4 deployment but in an automated fashion.
For us, it is a priority, but frankly it seems that our customer base is more concerned with Bahrain, Frankfurt and AWS pings than anything else.