RFC 7597: Mapping of Address and Port with Encapsulation (MAP-E)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7597
- Published
- July 2015
- Authors
- O. Troan; W. Dec; X. Li; C. Bao; S. Matsushima; T. Murakami; T. Taylor
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 35
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7598DHCPv6 Options for Configuration of Softwire Address and Port-Mapped ClientsUpdated
July 2015
- RFC 7596Lightweight 4over6: An Extension to the Dual-Stack Lite ArchitectureCurrent
July 2015
- RFC 7599Mapping of Address and Port using Translation (MAP-T)Current
July 2015
- RFC 7600IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)Current
July 2015
- RFC 7588A Widely Deployed Solution to the Generic Routing Encapsulation (GRE) Fragmentation ProblemCurrent
July 2015
- RFC 7618Dynamic Allocation of Shared IPv4 AddressesCurrent
August 2015
- RFC 7626DNS Privacy ConsiderationsObsoleted
August 2015
- RFC 7629Flow-Binding Support for Mobile IPCurrent
August 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?