Local Network Protection for IPv6
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 36
- Abstract
- Although there are many perceived benefits to Network Address Translation (NAT), its primary benefit of "amplifying" available address space is not needed in IPv6. In addition to NAT's many serious disadvantages, there is a perception that other benefits exist, such as a variety of management and security attributes that could be useful for an Internet Protocol site. IPv6 was designed with the intention of making NAT unnecessary, and this document shows how Local Network Protection (LNP) using IPv6 can provide the same or more benefits without the need for address translation. This memo provides information for the Internet community.
- Publication Date
- 2007-05-01
- Status Note
- Informational
- DOI
10.17487/RFC4864- Link
- https://doi.org/10.17487/RFC4864
- Author(s)
- Gunter Van de VeldeTony L. HainRalph DromsBrian E. CarpenterEric Klein
- Keyword(s)
- IPv6, NAT
Latest version of IETF RFC 4864
Document Versions — IETF RFC 4864
-
▶ IETF RFC 4864 (2007-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- Rosenberg, J., "Interactive Connectivity Establishment (ICE): A Methodology for Network Address Translator (NAT) Traversal for Offer/Answer Protocols", Work in Progress, October 2006. EXTERNAL
- Huston, G., "Architectural Commentary on Site Multi-homing using a Level 3 Shim", Work in Progress, July 2005. EXTERNAL
- Chown, T., "IPv6 Implications for TCP/UDP Port Scanning" , Work in Progress, October 2005. EXTERNAL
- Chown, T., Tompson, M., Ford, A., and S. Venaas, "Things to think about when Renumbering an IPv6 network", Work in Progress, September 2006. EXTERNAL
- "Universal Plug and Play Web Site", July 2005, < http://www.upnp.org/ >. EXTERNAL
- IETF RFC 1918 [Active*]
- IETF RFC 2461 [Superseded*]
- IETF RFC 2663 [Active*]
- IETF RFC 2993 [Active*]
- IETF RFC 3022 [Active*]
- IETF RFC 3027 [Active*]
- IETF RFC 3041 [Superseded*]
- IETF RFC 3177 [Superseded*]
- IETF RFC 3314 [Active*]
- IETF RFC 3315 [Superseded*]
- IETF RFC 3484 [Superseded*]
- IETF RFC 3633 [Superseded*]
- IETF RFC 3948 [Active*]
- IETF RFC 3956 [Active*]
- IETF RFC 3971 [Active*]
- IETF RFC 4192 [Active*]
- IETF RFC 4193 [Active*]
- IETF RFC 4632 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4864.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4864, Local Network Protection for IPv6. Available at https://doi.org/10.17487/RFC4864
Snippet:
IETF RFC 4864, Local Network Protection for IPv6. Available at https://doi.org/10.17487/RFC4864
HTML (ISO 690 compliant)
Preview:
IETF RFC 4864, Local Network Protection for IPv6. Available at https://doi.org/10.17487/RFC4864
Snippet:
<span class="citation"><cite>IETF RFC 4864</cite>, Local Network Protection for IPv6. Available at <a href="https://doi.org/10.17487/RFC4864" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4864</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4864, Local Network Protection for IPv6
doi: 10.17487/RFC4864
url: https://doi.org/10.17487/RFC4864
doi: 10.17487/RFC4864
url: https://doi.org/10.17487/RFC4864
Snippet:
<li> <cite id="bib-rfc4864">IETF RFC 4864</cite>, Local Network Protection for IPv6 <span class="doi">10.17487/RFC4864</span> </li>
Referenced By
- IETF RFC 4942 [Active*]
- IETF RFC 5218 [Active*]
- IETF RFC 5220 [Active*]
- IETF RFC 5902 [Active*]
- IETF RFC 5920 [Active*]
- IETF RFC 6036 [Superseded*]
- IETF RFC 6092 [Active*]
- IETF RFC 6144 [Active*]
- IETF RFC 6204 [Superseded*]
- IETF RFC 6264 [Active*]
- IETF RFC 6296 [Active*]
- IETF RFC 7368 [Active*]