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
Sat Oct 5 19:22:09 CEST 2019

> Dave That wrote :
> That last number is pure BS. It's not a single cost. It's that last dangling
> set of apps that can't be converted to ipv6 that's the infinite cost.

It's not only the apps, it's the tools and the entire business process that is behind. I am not going to replace a ten million dollar tool to make it IPv6 compatible.

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 ]