CurrentINFORMATIONALIETF stream

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

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC4966
Published
July 2007
Authors
C. Aoun; E. Davies
Status
INFORMATIONAL
Stream
IETF
Area
ops
Pages
25
Also known as
Obsoletes:
RFC 2766

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4966-reasons-to-move-the-network-address-translator-protocol-translator-nat-pt-to-his