Tunnel overhead [On killing IPv6 transition mechanisms]

[Doug Barton]

On 03/16/10 17:40, Brian E Carpenter wrote:
> Gert,
> 
> The problem is tunnels. The first example is from University of Auckland
> via Telstraclear and a HE tunnel. IPv6 penalty is about 390 ms round trip,
> crossing one ocean. 

Here is another data point, from my home in Southern California, to the
ARIN web servers on the East coast (Ashburn if I'm reading the traces
correctly).

IPv4:
ping -c 20 -s 1024 www.arin.net
--- www.arin.net ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 82.205/84.069/100.077/3.739 ms

IPv6 (through the HE.net tunnel in Fremont, CA):
ping6 -c 20 -s 1024 www.arin.net
--- www.arin.net ping6 statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 107.004/114.436/183.481/18.180 ms

That's a 30 ms penalty for the tunnel, which I have never found to be
unduly burdensome. With the same ping options I get even better results
for some sites:

--- ipv6.l.google.com ping6 statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 47.204/48.537/50.859/0.926 ms

For certain things the tunnel is actually _faster_ than IPv4, but that's
because I picked a tunnel endpoint that's co-located with the stuff I
want to access. :)

To make sure we're comparing apples to apples, this is a proto 41 tunnel
set up on my home router, providing "native" IPv6 to my laptop.

Doug

-- 

	... and that's just a little bit of history repeating.
			-- Propellerheads

	Improve the effectiveness of your Internet presence with
	a domain name makeover!    http://SupersetSolutions.com/