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
Thu May 28 15:48:43 CEST 2020

> The point was that the NCC is marketing an "IPv6 only" event, using
> a service provider who is not reachable from an IPv6 only client
> network.

I agree. It is sad to see how little IPv6 support there is by content and
services on the internet.

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