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 Agenda
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Benedikt Stockebrand
bs at stepladder-it.com
Fri May 6 19:10:09 CEST 2016
Hi Jens and list, Jens Link <jenslink at quux.de> writes: > Benedikt Stockebrand <bs at stepladder-it.com> writes: > >> 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. > > Can't be that relevant if it was not monitored properly. sorry, but I really can't publicly get into the details of that. Let's just say this was the tip of the iceberg, or the trailer of the TV series, or the reason I got so fond of drain cleaner... 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 Agenda
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]