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] Have we failed as IPv6 Working Group?
- Previous message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
- Next message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Mon Oct 7 13:19:21 CEST 2019
Gert Doering wrote on 07/10/2019 11:56: > I take a bit of offense here. We did what we could to "protect the > newcomers" with the "last /22" policy, but "gone is gone" - there just is > not enough v4, what else could we have done? No need to take offense - it's normal for our species to want to assign blame when we're upset, and even more normal to want to fling poo at other people to show how upset we are. It's not as if ipv4 exhaustion snuck up on everyone unnoticed. If people don't like how things were handled, then why they didn't pipe up with their suggestions while the problem was being discussed any time over the last 25 years? It seems a bit odd to start complaining at the point that the registries were scraping the last bits of address space from the bottom of the barrel. Nick
- Previous message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
- Next message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]