Mapping of Address and Port with Encapsulation (MAP-E) (RFC7597)
Original Publication Date: 2015-Jul-01
Included in the Prior Art Database: 2015-Jul-31
Internet Society Requests For Comment (RFCs)
O. Troan: AUTHOR [+9]
Mapping of IPv4 addresses in IPv6 addresses has been described in numerous mechanisms dating back to the mid-1990s [RFC1933] [RFC4213]. The "automatic tunneling" mechanism as first described in [RFC1933] assigned a globally unique IPv6 address to a host by combining the host's IPv4 address with a well-known IPv6 prefix. Given an IPv6 packet with a destination address with an embedded IPv4 address, a node could automatically tunnel this packet by extracting the IPv4 tunnel endpoint address from the IPv6 destination address.
Internet Engineering Task Force (IETF) O. Troan, Ed. Request for Comments: 7597 W. Dec Category: Standards Track Cisco Systems ISSN: 2070-1721 X. Li C. Bao Tsinghua University S. Matsushima SoftBank Telecom T. Murakami IP Infusion T. Taylor, Ed. Huawei Technologies July 2015
Mapping of Address and Port with Encapsulation (MAP-E)
This document describes a mechanism for transporting IPv4 packets across an IPv6 network using IP encapsulation. It also describes a generic mechanism for mapping between IPv6 addresses and IPv4 addresses as well as transport-layer ports.
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/rfc7597.
Troan, et al. Standards Track [Page 1]
RFC 7597 MAP-E 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...