Mapping of Address and Port using Translation (MAP-T) (RFC7599)
Original Publication Date: 2015-Jul-01
Included in the Prior Art Database: 2015-Jul-31
Internet Society Requests For Comment (RFCs)
X. Li: AUTHOR [+6]
Experiences from initial service provider IPv6 network deployments, such as [RFC6219], indicate that successful transition to IPv6 can happen while supporting legacy IPv4 users without a full end-to-end dual-IP-stack deployment. However, due to public IPv4 address exhaustion, this requires an IPv6 technology that supports IPv4 users utilizing shared IPv4 addressing, while also allowing the network operator to optimize their operations around IPv6 network practices. The use of double NAT64 translation-based solutions is an optimal way to address these requirements, especially in combination with stateless translation techniques that minimize operational challenges outlined in [Solutions-4v6].
Internet Engineering Task Force (IETF) X. Li Request for Comments: 7599 C. Bao Category: Standards Track Tsinghua University ISSN: 2070-1721 W. Dec, Ed. O. Troan Cisco Systems S. Matsushima SoftBank Telecom T. Murakami IP Infusion July 2015
Mapping of Address and Port using Translation (MAP-T)
This document specifies the solution architecture based on "Mapping of Address and Port" stateless IPv6-IPv4 Network Address Translation (NAT64) for providing shared or non-shared IPv4 address connectivity to and across an IPv6 network.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7599.
Li, et al. Standards Track [Page 1]
RFC 7599 MAP-T July 2015
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions...