[180297] in North American Network Operators' Group
Re: AWS Elastic IP architecture
daemon@ATHENA.MIT.EDU (tvest)
Sun May 31 08:27:01 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <CAAtZb4pAG2u=N+uh7zrH180yLMSuqgjVVnoL0o8oZ_NAmN3m9A@mail.gmail.com>
From: tvest <tvest@eyeconomics.com>
Date: Sun, 31 May 2015 08:26:57 -0400
To: Andras Toth <diosbejgli@gmail.com>,Matt Palmer <mpalmer@hezmatt.org>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
Point of clarification: AWS customer IP subnets can overlap, but customer V=
PCs that encompass overlapping subnets cannot peer with each other=2E In o=
ther words, the standard arguments in favor of address uniqueness still app=
ly=2E
TV
On May 31, 2015 7:23:37 AM EDT, Andras Toth <diosbejgli@gmail=2Ecom> wrote=
:
>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=2E The discussion was "no ipv6 in AWS" which is not
>true as I mentioned in my previous email=2E I did not state it works
>everywhere, but it does work=2E
>
>In fact as Owen mentioned the following, I assumed he is talking about
>Classic because this statement is only true there=2E In VPC you can
>define your own IP subnets and it can overlap with other customers, so
>basically everyone can have their own 10=2E0=2E0=2E0/24 for example=2E
>"They are known to be running multiple copies of RFC-1918 in disparate
>localities already=2E 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"
>
>Andras
>
>
>On Sun, May 31, 2015 at 7:18 PM, Matt Palmer <mpalmer@hezmatt=2Eorg>
>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=2E
>>>
>>> Official documentation:
>>>
>http://docs=2Eaws=2Eamazon=2Ecom/ElasticLoadBalancing/latest/DeveloperGui=
de/elb-internet-facing-load-balancers=2Ehtml#internet-facing-ip-addresses
>>
>> Congratulations, you've managed to find exactly the same info as Owen
>> already covered:
>>
>> "Load balancers in a VPC support IPv4 addresses only=2E"
>>
>> and
>>
>> "Load balancers in EC2-Classic support both IPv4 and IPv6 addresses=2E"
>>
>> - Matt
>>
--=20
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E
