[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: Fri, 29 May 2015 11:23:50 -0400
In-reply-to: <[email protected]>
References: <CADR+d4b7nUXof3ejtU9_+XFVMWg51Fo_KpfzGSsasQKjg_SAXA@mail.gmail.com> <CAD6AjGQcZVcwnHCDOqoNnkmSB0+kRb7nX+a7J=ERSr2RKZk_RA@mail.gmail.com> <[email protected]>

On Fri, May 29, 2015 at 3:45 AM, Owen DeLong <owen at delong.com> wrote:
> Yeah, if it were LISP, they could probably handle IPv6.

why can't they do v6 with any other encap?
the encap really doesn't matter at all to the underlying ip protocol
used, or shouldn't... you decide at the entrance to the 'virtual
network' that 'thingy is in virtual-network-5 and encap the packet...
regardless of ip version of the thing you are encapsulating.

Follow-Ups:
- AWS Elastic IP architecture
  - From: owen at delong.com (Owen DeLong)

References:
- AWS Elastic IP architecture
  - From: lnguyen at opsource.net (Luan Nguyen)
- AWS Elastic IP architecture
  - From: cb.list6 at gmail.com (Ca By)
- AWS Elastic IP architecture
  - From: owen at delong.com (Owen DeLong)

Prev by Date: 10Gb CPE
Next by Date: AWS Elastic IP architecture
Previous by thread: AWS Elastic IP architecture
Next by thread: AWS Elastic IP architecture
Index(es):
- Date
- Thread