nanog mailing list archives

Re: MAP-T (was: Re: V6 still not supported)


From: JORDI PALET MARTINEZ via NANOG <nanog () nanog org>
Date: Fri, 25 Mar 2022 21:53:16 +0100

The cost of deploying MAP in CPEs is a bit higher than 464XLAT, which is not an issue anyway. There are several open 
source implementations for both of them.

It is true that MAP avoids state in the network, however, it means higher "cost" for users in terms of restrictions of 
ports. It also means more IPv4 addresses even if the ports are not used. In some countries, like India, MAP was not 
alllowed by the regulator, because the lack of proper logging, so it was push-back by the bigger provider (probably the 
bigger in the world - Jio) of IPv6.

At the end, if you turn on IPv6 to residential customers, typically you will get 70-80% IPv6 traffic, so the state in 
the NAT64 using 464XLAT is lower and lower every day.

With 464XLAT there is no restriction on the number of ports per subscriber, the usage of IPv4 addresses is more 
efficient, and of course, you can use the same protocol in cellular networks, with also make simpler the support of 
backup links in CPEs (for example GPON in the primary link and 4G in the backup one).

Last but not least, 464XLAT also allows enterprise networks to swich to IPv6-only (with IPv4aaS) providing a smooth 
transition to a final IPv6-only stage.

The fact that in terms of users 464XLAT exceeds all the other transition tehcnologies all together, should mean 
something.

There is a bunch of information at https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-comparison/, which is 
just waiting for the final OK from the IESG to jumpt to the final stage (RFC Editor).

Regads,
Jordi
 
 
Saludos,
Jordi
@jordipalet
 

    -----Original Message-----
    From: NANOG [mailto:nanog-bounces+vasilenko.eduard=huawei.com () nanog org] On Behalf Of Jared Brown
    Sent: Friday, March 25, 2022 4:49 PM
    To: nanog () nanog org
    Subject: MAP-T (was: Re: V6 still not supported)

    Most IPv6 transition mechanisms involve some form of (CG)NAT. After watching a NANOG presentation on MAP-T, I have 
a question regarding this.

    Why isn't MAP-T more prevalent, given that it is (almost) stateless on the provider side?

    Is it CPE support, the headache of moving state to the CPE, vendor support, or something else?


    NANOG 2017
    Mapping of Address and Port using Translation MAP T: Deployment at Charter Communications 
https://www.youtube.com/watch?v=ZmfYHCpfr_w


    - Jared



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be 
for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, 
distribution or use of the contents of this information, even if partially, including attached files, is strictly 
prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any 
disclosure, copying, distribution or use of the contents of this information, even if partially, including attached 
files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to 
inform about this communication and delete it.




Current thread: