[6bone] report of 6bone planning BOF

[Jeroen Massar]

Mark Prior [mailto:mrp@mrp.net] wrote:

> At 11:18 PM +0100 19/3/03, Jeroen Massar wrote:
> >JORDI PALET MARTINEZ wrote:
> >
> >> You will discover soon that this will change in the next few
> >> months ...
> >
> >And I guess you are talking about the cost waiver
> >that is being proposed ;) But it is still to see
> >if that will also make the ISP's actually use it...
> >Fortunatly there are a couple of very good
> >transition methods which can help out in the
> >cases where native IPv6 is still not an option.
> >
>
> The router vendors have got to get IPv6 support out in the 
> code releases & platforms the ISPs want to run without 
> requiring them to upgrade the hardware or move to different 
> code streams (with a whole set of new bugs).

I know of one vendor for which you really do want to move
to a different code stream :)

But in those cases I think, certainly for the time being
these links can be IPv6'ed using some good reliable tunneling.
The ISP's can then upgrade when they deem it stable enough.
Note that I am talking about using 6in4 as an alternative
to native IPv6 because the underlying hardware can't cope
with it yet, or the ISP in question doesn't trust the new
code bases yet. These tunnels will then have a max of 3 hops
in the IPv4 world and never cross an AS boundary. Also see:
http://ip6.de.easynet.net/ipv6-minimum-peering.txt

Greets,
 Jeroen