Re: [v4tov6transition] draft-arkko-ipv6-transition-guidelines WGLC

[Randy Bush <randy@psg.com>]

> Free.FR deployed an IPv6 service in their existing IPv4 network using
> 6rd with a team of a couple of people and a month's time if I have the
> story straight.

first, all free.fr stories are one engineer in two weeks.

second, we should not confuse this with ipv6 deployment, as your words
are very careful to hint.  this is one way to hack ipv6 service when you
do not deploy ipv6 in your network.

i do not mean to dis free.fr.  really great isp (with abyssmal customer
service).  but we really need to differentiiate ipv6 deployment from
hacks to get around non-deployment.

and they are not 'transition' mechanisms, as the network is not being
transitioned to ipv6.  just another hack to get around non-transition.
but a lot better than teredo, 6to4, ...

> That involved almost no actual native IPv6; 6rd is an IPv6/IPv4 tunnel
> infrastructure. But it allowed them to provide both IPv4 and IPv6
> *services* to their customers while they took time to think about what
> they wanted to do natively. They can change their network under the
> hood, so to speak, an their own schedule.

yep.  one good strategy if you do not want to deploy ipv6.

> Comcast has been a proponent of ds-lite.

well, alain was.  i would judge comcast by what it actually has done.

> And yes, CERNET's case demonstrates that stateless translation between
> an IPv4-only infrastructure and an IPv6-only infrastructure in fact
> works.

well, with some difficulty, as there are a lot of tunnels to get to the
ipv4 internet.

randy