Youtube-over-IPv6

FAHAD ALI KHAN fahad.alikhan at gmail.com
Fri Jan 29 07:57:42 CET 2010


>From Pakistan, i observe the streaming through pure IPv4, not through v6 in
v4 tunnels.

Nor i find AAAA entries against www.youtube.com.

*Regards

Fahad Ali Khan*

On Fri, Jan 29, 2010 at 11:48 AM, Shaun Ewing <s.ewing at aussiehq.com.au>wrote:

>
>
> On 29/01/10 11:45 AM, "Erik Kline" <ek at google.com> wrote:
>
> > But hopefully it's working well and correctly.
>
> Good work, but there's a huge latency difference between v4 and v6 where I
> am (Australia) and I seem to get v6 addresses out of a Google Ireland range
> (2a00:1450::/32) from one set of our Google over V6 resolvers and the usual
> Google range I'm used to (2001:4860::/32) from another set of our
> resolvers.
>
> Despite that, there's no noticeable difference to user experience (ie:
> videos seem to play fine) so I guess that's the key factor here.
>
> Anyway, some info below if it's any use:
>
> Our main resolvers use anycast within our network, but when using the ones
> in my local city (CBR - which query from 203.88.112.0/24):
>
> IPv4:
>
> $ dig +short v21.lscache1.l.google.com A
> 74.125.109.30
>
> --- 74.125.109.30 ping statistics ---
> 5 packets transmitted, 5 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev = 5.132/5.264/5.560/0.154 ms
>
> And
>
> traceroute to 74.125.109.30 (74.125.109.30), 64 hops max, 52 byte packets
>  1  172.20.10.254 (172.20.10.254)  1.673 ms  1.064 ms  1.265 ms
>  2  172.16.0.1 (172.16.0.1)  0.257 ms  0.164 ms  0.166 ms
>  3  vl2.cor1.cbr1.as24557.net.au (203.88.112.252)  6.260 ms  9.195 ms
>  1.166
> ms
>  4  gi0-2-4.bdr2.cbr1.as24557.net.au (203.88.112.18)  0.582 ms  0.522 ms
> 0.468 ms
>  5  gi0-2-4.bdr1.syd1.as24557.net.au (203.88.112.21)  5.492 ms  5.167 ms
> 5.044 ms
>  6  as15169.sydney.pipenetworks.com (218.100.2.98)  5.106 ms  5.113 ms
> 5.287 ms
>  7  64.233.174.253 (64.233.174.253)  5.515 ms  5.220 ms  5.738 ms
>  8  74.125.109.30 (74.125.109.30)  5.210 ms  5.300 ms  5.384 ms
>
> Vs
>
> IPv6:
>
> $ dig +short v21.lscache1.l.google.com AAAA
> 2a00:1450:4001:3::1e
>
> --- 2a00:1450:4001:3::1e ping6 statistics ---
> 5 packets transmitted, 5 packets received, 0.0% packet loss
> round-trip min/avg/max/std-dev = 351.175/354.353/355.477/1.600 ms
>
> And
>
> traceroute6 to 2a00:1450:4001:3::1e (2a00:1450:4001:3::1e) from
> 2405:5000:XX, 64 hops max, 12 byte packets
>  1  2405:5000:XX  0.882 ms  0.766 ms  0.793 ms
>  2  vl2-gw.cbr1.as24557.net.au  0.478 ms  0.389 ms  0.414 ms
>  3  gi0-1-3.bdr2.cbr1.as24557.net.au  0.610 ms  0.541 ms  0.469 ms
>  4  ge-0-0-0-700.bdr01.cbr01.act.vocus.net.au  0.714 ms  0.759 ms  0.699
> ms
>  5  2402:7800:0:2::35  4.757 ms  6.414 ms  4.866 ms
>  6  ge-0-0-2.bdr02.syd01.nsw.vocus.net.au  4.922 ms  4.945 ms  4.758 ms
>  7  2402:7800:0:2::3e  5.571 ms  11.963 ms  5.184 ms
>  8  * * *
>  9  * * *
>
> And when querying our other set of resolvers in SYD (these query from
> 113.20.0.0/24):
>
> IPv4:
>
> $ dig +short v21.lscache1.l.google.com A
> 74.125.98.30
>
> --- 74.125.98.30 ping statistics ---
> 5 packets transmitted, 5 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev = 276.145/276.523/277.288/0.451 ms
>
> And
>
> traceroute to 74.125.98.30 (74.125.98.30), 64 hops max, 52 byte packets
>  1  172.20.10.254 (172.20.10.254)  1.834 ms  1.065 ms  1.072 ms
>  2  172.16.0.1 (172.16.0.1)  0.245 ms  0.169 ms  0.182 ms
>  3  vl2.cor1.cbr1.as24557.net.au (203.88.112.252)  0.732 ms  0.801 ms
>  0.733
> ms
>  4  gi0-2-4.bdr2.cbr1.as24557.net.au (203.88.112.18)  0.668 ms  0.563 ms
> 0.522 ms
>  5  gi0-2-4.bdr1.syd1.as24557.net.au (203.88.112.21)  5.993 ms  4.816 ms
> 4.714 ms
>  6  as15169.sydney.pipenetworks.com (218.100.2.97)  5.656 ms  6.546 ms
> 5.921 ms
>  7  66.249.95.234 (66.249.95.234)  6.634 ms  5.372 ms  5.466 ms
>  8  209.85.249.52 (209.85.249.52)  108.913 ms  105.382 ms  105.407 ms
>  9  209.85.255.34 (209.85.255.34)  107.364 ms  134.131 ms  107.195 ms
> 10  72.14.232.114 (72.14.232.114)  176.733 ms  177.158 ms  175.981 ms
> 11  209.85.242.233 (209.85.242.233)  181.669 ms  181.570 ms  181.603 ms
> 12  66.249.94.39 (66.249.94.39)  219.298 ms  220.909 ms
>    209.85.242.235 (209.85.242.235)  182.338 ms
> 13  209.85.241.53 (209.85.241.53)  276.365 ms  278.211 ms  276.176 ms
> 14  66.249.94.90 (66.249.94.90)  219.789 ms
>    216.239.43.215 (216.239.43.215)  351.971 ms
>    66.249.94.90 (66.249.94.90)  219.523 ms
> 15  * * *
> 16  74.125.98.30 (74.125.98.30)  276.886 ms
>    216.239.43.215 (216.239.43.215)  277.086 ms
>    74.125.98.30 (74.125.98.30)  276.653 ms
>
> vs
>
> IPv6:
>
> $ dig +short v21.lscache1.l.google.com AAAA
> 2001:4860:4001:402::1e
>
> --- 2001:4860:4001:402::1e ping6 statistics ---
> 5 packets transmitted, 5 packets received, 0.0% packet loss
> round-trip min/avg/max/std-dev = 208.170/210.646/216.873/3.290 ms
>
> And
>
> traceroute6 to 2001:4860:4001:402::1e (2001:4860:4001:402::1e) from
> 2405:5000:XX, 64 hops max, 12 byte packets
>  1  2405:5000:XX  1.301 ms  0.852 ms  1.014 ms
>  2  vl2-gw.cbr1.as24557.net.au  0.582 ms  0.418 ms  0.464 ms
>  3  gi0-1-3.bdr1.syd1.as24557.net.au  5.688 ms  5.097 ms  26.557 ms
>  4  as15169.ipv6.sydney.pipenetworks.com  5.295 ms  8.224 ms  5.466 ms
>  5  * * *
>  6  * * *
>
> :-)
>
> -Shaun
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20100129/0608ff48/attachment.htm>


More information about the ipv6-ops mailing list