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 ]

Sander Steffann sander at steffann.nl
Sat Oct 5 18:11:18 CEST 2019

Hi,

> One way to look at the problem is that IPv4 exhaustion is a problem of externalities: my network is growing, and it costs me more now because you don't support IPv6. As an economic problem, then, think about how to shift your costs to those who have only IPv4.

"We only do settlement-free peering on IPv6" ?

Cheers,
Sander

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: </ripe/mail/archives/ipv6-wg/attachments/20191005/3ddc338a/attachment.sig>

• 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 ]