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 ]

Nico Schottelius nico.schottelius at ungleich.ch
Thu May 28 15:54:16 CEST 2020

I personally think for each IPv4 only service we should create an IPv6
only service and use that for ripe/ieee/network related events.

Everyone in our community should be able to get IPv6 anywhere, anytime.

Cheers,

Nico

p.s.: Yes, I would always volunteer for providing that.

Philip Homburg <pch-ripeml at u-1.phicoh.com> writes:

>> 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.

--
Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch

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 ]