RFC 7857: Updates to Network Address Translation (NAT) Behavioral Requirements

In plain English — editorial summary, not part of the RFC

This document clarifies and updates several requirements of RFCs 4787, 5382, and 5508 based on operational and development experience. The focus of this document is Network Address Translation from IPv4 to IPv4 (NAT44). This document updates RFCs 4787, 5382, and 5508.

Document record

Document ID

RFC7857

Published

April 2016

Authors

R. Penno; S. Perreault; M. Boucadair; S. Sivakumar; K. Naito

Status

BEST CURRENT PRACTICE

Stream

IETF

Area

wit

Pages

14

Also known as

BCP127

Updates:

RFC 4787, RFC 5382, RFC 5508

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC7857

Topics

• address sharing
• IPv4 service continuity
• Carrier Grade NAT
• CGN
• LSN
• NAT traversal
• RFC4787
• RFC5382
• RFC5508
• DS-Lite
• NAT64
• Address depletion

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent

  March 2017

• RFC 8512A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)Current

  January 2019

• RFC 7648Port Control Protocol (PCP) Proxy FunctionCurrent

  September 2015

• RFC 8115DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 PrefixesCurrent

  March 2017

• RFC 7596Lightweight 4over6: An Extension to the Dual-Stack Lite ArchitectureCurrent

  July 2015

• RFC 7393Using the Port Control Protocol (PCP) to Update Dynamic DNSCurrent

  November 2014

• RFC 8026Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization MechanismCurrent

  November 2016

• RFC 7678Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional SolutionsCurrent

  October 2015

Also filed under

• BEST CURRENT PRACTICE
• 2016
• IETF stream
• wit area
• BCP 127