Cite this BCP: TXTBCP 127 contains the following RFCs:
|RFC 4787, BCP 127||ASCII, PDF||Network Address Translation (NAT) Behavioral Requirements for Unicast UDP||F. Audet, Ed., C. Jennings||January 2007||Updated by RFC 6888, RFC 7857||Best Current Practice|
|RFC 6888, BCP 127||ASCII, PDF||Common Requirements for Carrier-Grade NATs (CGNs)||S. Perreault, Ed., I. Yamagata, S. Miyakawa, A. Nakagawa, H. Ashida||April 2013||Updates RFC 4787||Best Current Practice|
|RFC 7857, BCP 127||ASCII, PDF||Updates to Network Address Translation (NAT) Behavioral Requirements||R. Penno, S. Perreault, M. Boucadair, Ed., S. Sivakumar, K. Naito||April 2016||Updates RFC 4787, RFC 5382, RFC 5508||Best Current Practice|
Abstract of RFC 4787
This document defines basic terminology for describing different types of Network Address Translation (NAT) behavior when handling Unicast UDP and also defines a set of requirements that would allow many applications, such as multimedia communications or online gaming, to work consistently. Developing NATs that meet this set of requirements will greatly increase the likelihood that these applications will function properly. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Abstract of RFC 6888
This document defines common requirements for Carrier-Grade NATs (CGNs). It updates RFC 4787.
Abstract of RFC 7857
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.