[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 ]
Shane Kerr
shane at time-travellers.org
Wed Feb 3 12:07:22 CET 2010
Martin, On 2010-02-03 10:58, Martin Millnert wrote: > On Wed, 2010-02-03 at 10:01 +0100, Gert Doering wrote: >> 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. > Short version: > > I second this statement. This makes sense. Although of course I would like this to be something like: RIPE 61: ESSID RIPE is globally-unique IPv4+IPv6, ESSID RIPE-NAT is NAT IPv4 plus globally-unique IPv6 RIPE 63: ESSID RIPE is NAT IPv4 plus globally-unique IPv6 ESSID RIPE-NO-NAT is globally unique IPv4+IPv6 In the future we could further mimic the "real world" by charging money for the use of the RIPE-NO-NAT network. For a sufficently massive fee we could probably even keep addresses persistent between meetings. ;) -- Shane
- 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 ]