nanog mailing list archives

Re: MAP-T in production


From: Fred Baker <fredbaker.ietf () gmail com>
Date: Wed, 22 Jul 2020 14:24:28 -0700

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 () 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

Current thread: