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] Join us for the RIPE NCC Educa::IPv6-only
- Previous message (by thread): [ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
- Next message (by thread): [ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
pch-ripeml at u-1.phicoh.com
Fri May 29 14:00:08 CEST 2020
>That also means actively using, promoting and preferring IPv6 only >services. (I'm assuming that IPv6 only meens a service that is reachable only over IPv6 and not IPv4) I don't see why promoting communication failures is a good thing. Except possibly as a fun thing to nudge people to take action. For example a quiz with prizes could be hosted on an IPv6-only platform. >And not accepting hardware, software or platforms which >lack features in IPv6 only environments. I don't know where to put it, but there may be a benefit for a list that lists known internet services that do not (or poorly) support IPv6 and with replacements that do support them. Such a list may have two advantages: 1) Somebody who likes to promote IPv6 would not have to spend time looking for good alternatives to known brands 2) Being on a list of backward companies is bad pr for any company, so it may stimulate companies to get off the wrong part of the list.
- Previous message (by thread): [ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
- Next message (by thread): [ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]