Hi Jen, Marco and list, I personally think that at event like the RIPE meeting we should actually be one of the first to do that due to the amount of experience and of people interested in the outcome around. We'll still need the vintage stuff around as a fallback (unless I finally get around to mod my ancient Galaxy Tab 10.1), but if the NOC crowd can actually handle this, what I'd like to see are three classes of networks/SSIDs/whatever: 0) IPv4 only (for disciplinary purposes:-) 1) IPv4+IPv6 dual stacked "vintage" network 2) IPv6+NAT64 "default" network 3) IPv6-only "see what already works" network Question is: With all the stress involved running a conference network, can the NOC handle that, and how can we help them if they are actually willing to try? Jen Linkova <furry13@gmail.com> writes:
2) change the password from 'iknowbesteffort'
2a) change the password for the vintage stuff to 'iknowiamtenyearsbehind':-)
3) stop calling it 'experimental' in public
3a) and start calling the vintage stuff "dead and smelling":-)
I'm not suggesting making it a default network at the current stage but I think that it is mature enough to move out of 'experimental' phase. We could call it 'pilot', 'canary' or '1st phase of rollout' ;)
or "this is the last warning":-) SCNR OK, more seriously: Actually calling things by some name *is* important, so this is only half funny and half serious. Cheers, Benedikt -- Benedikt Stockebrand, Stepladder IT Training+Consulting Dipl.-Inform. http://www.stepladder-it.com/ Business Grade IPv6 --- Consulting, Training, Projects BIVBlog---Benedikt's IT Video Blog: http://www.stepladder-it.com/bivblog/