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] 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 ]
Jens Link
lists at quux.de
Thu May 28 16:40:57 CEST 2020
Nico Schottelius <nico.schottelius at ungleich.ch> writes: > I personally think for each IPv4 only service we should create an IPv6 > only service and use that for ripe/ieee/network related events. I once removed the A record to a wiki I run for several nerds. I won't do that again. So much crying. And you can try for yourself: Put a link on twitter to an IPv6 only resource and see how many people are complaining. > Everyone in our community should be able to get IPv6 anywhere, anytime. *should* Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink at quux.de | --------------- | ----------------------------------------------------------------------------
- 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 ]