[ipv6-wg] IPv6 experiments at future RIPE Meetings

Hi James & all,

I missed the "Berlin experiment" and i honestly feel those experiments are 
only useful to allow "IPv6 advocates" to check if they can really 
live/function without the "safety net" that IPv4 really is. :-)

I already know i can have 100% functionality with IPv6-only, because there 
is some stuff on my domain that i have absolutely no control.

IMHO, for the meeting "neutral attendee" this kind of experiment may
become a pain, and it may, to some extent, create/increase resistance to 
IPv6 usage/deployment.

So, if the NCC is interested in allowing people to test how ready they 
really are to survive without IPv4 i would advice on installing one 
wifi access point a bit away from where most people concentrate, and 
clearly tag that area as "No IPv4 available here".
You might even want to "stamp" the floor with colorful arrows driving 
people for the edge "Test-how-will-you-survive-without-v4" zone. :-))


Best Regards,
Carlos


On Tue, 2 Feb 2010, James Aldridge wrote:

> Reading the minutes of the IPv6 WG at RIPE 59 I read:
>> David asked the audience if the IPv6 Hour should be rerun at future
>> meetings.. There is consensus that it should be.
>
> Rob Blokzijl has asked that we treat the RIPE Meeting network as a production 
> network. This effectively means that we won't be turning off the dual-stack 
> network for another "IPv6 Hour".
>
> What we can do is to build the IPv6 only networks as we did in Berlin and 
> make these available to anyone who wants to use them, but without the 
> complications caused by the IPv6 Hour.
>
> One question that remains is whether, with rfc2766 now "historic", providing 
> NAT-PT on the IPv6-only networks is worthwhile for RIPE 60 and future 
> meetings.  Would it be enough just to provide the IPv6 networks but without 
> any translation to be able to reach the IPv4 legacy Internet?
>
> Any feedback would be appreciated.
>
> Regards,
> James
>
> -- 
> James Aldridge, Senior Systems & Network Engineer, RIPE NCC
> RIPE Meeting technical team
>
>