[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AWS Elastic IP architecture
- Subject: AWS Elastic IP architecture
- From: morrowc.lists at gmail.com (Christopher Morrow)
- Date: Thu, 28 May 2015 11:30:15 -0400
- In-reply-to: <CAD6AjGQcZVcwnHCDOqoNnkmSB0+kRb7nX+a7J=ERSr2RKZk_RA@mail.gmail.com>
- References: <CADR+d4b7nUXof3ejtU9_+XFVMWg51Fo_KpfzGSsasQKjg_SAXA@mail.gmail.com> <CAD6AjGQcZVcwnHCDOqoNnkmSB0+kRb7nX+a7J=ERSr2RKZk_RA@mail.gmail.com>
On Thu, May 28, 2015 at 11:00 AM, Ca By <cb.list6 at gmail.com> wrote:
> On Thu, May 28, 2015 at 7:34 AM, Luan Nguyen <lnguyen at opsource.net> wrote:
>
>> Hi folks,
>> Anyone knows what is used for the AWS Elastic IP? is it LISP?
>>
>>
> AWS does not really talk about things like this, but i highly doubt it is
> LISP.
i sort of doesn't matter right? it is PROBABLY some form of
encapsulation (like gre, ip-in-ip, lisp, mpls, vpls, etc) ...
something to remove the 'internal ip network' from what is routed in a
datacenter and what is routed externally on the tubes.
Maybe a better question: "Why would lisp matter here?" (what makes
lisp the thing you grabbed at as opposed to any of the other possible
encap options?)