RFC 5902: IAB Thoughts on IPv6 Network Address Translation
In plain English — editorial summary, not part of the RFC
There has been much recent discussion on the topic of whether the IETF should develop standards for IPv6 Network Address Translators (NATs). This document articulates the architectural issues raised by IPv6 NATs, the pros and cons of having IPv6 NATs, and provides the IAB's thoughts on the current open issues and the solution space. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5902
- Published
- July 2010
- Authors
- D. Thaler; L. Zhang; G. Lebovitz
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6081Teredo ExtensionsCurrent
January 2011
- RFC 6535Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)Current
February 2012
- RFC 6619Scalable Operation of Address Translators with Per-Interface BindingsCurrent
June 2012
- RFC 4864Local Network Protection for IPv6Current
May 2007
- RFC 7021Assessing the Impact of Carrier-Grade NAT on Network ApplicationsCurrent
September 2013
- RFC 7785Recommendations for Prefix Binding in the Context of Softwire Dual-Stack LiteCurrent
February 2016
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?