[180301] in North American Network Operators' Group
Re: AWS Elastic IP architecture
daemon@ATHENA.MIT.EDU (Owen DeLong)
Sun May 31 09:43:52 2015
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CAAtZb4pAG2u=N+uh7zrH180yLMSuqgjVVnoL0o8oZ_NAmN3m9A@mail.gmail.com>
Date: Sun, 31 May 2015 06:40:10 -0700
To: Andras Toth <diosbejgli@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
I wasn=E2=80=99t being specific about VPC vs. Classic.
The support for IPv6 in Classic is extremely limited and basically =
useless for 99+% of applications.
I would argue that there is, therefore, effectively no meaningful =
support for IPv6 in AWS, period.
What you describe below seems to me that it would only make the =
situation I described worse, not better in the VPC world.
Owen
> On May 31, 2015, at 4:23 AM, Andras Toth <diosbejgli@gmail.com> wrote:
>=20
> Congratulations for missing the point Matt, when I sent my email
> (which by the way went for moderation) there wasn't a discussion about
> Classic vs VPC yet. The discussion was "no ipv6 in AWS" which is not
> true as I mentioned in my previous email. I did not state it works
> everywhere, but it does work.
>=20
> In fact as Owen mentioned the following, I assumed he is talking about
> Classic because this statement is only true there. In VPC you can
> define your own IP subnets and it can overlap with other customers, so
> basically everyone can have their own 10.0.0.0/24 for example.
> "They are known to be running multiple copies of RFC-1918 in disparate
> localities already. In terms of scale, modulo the nightmare that must
> make of their management network and the fragility of what happens
> when company A in datacenter A wants to talk to company A in
> datacenter B and they both have the same 10-NET addresses"
>=20
> Andras
>=20
>=20
> On Sun, May 31, 2015 at 7:18 PM, Matt Palmer <mpalmer@hezmatt.org> =
wrote:
>> On Sun, May 31, 2015 at 01:38:05AM +1000, Andras Toth wrote:
>>> Perhaps if that energy which was spent on raging, instead was spent =
on
>>> a Google search, then all those words would've been unnecessary.
>>>=20
>>> Official documentation:
>>> =
http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-=
internet-facing-load-balancers.html#internet-facing-ip-addresses
>>=20
>> Congratulations, you've managed to find exactly the same info as Owen
>> already covered:
>>=20
>> "Load balancers in a VPC support IPv4 addresses only."
>>=20
>> and
>>=20
>> "Load balancers in EC2-Classic support both IPv4 and IPv6 addresses."
>>=20
>> - Matt
>>=20
