Several US companies (including my employes) simply use the same ARIN prefix
everywhere and inject local routes at each WW locations. As long as the prefix
length is short enough, there will be no issue about routing or about RIR.
-éric
On 21/05/18 06:47, "ipv6-ops-bounces+evyncke=cisco@lis
Erik Kline wrote on 21/05/2018 08:13:
Please don't do NAT. You're just moving a ton of pain onto application
developers.
I would very much like to avoid NAT, what I am looking for is a technology or
feature that allows me to avoid NAT. Also because the developers share their
pain withh the
On Mon, 21 May 2018 at 14:59, Mikael Abrahamsson wrote:
> On Mon, 21 May 2018, Luigi Rosa wrote:
> > Hi,
> > one of my customer is a US corporate with offices literally on 5
continents
> > and one datacentre. Offices are connected each other and to the
datacentrevia
> > MPLS, each office accesse
Mikael Abrahamsson wrote on 21/05/2018 07:59:
https://tools.ietf.org/html/draft-ietf-rtgwg-enterprise-pa-multihoming-06 might
be relevant to your requirements.
This is a great starting point, thank you!
For sure I will do 1:1 NAT if I will have do go with NPTv6.
--
Ciao,
luigi
/
+--[Lui
On Mon, 21 May 2018, Luigi Rosa wrote:
Hi,
one of my customer is a US corporate with offices literally on 5 continents
and one datacentre. Offices are connected each other and to the datacentrevia
MPLS, each office accesses the Internet via local ISP.
Since they asked me to start planning fo
Hi,
one of my customer is a US corporate with offices literally on 5 continents and
one datacentre. Offices are connected each other and to the datacentrevia MPLS,
each office accesses the Internet via local ISP.
Since they asked me to start planning for IPv6, my idea was originally to buy a