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/ipv6-wg@ripe.net/
[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 ]
Michel Py
michel at arneill-py.sacramento.ca.us
Mon Oct 7 06:07:10 CEST 2019
> Kai 'wusel' Siering > Rationale: an internal network needing more than 16 million IPv4 addresses (10/8) does have the power to solve their > addressing needs with IPv6. This isn't true for newcomers that have to deal with old players not enabling v6. I do not agree because it does not fit my use-case, but this is the best argument I have heard for many years. Keep in mind though : your idea is great, but it has been tried many times, for more than a decade, including by people who are respected players, big shots, and have serious clout, and it has repeatedly failed. What makes you think that you can make it work ? Everyone has tried, everyone has failed. Multiple times. I must have missed what news you have about it. Michel.
- 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 ]