[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: draft-arkko-ipv6-transition-guidelines WGLC






On Tue, 31 Aug 2010, Gunter Van de Velde (gvandeve) wrote:

Next to that... teredo and 6to4 are non-managed services, while 6rd is a managed service... big difference for the user experience.

http://tools.ietf.org/html/draft-vandevelde-v6ops-harmful-tunnels-01

What do you mean about managed service? I think 6to4 and teredo can be managed....

Best Regards,
		Janos Mohacsi


G/

-----Original Message-----
From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] On Behalf Of Rémi Després
Sent: Tuesday, August 31, 2010 6:07 PM
To: Randy Bush
Cc: Cameron Byrne; IPv6 v6ops
Subject: Re: draft-arkko-ipv6-transition-guidelines WGLC


Le 19 ao?t 2010 ? 08:09, Randy Bush a écrit :

from 10,000m, what is 6rd but a teredo/6to4 that colludes with the
provider who won't do real v6?  it's a cute hack, but a hack.

Descending to 100m, one can see that, unlike Teredo and 6to4, 6rd provides native IPv6 prefixes to customer sites, unlike Teredo and 6to4:
- Hosts behind a 6rd CPE are on a dual-stack LAN, and can't determine whether the ISP network is dual stack throughout or 6rd.
- From 6rd sites, connectivity with other IPv6 native addresses is guaranteed, which is the case with neither Teredo nor 6to4.

You told me once that, for you, "hack" had no negative connotation.
Then, "cute hack" can nicely be taken positively, thanks ;-).

Cheers,
RD

PS: Note that I have absolutely no financial interest in any of its actual applications, just being proud of having originated a useful mechanism.