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 ]
Philip Homburg
pch-ripeml at u-1.phicoh.com
Fri May 29 14:51:47 CEST 2020
>As previously stated, I think that everyone [in our community] is able to >get IPv6. So this is not about promoting communication failures, but >switching over to a protocol from which we all benefit. In my experience, if you make people jump through hoops, you don't get any buy-in. Yes, they may be able to figure out how to set up a tunnel to access your service, but they will never do anything to support IPv6 in their own products or services. >> 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. > >You have a point and it has actually been started about a year ago: > >https://redmine.ungleich.ch/projects/ipv6/wiki/IPv6_Hardware_Compatibility_Lis >t What I meant was services: - what to use instead of github (probably gitlab) - what to use instead of zoom (maybe jitsi, but does jitsi scale?) - and where this discussion started, what to use instead of eventbrite.nl
- 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 ]