![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
X-Original-To: nanog@nanog.org In-Reply-To: <5E0F32BF-74D1-4DD2-B142-234561BD7D28@delong.com> From: =?UTF-8?B?SsOpcsO0bWUgRmxldXJ5?= <jerome@fleury.net> Date: Sat, 3 Oct 2015 15:51:47 -0700 To: Owen DeLong <owen@delong.com> Cc: "nanog@nanog.org" <nanog@nanog.org> Errors-To: nanog-bounces@nanog.org On Sat, Oct 3, 2015 at 12:22 PM, Owen DeLong <owen@delong.com> wrote: > So the problem you are suggesting we focus on is mostly a solved problem. > Content Providers are progressing, modulo some serious laggards, notably > Amazon and a few others. > > newly released IOS9 and OSX El Capitan add some serious latency for v4 only content, see: https://www.ietf.org/mail-archive/web/v6ops/current/msg22455.html I'm expecting all content providers to jump on the IPv6 train now that they're behind.
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
home | help | back | first | fref | pref | prev | next | nref | lref | last | post |