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 during RIPE 71
- Previous message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
- Next message (by thread): [ipv6-wg] : IGF Best Practice Forum document review “Creating an Enabling Environment for IPv6 Adoption"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hyrka
nick at ripe.net
Tue Nov 10 11:52:13 CET 2015
Hi Benedikt, On 07/11/15 14:29, Benedikt Stockebrand wrote: > Hi Sander, Marco, and list, > > Sander Steffann <sander at steffann.nl> writes: > >> Hi Marco, >> >>> At the moment the actual capacity of the NAT64 network is not >>> known. This means we cannot offer any guarantees on throughput or >>> the number of simultaneous connections supported. > > Marco, you still sound like a corporate lawyer:-) > >>> Meanwhile, we will gather some basic information such as number of >>> clients connected to the network. Some RIPE NCC staff might use this >>> opportunity to run tests as well. We encourage the community to keep >>> track of any issues reported and to document them together with >>> possible solutions. >> >> This bit disappoints me a bit. [...] > > Come on, Sander. The NCC ops folks (Razvan and his lot) aren't exactly > having a paid vacation trip during a RIPE meeting; they usually look > just as tired as everybody else on friday, so asking for an > unpredictable extra workload isn't exactly fair. > > It's not like I wouldn't love to hear the announcement during the > opening plenary that IPv4 is only available wired from a single switch > located in the terminal room, but looks like we'll have a couple rounds > of nagging to do. > > > What I'd like to see, and that's well in line with what Marco wrote, is > that we see if we can make as many people as possible actually try the > IPv6 network out. No longer calling it "experimental" really is an > important step here; talking about this during the opening plenary is > even more important. > > Rather than just telling the ops folks what to do or not I really > suggest we help them get the data they need to do the next step, which > is to convince as many people as possible to use the IPv6 network and > then give any feedback they can come up with. > > Oh, and one more thing: We might ease things up for ops if we actually > managed to point out during the opening plenary that people with IPv6 > stickers on their badges are generally volunteering as > experimental^Winofficial first level IPv6 support... > > @Nick: Can we do something about getting maybe 3 minutes worth of time > during the monday plenary for this, or could somebody from the regular > staff do such a quick announcement for us? We'll ask Hans Petter to add this to his introductory talk at the start of RIPE 71. Our suggestion is to post the intermission slide we're building for the v6-only network and Hans Petter can point to it, filling in the details. Cheers, Nick > > > Cheers, > > Benedikt >
- Previous message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
- Next message (by thread): [ipv6-wg] : IGF Best Practice Forum document review “Creating an Enabling Environment for IPv6 Adoption"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]