Re: [v6ops] reclassify 464XLAT as standard instead of info

[Alexandre Petrescu <[e-mail]>]

Le 25/09/2017 à 12:19, Mikael Abrahamsson a écrit :
> On Mon, 25 Sep 2017, Alexandre Petrescu wrote:
> 
>> If it can, then use it.
> 
> Some people want to migrate away from IPv4 in their networks.

I aree, should be that direction.

> This has to be done incrementally

I agree - but start with the network, not with the Terminal.

Make first an IPv6-only network.

> and since encap can be done over IPv4 and IPv6 without the customer
> seeing any difference, then this is a good way to do things
> incrementally.

It was tried numerous times before CLAT: 3ffe, sixxs, 6to4, DS-MIPv6,
and others.

> So over time we'll see people migrate from LDPv4 to LDPv6, from GTP 
> over IPv4 to GTP over IPv6, from 6PE to 4PE etc.

During this time you prohibit a number of apps and protocols such as
DHCPv6-PD.

> In the end, IPv4 will be a corner case service tunneled/translated 
> over an IPv6 network for most people. We might be up to 20 years out 
> from this being done universally, but that's the end goal for most 
> people who have actually put serious thought into their long time 
> future. I know people who are already trying to do this because 
> they're growing quickly and they don't have IPv4 addresses to spare,

Tell them to do IPv6-PDP-Type v4v6, and NAT for IPv4, and leave IPv6 alone.

> to waste on infrastructure use, and using RFC1918 addresses has lots 
> of operational downsides.

CLAT has many operational downsides as well, forget it.

Fundamentally the IPv4 NAT issue is the fact that it translates.  But
CLAT also translates - they both have same issue.

Alex

>