| Number | Files | Title | Authors | Date | More Info | Status |
|---|---|---|---|---|---|---|
| RFC 4787,BCP 127 | Network Address Translation (NAT) Behavioral Requirements for Unicast UDP | F. Audet, Ed., C. Jennings | January 2007 | Updated byRFC 6888,RFC 7857 | Best Current Practice | |
| RFC 6888,BCP 127 | Common Requirements for Carrier-Grade NATs (CGNs) | S. Perreault, Ed., I. Yamagata, S. Miyakawa, A. Nakagawa, H. Ashida | April 2013 | UpdatesRFC 4787 | Best Current Practice | |
| RFC 7857,BCP 127 | Updates to Network Address Translation (NAT) Behavioral Requirements | R. Penno, S. Perreault, M. Boucadair, Ed., S. Sivakumar, K. Naito | April 2016 | UpdatesRFC 4787,RFC 5382,RFC 5508 | Best Current Practice |
This document defines basic terminology for describing differenttypes of Network Address Translation (NAT) behavior when handlingUnicast UDP and also defines a set of requirements that would allowmany applications, such as multimedia communications or onlinegaming, to work consistently. Developing NATs that meet this set ofrequirements will greatly increase the likelihood that theseapplications will function properly. This document specifies an Internet Best Current Practices for theInternet Community, and requests discussion and suggestions forimprovements.
This document defines common requirements for Carrier-Grade NATs(CGNs). It updates RFC 4787.
This document clarifies and updates several requirements of RFCs4787, 5382, and 5508 based on operational and development experience.The focus of this document is Network Address Translation from IPv4to IPv4 (NAT44).
This document updates RFCs 4787, 5382, and 5508.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.