[ipv6-wg] IPv6 experiments at future RIPE Meetings
- Previous message (by thread): [ipv6-wg] IPv6 experiments at future RIPE Meetings
- Next message (by thread): [ipv6-wg] IPv6 experiments at future RIPE Meetings
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Tue Feb 2 15:53:11 CET 2010
James, On 2010-02-02 15:18, 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". Sure, makes sense. > 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. For the IPV6-only with translation, we should consider one of the transition tools now available. ISC (my company, although I have had no involvement with this software) just released AFTR: https://www.isc.org/software/aftr It's open source, gratis, libre, and so on. I do think RIPE meetings should switch to RFC 1918 addresses for both IPv4/IPv6 and IPv4-only networks ASAP. These are heavily used, even in production networks. Probably too late for the next RIPE meeting, but shouldn't be a problem for subsequent ones. -- Shane
- Previous message (by thread): [ipv6-wg] IPv6 experiments at future RIPE Meetings
- Next message (by thread): [ipv6-wg] IPv6 experiments at future RIPE Meetings
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]