[ipv6-wg] IPv6-only network during RIPE 71

+ Marco, Nick

On Mon, Oct 26, 2015 at 11:02 AM, Gert Doering <gert at space.net> 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.
>
> OTOH, I'm not sure whether it should be default - can Android cope with
> IPv6-only networks today?

All new versions (5.x AFAIR) work well, I think I demonstrated it on
the last meeting ;)

>If yes, then go for it :-) - if not, maybe not
> this year...

Marco, Nick - what do you think? I definitely see a lot of interest
and support in the community for moving IPv6-only
network out of the experimental state. Probably moving dual-stack
network to legacy this meeting might be bit extreme (we do care about
people who do not care about Ipv6 yet, don't we? ;)) and we do not
provide bad network experience), but what about stop calling it
"experimental" and include it in the list of the standard SSIDs?

-- 
SY, Jen Linkova aka Furry