Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 25
Abstract: This document discusses issues with the specific form of IPv6-IPv4 protocol translation mechanism implemented by the Network Address Translator - Protocol Translator (NAT-PT) defined in RFC 2766. These issues are sufficiently serious that recommending RFC 2766 as a general purpose transition mechanism is no longer desirable, and this document recommends that the IETF should reclassify RFC 2766 from Proposed Standard to Historic status. This memo provides information for the Internet community.
Publication Date: 2007-07-01
Status Note: Informational
DOI: 10.17487/RFC4966
Link: https://doi.org/10.17487/RFC4966
Author(s): Cedric Aoun
Elwyn B. Davies
Keyword(s): NAT-PT, V6OPS

Latest version of IETF RFC 4966

Document Versions — IETF RFC 4966

▶ IETF RFC 4966 (2007-07-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 1035 [Active, Amended*]
IETF RFC 2663 [Active*]
IETF RFC 2765 [Superseded*]
IETF RFC 2766 [Superseded*]
IETF RFC 3027 [Active*]
IETF RFC 3314 [Active*]
IETF RFC 3484 [Superseded*]
IETF RFC 4033 [Active*]
RFC4215 — RFC4215 EXTERNAL
IETF RFC 4294 [Superseded*]

Bibliographic Reference(s)

Okazaki, S. and A. Desai, "NAT-PT Security Considerations", Work in Progress, June 2003. EXTERNAL
Venaas, S., "An IPv4 - IPv6 multicast gateway" , Work in Progress, February 2003. EXTERNAL
Satapati, S., "NAT-PT Applicability" , Work in Progress, October 2003. EXTERNAL
Hallingby, P. and S. Satapati, "NAT-PT DNS ALG solutions", Work in Progress, July 2002. EXTERNAL
Shin, M. and J. Lee, "Considerations for Mobility Support in NAT-PT", Work in Progress, July 2005. EXTERNAL
Malki, K., "IPv6-IPv4 Translation mechanism for SIP-based services in Third Generation Partnership Project (3GPP) Networks", Work in Progress, December 2003. EXTERNAL
Park, S., "Scalable mNAT-PT Solution" , Work in Progress, May 2003. EXTERNAL
Tsuchiya, K., Higuchi, H., Sawada, S., and S. Nozaki, "An IPv6/IPv4 Multicast Translator based on IGMP/MLD Proxying (mtp)", Work in Progress, February 2003. EXTERNAL
Pol, R., Satapati, S., and S. Sivakumar, "Issues when translating between IPv4 and IPv6", Work in Progress, January 2003. EXTERNAL
IETF RFC 1858 [Active*]
IETF RFC 2960 [Superseded*]
IETF RFC 3128 [Active*]
RFC3498 — RFC3498 EXTERNAL

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4966.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 4966, Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status. Available at https://doi.org/10.17487/RFC4966

Snippet:

IETF RFC 4966, Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status. Available at https://doi.org/10.17487/RFC4966

HTML (ISO 690 compliant)

Preview:

IETF RFC 4966, Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status. Available at https://doi.org/10.17487/RFC4966

Snippet:

<span class="citation"><cite>IETF RFC 4966</cite>, Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status. Available at <a href="https://doi.org/10.17487/RFC4966" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4966</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 4966, Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status
doi: 10.17487/RFC4966
url: https://doi.org/10.17487/RFC4966

Snippet:

<li>
<cite id="bib-rfc4966">IETF RFC 4966</cite>, Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status
<span class="doi">10.17487/RFC4966</span>
</li>

Referenced By

IETF RFC 4942 [Active*]
IETF RFC 5971 [Active*]
IETF RFC 6145 [Superseded*]