2016
DOI: 10.17487/rfc7857
|View full text |Cite
|
Sign up to set email alerts
|

Updates to Network Address Translation (NAT) Behavioral Requirements

Abstract: This document clarifies and updates several requirements of RFCs 4787, 5382, and 5508 based on operational and development experience.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2016
2016
2023
2023

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(2 citation statements)
references
References 14 publications
0
2
0
Order By: Relevance
“…We argue that the lack of guidelines and regulations for CGN deployment compounds the situation. While the IETF publishes best practices for general NAT behavior [6,21,33] as well as basic requirements for CGN deployments [34] (which, incidentally, many of our identified CGNs violate), dimensioning NATs at carrier-scale in a way that minimizes collateral damage remains a black art. Our finding that some large ISPs find the need to employ publicly routable (indeed, sometimes routed) address space for internal CGN deployment ( § 6.1) underlines the graveness of the situation.…”
Section: Discussionmentioning
confidence: 99%
“…We argue that the lack of guidelines and regulations for CGN deployment compounds the situation. While the IETF publishes best practices for general NAT behavior [6,21,33] as well as basic requirements for CGN deployments [34] (which, incidentally, many of our identified CGNs violate), dimensioning NATs at carrier-scale in a way that minimizes collateral damage remains a black art. Our finding that some large ISPs find the need to employ publicly routable (indeed, sometimes routed) address space for internal CGN deployment ( § 6.1) underlines the graveness of the situation.…”
Section: Discussionmentioning
confidence: 99%
“…Although these technologies are not the primary scope of this document, the benchmarking methodology associated with singletranslation technologies as defined in Section 4.1 can be employed to benchmark implementations that use NAT44 (as defined by [RFC2663] with the behavior described by [RFC7857]) and implementations that use NAT66 (as defined by [RFC6296]). …”
Section: Nat44 and Nat66mentioning
confidence: 99%