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

Hi,

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?  If yes, then go for it :-) - if not, maybe not
this year...

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5023 bytes
Desc: not available
URL: </ripe/mail/archives/ipv6-wg/attachments/20151026/6808725e/attachment.bin>