On Tue, Nov 03, 2015 at 11:21:42AM +0900, Shane Kerr wrote: > Marco, > > My impression is that you are representing the RIPE NCC's > (semi-)official stance on this subject, so even though I am addressing > this to you my mail is really intended to be towards the company. > > tl;dr Don't so cautious. Removing the "experimental" tag from IPv6 won't > ruin the RIPE meeting. > > > Honestly, I think that the RIPE NCC is being way too cautious. The > remedy in all cases is simply "pick this other SSID". > > Really, it's that simple! > > Even the most technically inept users are experienced with selecting > alternate WiFi networks. > > I suppose there may be users who really, REALLY want to debug their > setup (perhaps they are tired of their corporate VPN not working over > IPv6-only, or something like that). In that case, the RIPE NCC > certainly has no responsibility to work with these people, unless the > company wants to and has spare resources. (There will be RIPE > participants who are willing to help, so such people might be able to > fix their setups with assistance from enthusiastic experts.) >
+1 here folks. I have to agree with Shane's sentiments here. The "fix" for any problems is so trivial I really don't think transitioning the IPV6 only SSID from experimental to fully published, part of the standard meeting literature and on site advertisements is a problem. Fair play to Marco and co for wanting to ensure absolute perfection (in as near as can be) with regards to the meeting network(s) but suffice to say, I trust the RIPE ops folks implicitly to run a good set of networks for all of us. I also trust them to be able to help any users with problems (on either network). See you all in Romania anyway. -- Mick O'Donovan | Network Engineer | BT Ireland | Website: http://www.btireland.net Looking Glass: http://lg.as2110.net Peering Record: http://as2110.peeringdb.com AS-SET Macro: AS-BTIRE | ASN: 2110
signature.asc
Description: Digital signature
