[162587] in North American Network Operators' Group
Re: "It's the end of the world as we know it" -- REM
daemon@ATHENA.MIT.EDU (joel jaeggli)
Fri Apr 26 01:27:38 2013
Date: Thu, 25 Apr 2013 22:27:19 -0700
From: joel jaeggli <joelja@bogus.com>
To: nanog@nanog.org
In-Reply-To: <20130426051650.GC26847@hezmatt.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 4/25/13 10:16 PM, Matt Palmer wrote:
> On Thu, Apr 25, 2013 at 07:49:03PM -0700, Michael Thomas wrote:
>> On 04/25/2013 07:27 PM, Owen DeLong wrote:
>>> AWS stands out as a complete laggard in this area.
>> Heh... that's why I put all kinds of question marks and hedges :)
>> That's disappointing about aws. On the other hand, if aws lights
>> up v6, a huge amount of content will be v6 capable in one swell-foop.
> Even if the only thing that supported IPv6 was ELB, and everything else was
> still IPv4 internally, that'd put a lot of traffic on IPv6 very quickly, and
> ELB is something *entirely* controlled by AWS (you CNAME to an ELB FQDN, AWS
> takes care of resolution and proxies a TCP connection to your instance).
elb ipv6 support has been in place for some time (may 2011 for us east
and ireland)
"IPv6 support is currently available in the following Amazon EC2
regions: US East (Northern Virginia), US West (Northern California), US
West (Oregon), EU (Ireland), Asia Pacific (Tokyo), and Asia Pacific
(Singapore).?
>
> - Matt
>
