MAP-T in production

Wed Jul 22 21:57:01 UTC 2020

I’m here ;-)

I’m tracking all possible products and deployments of NAT64/DNS64/464XLAT. I’ve done a few of them myself for many customers.

The idea is to bring the relevant RFCs to Internet Standards

We could try to do the same also with MAP-T and others. However, my point right now is that the one with a bigger deployment is 464XLAT (hundreds of millions of subscribers), which exceeds by far what has been done with all the other transitions technologies all together. The funny thing is that 464XLAT is just “informational” :-)

Regards,

Jordi

@jordipalet

El 22/7/20 23:25, "NANOG en nombre de Fred Baker" <nanog-bounces+jordi.palet=consulintel.es at nanog.org en nombre de fredbaker.ietf at gmail.com> escribió:

For the record, we are asking similar questions about 464XLAT in v6ops. If you are deploying it, please advise Jordi Palet Martinez.

For those unfamiliar with them, MAP-T and 464XLAT are each deployment frameworks for IPv4/IPv6 translation, as described in RFCs 4164, 4166, 4167, and 7915.

Sent from my iPad

On Jul 22, 2020, at 2:16 PM, Brian Johnson <brian.johnson at netgeek.us> wrote:

Has anyone implemented a MAP-T solution in production? I am looking for feedback on this as a deployment strategy for an IPv6 only core design. My concern is MAP-T CE stability and overhead on the network. The BR will have to do overloaded NAT anyway to access IPv4 only resources. The idea being that when IPv4 is no longer needed, this will be a quicker “clean-up” project than a dual-stack solution.

I have reviewed Jordan Gotlieb’s presentation from Charter and would love to hear if this is still in use at Charter or if was ever fully implemented and the experiences)

I’d love any real life examples and success/failure stories.

Thanks.

- Brian

**********************************************
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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20200722/d22ae478/attachment.html>