This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] IPv6 only network at RIPE 68
- Previous message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
- Next message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
MarcoH
marcoh at marcoh.net
Sat May 17 08:12:04 CEST 2014
Hi, Thanks for all your positive thoughts. Regarding bumping up the status, I already briefly spoke to Razvan. Once the RIPE68 dust has settled and everything is unpacked, we will organise a meeting to evaluate this instance and discuss the options to further progress this. To the call to provide a true IPv6 Only service, I am not a big fan. The goal when we started this was not to prove that without IPv4, the Internet as we know it does not exist. The idea is to show that there is a middle way in which you can build a network that still gives a good user experience but with far less stress on IPv4 resources. Also this provides a great testbed to see which applications or services rely on a working IPv4 stack or insist opening an IPv4 socket. I think we have to be realistic here and although everything can be build, to stick to the setup and the one (ok two) SSID we have. The setup is now pretty straightforward and does not require a lot of additional resources from the ops team or equipment. These peoples primary task is to run a meeting and provide a good experience for all attendees, doing network experiments is not their core business. At least not during the meeting itself. So any requests for additional features have to be carefully evaluated. Making sure they do not demand too much resources or risk damaging the overall experience of meeting attendees. Also keep in mind that RIPE is made up of a very broad group of people and not everybody has the technical knowledge to fix it themselves when things break. MarcoH -- Sent from mobile, sorry for the typos > On 17 mei 2014, at 00:20, Gert Doering <gert at space.net> wrote: > > Hi, > >> On Fri, May 16, 2014 at 04:24:56PM +0200, Jen Linkova wrote: >> What would be really awesome is to stop announcing that network as 'an >> experiment'. My understanding is that we need >> 1) [hardest part] get smth better than 'best effort' support level; >> 2) change the password from 'iknowbesteffort' >> 3) stop calling it 'experimental' in public >> 4) tell people that if smth does not work they should fall back to the >> 'standard' network and see if it helps. > > Seconded. This is what I disliked about the thing: the "oh, it's not > going to work for you, it's just an experiment" touch the messages > surrounding it had. > >> We could call it 'pilot', 'canary' or '1st phase of rollout' ;) > > "The future Internet" :) > > 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
- Previous message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
- Next message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]