Curious as to who is running IPv6 with TW Telecom or Cogent.
I'm wanting to turn up native IPv6 with them, And wanted to hear
thoughts/experiences.
I assume it should be a "non-event". We've already got a prefix from arin
that we are going to announce.
Nick Olsen
Network Operations
(855) FLSPEED x106
Hi,
It was very painless and straight forward with Cogent. TATA (6453) was a
little more paperwork than I anticipated and took some time to process.
---Mike
We have it up and running with cogent we have had no issues with cogent.
But have a much larger issue in everyone we need to connect with is
still using IPv4.
Cheers
Ryan
Technically it was a non-event.
Layer 8 wise, they refused to turn up IPv6 without a renewal or new order.
Time Warner Cable is demanding a new order and additional costs to support V6.
Interesting. I noticed a similar issue with ipv6.cnn.com today. I dont
see it via TATA, but see it via Cogent. So whats the story behind it
and ARIN not being seen through cogent ? Is it due to no v6 relation
bewtween he.net and Cogent ?
2620:0:2200:8:8888:8888:8888:8901 (whats with the crazy 8s?)
Router: gin-mtt-mcore3
Site: CA, Montreal - MTT, TATA COMM. INT. CENTER
Command: traceroute ipv6 2620:0:2200:8:8888:8888:8888:8901
Tracing the route to 2620:0:2200:8:8888:8888:8888:8901
1 * * *
2 * * *
3 * * *
4 * * *
---Mike
Probably. I'm seeing arin via level3, but of course level3 doesn't seem to have he.net or google peered v6 yet.
Our theory is to link 3-4 NSP dual-stack and probably setup 3+ tunnels as last resorts.
Jack
I see it as 2620:0:2200::/48 from HE ( 6939 2828 5662 ) and Cogent (
174 2828 5662)
TATA says...
Router: gin-mtt-mcore3
Site: CA, Montreal - MTT, TATA COMM. INT. CENTER
Command: show bgp ipv6 unicast 2620:0:2200::/48
% Network not in table
I wonder how many 'holes' are like this...
---Mike
TWT is no problem with IPv6.
Wow. CNN now has IPv6. That's awesome. I guess i missed the memo.
So, major players with IPv6 are?
ipv6.cnn.com (just book marked it)
ipv6.google.com (or you can have it all with a white-list)
www.v6.facebook.com
m.v6.facebook.com
ipv6.t-mobile.com (admittedly, not major a major content source, but it's mine)
And, then debunking the "dual-stack is too risky" notion is
www.ucla.edu (which is a big business by most measures) and serves
AAAA and A records without a white-list or special FQDN.
I have predicted that by the end of 2011 nearly ~50% of my network
traffic (mobile provider) can be served by IPv6 natively end to end.
I think a lot of folks that measure Facebook and Google (including
YouTube) traffic today can see how that is feasible given current
volumes and rates of growth. Hence, the viability of IPv6-only
endpoints (especially mobile) with NAT64/DNS64 as truly connecting the
IPv4 long-tail remaining 50% that will continue to shrink as more
major sites follow the CNN's path.
Cameron
Check this out for a huge list of networks and their IPv6 status for
Web, Mail, DNS, NTP, and XMPP:
Yahoo just dropped in on the IPv6 content party
http://ipv6.weather.yahoo.com/
I just bookmarked it. Well done Yahoos.
Cameron
Well,
ipv6.ycpi.ops.yahoo.net has IPv6 address 2a00:1288:f006:1fe::1000
ipv6.ycpi.ops.yahoo.net has IPv6 address 2001:4998:f00b:1fe::1000
ipv6.ycpi.ops.yahoo.net has IPv6 address 2001:4998:f011:1fe::1000
In my bgp I see only the first address, I don't see any path to two others. Do you have the route to them?
> Yahoo just dropped in on the IPv6 content party
> http://ipv6.weather.yahoo.com/
> I just bookmarked it. Well done Yahoos.Well,
ipv6.ycpi.ops.yahoo.net has IPv6 address 2a00:1288:f006:1fe::1000
ipv6.ycpi.ops.yahoo.net has IPv6 address 2001:4998:f00b:1fe::1000
ipv6.ycpi.ops.yahoo.net has IPv6 address 2001:4998:f011:1fe::1000In my bgp I see only the first address, I don't see any path to two
others. Do you have the route to them?
Missing 2001:4998:f00b:1fe::1000 but we see the other two.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
Well,
ipv6.ycpi.ops.yahoo.net has IPv6 address 2a00:1288:f006:1fe::1000
ipv6.ycpi.ops.yahoo.net has IPv6 address 2001:4998:f00b:1fe::1000
ipv6.ycpi.ops.yahoo.net has IPv6 address 2001:4998:f011:1fe::1000In my bgp I see only the first address, I don't see any path to two
others. Do you have the route to them?
I see two of them directly from yahoo : 2001:4998::/32 (that covers the
last two IPs) but the first one comes to me via HE (2a00:1288::/32)
You think many people are going to type the "v6" part of the URL
considering most people when they get v6 won't even know if they have it
or not?
These routes are all in route-views.oregon-ix.net
Most importantly, i am on the Comcast IPv6 trial and the T-Mobile USA
IPv6 trial and ipv6.weather.yahoo.com loads well for both.
route-views>sh ipv6 route 2001:4998:f011:1fe::1000
Routing entry for 2001:4998:F011::/48
Known via "bgp 6447", distance 20, metric 0, type external
Route count is 1/1, share count 0
Routing paths:
2001:470:0:1A::1
Last updated 3w5d ago
route-views>show ipv6 route 2a00:1288:f006:1fe::1000
Routing entry for 2A00:1288::/32
Known via "bgp 6447", distance 20, metric 0, type external
Route count is 1/1, share count 0
Routing paths:
2001:470:0:1A::1
Last updated 7w0d ago
route-views>sh ipv6 route 2001:4998:f00b:1fe::1000
Routing entry for 2001:4998::/32
Known via "bgp 6447", distance 20, metric 0, type external
Route count is 1/1, share count 0
Routing paths:
2001:B08:2:280::4:100
Last updated 2d01h ago
route-views>
Cameron
Only people that know what they want will type the ipv6.*.example.com
stuff. It's self selecting. This will keep the non-techies away from
the new IPv6 deployments while the network operators and content
providers work out the kinks.
I believe the life-cycle for IPv6 introduction at the biggest web
sites will be ipv6.*.example.com, then ipv6 DNS white list, then open
the flood gates. Other sites will go directly to opening the flood
gates depending on their user profiles. There is a lot of great work
going on to see what the risk is for opening AAAA to all users
Here is one take on the discussion of whitelist
http://tools.ietf.org/html/draft-livingood-dns-whitelisting-implications-01
Cameron
It's not unusual to start by testing IPv6 this way. I'm sure Yahoo will
eventually put AAAA records in for the standard URLs once they
go full production with it.
Owen
Until all the routing kinks being mentioned are all worked, out, it's
probably somewhat intentional that the namespace is being
kept separate, so that v6-aware techies can help diagnose/debug
routing oddities, DNS lookup issues, and other gotchas *before*
the rest of the population is subjected to it.
Matt
(speaking only for himself, at the moment)
We have had Cogent and recently added TWC (not TWT) and have had no
problems. We still see the majority of our IPv6 traffic go though the
NOX (I2), though.