RFC 2766: Network Address Translation - Protocol Translation (NAT-PT)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4966.
Current version: 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 specifies an IPv4-to-IPv6 transition mechanism, in addition to those already specified. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2766
- Published
- February 2000
- Authors
- G. Tsirtsis; P. Srisuresh
- Status
- HISTORIC
- Stream
- IETF
- Area
- ops
- Pages
- 21
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2767Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)Obsoleted
February 2000
- RFC 2365Administratively Scoped IP MulticastCurrent
July 1998
- RFC 3574Transition Scenarios for 3GPP NetworksCurrent
August 2003
- RFC 2406IP Encapsulating Security Payload (ESP)Obsoleted
November 1998
- RFC 2402IP Authentication HeaderObsoleted
November 1998
- RFC 1827IP Encapsulating Security Payload (ESP)Obsoleted
August 1995
- RFC 1826IP Authentication HeaderObsoleted
August 1995
- RFC 4302IP Authentication HeaderCurrent
December 2005
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?