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] ipv6-wg Digest, Vol 55, Issue 2
- Previous message (by thread): [ipv6-wg] ipv6-wg Digest, Vol 55, Issue 2
- Next message (by thread): [ipv6-wg] ipv6-wg Digest, Vol 55, Issue 2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Benedikt Stockebrand
bs at stepladder-it.com
Tue May 3 16:15:01 CEST 2016
Hi Jens and list, Jens Link <lists at quux.de> writes: > When I look for example at https://www.vyncke.org/ipv6status/detailed.php?country=de > I would say many (most?) content providers have to work on IPv6. that's the point. And I still find it difficult to tell people that the increasing number of users stuck behind DS-Lite will actually become a problem to the IPv4-only content providers---at best things will be slower, but at worst they will work less reliably. > And may I add cloud providers? No, you may not. Definitely not. Go away. And take those enterprises using them as a cheap CDN with you... > Last time I checked none of the big players (Amazon, > Google, ...) supported IPv6 in their cloud products. And what's even more frustrating: The Amazon stuff at some time supported IPv6 at least on a best effort base, but they switched it off again. Cheers, Benedikt -- Benedikt Stockebrand, Stepladder IT Training+Consulting Dipl.-Inform. http://www.stepladder-it.com/ Business Grade IPv6 --- Consulting, Training, Projects BIVBlog---Benedikt's IT Video Blog: http://www.stepladder-it.com/bivblog/
- Previous message (by thread): [ipv6-wg] ipv6-wg Digest, Vol 55, Issue 2
- Next message (by thread): [ipv6-wg] ipv6-wg Digest, Vol 55, Issue 2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]