RFC 7597: 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…

Read RFC 7597 on the RFC Editor

Outgoing relationships (33 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2473: Generic Packet Tunneling in IPv6 Specification
Normative reference — RFC 5625: DNS Proxy Implementation Guidelines
Informative reference — RFC 4862: IPv6 Stateless Address Autoconfiguration
Informative reference — RFC 2827: Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing
Informative reference — RFC 2663: IP Network Address Translator (NAT) Terminology and Considerations
Informative reference — RFC 4787: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
Informative reference — RFC 3056: Connection of IPv6 Domains via IPv4 Clouds
Informative reference — RFC 3633: IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6
Informative reference — RFC 4213: Basic Transition Mechanisms for IPv6 Hosts and Routers
Informative reference — RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry
Informative reference — RFC 4632: Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan
Informative reference — RFC 6269: Issues with IP Address Sharing
Informative reference — RFC 6333: Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
Informative reference — RFC 5382: NAT Behavioral Requirements for TCP
Informative reference — RFC 6056: Recommendations for Transport-Protocol Port Randomization
Informative reference — RFC 879: The TCP Maximum Segment Size and Related Topics
Informative reference — RFC 4953: Defending TCP Against Spoofing Attacks
Informative reference — RFC 5214: Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
Informative reference — RFC 5969: IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification
Informative reference — RFC 2529: Transmission of IPv6 over IPv4 Domains without Explicit Tunnels
Informative reference — RFC 5961: Improving TCP's Robustness to Blind In-Window Attacks
Informative reference — RFC 6346: The Address plus Port (A+P) Approach to the IPv4 Address Shortage
Informative reference — RFC 1858: Security Considerations for IP Fragment Filtering
Informative reference — RFC 4963: IPv4 Reassembly Errors at High Data Rates
Informative reference — RFC 5508: NAT Behavioral Requirements for ICMP
Informative reference — RFC 1933: Transition Mechanisms for IPv6 Hosts and Routers
Informative reference — RFC 4459: MTU and Fragmentation Issues with In-the-Network Tunneling
Informative reference — RFC 3128: Protection Against a Variant of the Tiny Fragment Attack (RFC 1858)
Informative reference — RFC 6324: Routing Loop Attack Using IPv6 Automatic Tunnels: Problem Statement and Proposed Mitigations
Informative reference — RFC 6864: Updated Specification of the IPv4 ID Field
Informative reference — RFC 7598: DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients
Informative reference — RFC 6250: Evolution of the IP Model

Incoming relationships (12 related RFCs)

Normatively referenced by — RFC 7599: Mapping of Address and Port using Translation (MAP-T)
Normatively referenced by — RFC 9313: Pros and Cons of IPv6 Transition Technologies for IPv4-as-a-Service (IPv4aaS)
Normatively referenced by — RFC 7618: Dynamic Allocation of Shared IPv4 Addresses
Normatively referenced by — RFC 9386: IPv6 Deployment Status
Normatively referenced by — RFC 7678: Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional Solutions
Informatively referenced by — RFC 7596: Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture
Informatively referenced by — RFC 7598: DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients
Informatively referenced by — RFC 9099: Operational Security Considerations for IPv6 Networks
Informatively referenced by — RFC 7620: Scenarios with Host Identification Complications
Informatively referenced by — RFC 8114: Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network
Informatively referenced by — RFC 7703: Experience with Testing of Mapping of Address and Port Using Translation (MAP-T)
Informatively referenced by — RFC 8026: Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization Mechanism