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] 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
Thu May 5 12:41:23 CEST 2016
Hi Jens and list, > Seriously. Several people told me "If AWS doesn't offer IPv6 we don't > need IPv6." On the other hand someone told me "our solution for IPv6 > hosting is Amazon. Or some other cloud provider." I had a somewhat similar experience with a customer not too long (not long enough?) ago. They used AWS/S3 for some relevant stuff, and since it was done externally it wasn't properly QAed. When Amazon switched IPv6 off again, they had a little bit of an issue. We only found out kind of accidentially, especially so because they didn't want to make it all that obvious that they are using Amazon. To my knowledge they are still trying to figure out where to move everything to, and how to do such a move seamlessly. Good News[TM] is that this was outside the scope of my responsibilities, but it was still rather frustrating. 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 ]