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] Join us for the RIPE NCC Educa::IPv6-only
- Previous message (by thread): [ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
- Next message (by thread): [ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Fri May 29 14:21:02 CEST 2020
Dez C wrote on 29/05/2020 09:29: > What you're proposing is the end user's perspective and its fine. We're > not just end users, we can influence things on a larger scale > (sometimes, at least) this kinda nails it. We're not appealing to end users because ipv6 is right at the bottom of the infrastructure stack and is completely boring for the same reason that e.g. cement or paint composition are boring. Sure, nerdy types like us might get excited about it, but we need to not kid ourselves that ipv6 has any mass appeal because it doesn't. People care about cat videos; people don't care how the cat videos arrive. If we want deployment, we need to create the ability to deploy ipv6 relatively easily, so that other pressures can be effective in pushing the actual deployment (e.g. pricing / NAT / policy / etc). There are lots of ways to approach this: one of them is having online meetings about deployment challenges. It isn't the only way; it's a long-term game and online deployment meetings won't cause the protocol to be deployed instantly. But it will help. Nick
- Previous message (by thread): [ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
- Next message (by thread): [ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]