While I am unable to be at RIPE-71, I cannot refrain from wondering why are we so shy/afraid of IPv6...
FOSDEM (those layer-7 people) did an IPv6-only (strange name IMHO because it had NAT64), so, why wouldn't a meeting about IP be as assertive about IP? -éric (fool enough to run a dual-stack large conference WiFi with Gert D., Gunter, Andrew and others back in 2010 or even earlier) On 26/10/15 11:35, "ipv6-wg on behalf of Luuk Hendriks" <[email protected] on behalf of [email protected]> wrote: >On Mon 26 Oct 2015, 11:23, Piotr Strzyzewski wrote: >> On Mon, Oct 26, 2015 at 11:02:52AM +0100, Gert Doering wrote: >> > On Mon, Oct 26, 2015 at 10:46:02AM +0100, Ond??ej Caletka wrote: >> > > I think the technology is mature enough to be provided as a regular >>RIPE >> > > NCC service during the meeting - that means regular network name >>and, >> > > most important, a password that is propagated in the same way the >>normal >> > > Wi-Fi network password is. This is especially important for the one >> > > third of newcomers that have had a big troubles learning the >>password of >> > > the IPV6ONLYEXP network. >> > > >> > > After RIPE 70, I proposed a "drastic" approach [1], renaming the >> > > dual-stack meeting network to -legacy and promote the NAT64 network >>as >> > > the default. This is the same way they do it on FOSDEM since 2014 >>[2]. >> > > But maybe we could try a slow start first, keeping the dual-stacked >> > > network the default and offering the NAT64 network with some suffix >>like >> > > -v6only. >> > >> > I'm with you that we should no longer market the IPv6-only as "this >>is an >> > experiment, it will not work, and is unreliable anyway, so use on your >> > own risk!" network. This is what Internet looks like on more and more >> > mobile networks already today - time to get used to it. >> >> +1 >> >> > OTOH, I'm not sure whether it should be default - can Android cope >>with >> > IPv6-only networks today? If yes, then go for it :-) - if not, maybe >>not >> > this year... >> >> If not, Android users could use this "-legacy" network the same way like >> so called "pioneers" use this "experimental" one last time at RIPE >> Meeting. > >What I remember from the last meeting is that often the applications seem >to be the problem (Skype, for example). I think the most important thing >here is the availability of 'troubleshooting information', so people know >where to look in case things don't work. >Jen made a list with troublesome applications: if that list is available >at the network operation room, it can function as a shortcut. 'Program $X >is not working? Try the legacy ssid' > >And +1 on removing terminology like 'legacy'. > > > luuk >
