[ipv6-wg] IPv6-only network during RIPE 71
- Previous message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
- Next message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jen Linkova
furry13 at gmail.com
Tue Nov 3 14:45:12 CET 2015
On Tue, Nov 3, 2015 at 11:53 AM, Philip Homburg <pch-ripeml at u-1.phicoh.com> wrote: > The network at RIPE meetings currently provides a good network experience. > The wifi works, there is IPv6 that works, and for those > living in the past (which is essentially all of us, because only > a small fraction of the internet is actually reachable over IPv6), there is > also native IPv4. > > The surprising thing to me is that there is a request to the ops team > at the meeting to provide broken IPv4 by default. > > I can understand the desire to have experimental networks at a meeting > to test what works and what doesn't work. > > But why should such a broken network be default? There are many broken > networks in the world. Wifi often doesn't work, in many places there is > no 3G GSM. Do we want to replicate that as well at a RIPE meeting? I'm not sure I understand why you are calling v6-only network 'broken one'? I've been sitting in v6-only network at RIPE meetings since that SSID was introduced. I'm in Japan now and so far I did not have to connect to dual-stack SSID - v6-only works just fine. What exactly (besides a few applications) is broken here? > (Can't wait for a request for Atlas to support NAT64, that's going to be > interesting) RIPE Atlas probe is a host. It should not care much if it's traffic is going via NAT64 box or not. -- SY, Jen Linkova aka Furry
- Previous message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
- Next message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]