[ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
- Previous message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
- Next message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
João Damas
joao at bondis.org
Wed Feb 3 12:24:52 CET 2010
On 3 Feb 2010, at 10:01, Gert Doering wrote: > > At the beginning of this thread, it was stated that the RIPE meeting > network is not to be treated as an experiment or testbed. > > If people think there is an interest in having a NAT-broken network > around, then please make it available on a dedicated SSID, but don't > experiment with the meeting network. yep, I agree. The last thing I need at a RIPE meeting is to have to spend additional time figuring out how the to get the net working. When attending a RIPE meeting I still need to carry on with normal work, it is not a vacation. Additionally, experiments are better done in controlled situations where one actually has the means to address the findings. BTW, IPv6 ought to continue to be considered as a production service on the RIPE network, just in case. Joao
- Previous message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
- Next message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]