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 ]
Jens Link
lists at quux.de
Fri May 29 09:38:40 CEST 2020
Nick Hilliard <nick at foobar.org> writes: > having the meetings, for starters. Sure. Let's talk more about deploying IPv6. Did work very well for the last decade / years. Personally I think that one thing that might work better is to avoid IPv4 only services when there is an alliterative service with IPv6 enabled. One only has some little extra work, like installing a browser plugin and watching the output. So do not complain that $ISP has no IPv6 choose an alliterative if you can. If the git web service you are using does not complain and open tickets, choose an alternative. If your CDN does not fully support IPv6 do not complain and choose an alternative. .... 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 ]