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

Hi Marco,

Thanks a lot for such detailed response.
Some comments inline:

On Thu, Oct 29, 2015 at 11:30 AM, Marco Hogewoning <marcoh at marcoh.net> wrote:
> Our primary concern is that within the resource constraints we have on staff time and expertise, we cannot offer detailed support to end users, who are experiencing problems.

Hopefully most of support which is specific to IPv6-only network
should be 'please switch to  dual-stack and let us know if it helps'.

> Taken into account the discussion in this working group, we do agree that labelling the IPv6-only network as “experimental” might have unintended consequences and leave the impression that IPv6 is not ready for deployment.
>
> We support the working group in their efforts to change the messaging surrounding this initiative to make it appear less experimental and put more confidence in IPv6 as a technology, which is ready for broad deployment.
>
> At the same time we are not assured that an IPv6-only environment will not lead to any problems at the user level, which might be perceived as a problem with the RIPE meeting network.
>
> We are happy to work with the community in implementing changes to the network name and documentation and promotion efforts. Our IT staff has confirmed that we can change the name and password without much effort and this can be done prior to RIPE 71.

I agree that we should take baby steps and do not change too many
things at once.
If we can get rid of 'experimental' label prior to RIPE71 it would be great.

> However we must also insist that, at this stage, that there must be no confusion with the primary dual stack network, which is supported by RIPE NCC staff.
>
> On an additional note we must warn the community on the use of any relative or subjective names such as “new” and select an alternative that provides a functional description of the network.

What about
- changing SSID name to smth like 'RIPEMTG-NO-V4' or 'RIPEMTG-NAT64'?
As it would be a new SSID, it minimized chances of people connecting
to it accidentally, w/o understanding what they are doing.
- stop using the word 'experimental' and list this new SSID among
other SSIDs set up for the meeting?


> We invite the community to use this upcoming RIPE meeting to collect further feedback and develop user level documentation on any remaining problems and any possible workarounds that could avoid such issues.
>
> We hope that this documentation in turn can form the basis for a discussion with the broader RIPE community on a proposal to change configuration of the primary network and provide confidence that such a change would not lead to any operational problems for RIPE meeting attendees or otherwise have impact on the stability of the RIPE NCC operated infrastructure.

As this topic seems to be a hot one for this WG, I'm planning to
reserve some time during the WG session in Bucharest for the
'open-mic' discussion.

-- 
SY, Jen Linkova aka Furry