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] Clear Guidance for Enterprises
- Previous message (by thread): [ipv6-wg] Clear Guidance for Enterprises
- Next message (by thread): [ipv6-wg] Clear Guidance for Enterprises
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jordan A. Borgner
jab at manmtr.net
Sun Jun 4 22:16:58 CEST 2023
On 6/3/23 12:33, Gert Doering wrote: > So, what else can we do? At the end a number of factors that make up the big picture must play together to roll that stone up the hill, and all of them influence one another, at least a bit. Compatibility to other networks, amount of work to maintain the own network, demand on IPv6 products, better offers of IPv6 products etc, you called it. Making IPv4 expensive is one good step. An official renaming of IPv4 to "Legacy IP" or "IP Legacy", at least by the vendors, might be a good psychological trick. What's very important too is to get the application developers on board. Advances in the software that uses the network (and gives it its reason to exist) is a crucial factor I think. If there are technical benefits that can be achieved using IPv6 but not Legacy IP (too tired to think of some now), you may feel a difference between IPv6 and Legacy IP at some point and the latter may become outpaced. So developers need to be convinced too. And taught about it. -- Jordan A. Borgner
- Previous message (by thread): [ipv6-wg] Clear Guidance for Enterprises
- Next message (by thread): [ipv6-wg] Clear Guidance for Enterprises
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]