| CARVIEW |
Select Language
HTTP/2 200
date: Mon, 14 Jul 2025 06:40:44 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95ef07b8f8d8741b-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 7857 » RFC Editor
Search RFCs
- File formats:
- Status:
- BEST CURRENT PRACTICE
- Updates:
- RFC 4787, RFC 5382, RFC 5508
- Authors:
- R. Penno
S. Perreault
M. Boucadair, Ed.
S. Sivakumar
K. Naito - Stream:
- IETF
- Source:
- tsvwg (wit)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7857
Discuss this RFC: Send questions or comments to the mailing list tsvwg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7857
Abstract
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 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us