RFC 6144: Framework for IPv4/IPv6 Translation
In plain English — editorial summary, not part of the RFC
This note describes a framework for IPv4/IPv6 translation. This is in the context of replacing Network Address Translation - Protocol Translation (NAT-PT), which was deprecated by RFC 4966, and to enable networks to have IPv4 and IPv6 coexist in a somewhat rational manner while transitioning to an IPv6 network. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6144
- Published
- April 2011
- Authors
- F. Baker; X. Li; C. Bao; K. Yin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6877464XLAT: Combination of Stateful and Stateless TranslationCurrent
April 2013
- RFC 6145IP/ICMP Translation AlgorithmObsoleted
April 2011
- RFC 6146Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 ServersCurrent
April 2011
- RFC 6147DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 ServersCurrent
April 2011
- RFC 6156Traversal Using Relays around NAT (TURN) Extension for IPv6Obsoleted
April 2011
- RFC 6172Deprecation of the Internet Fibre Channel Protocol (iFCP) Address Translation ModeCurrent
March 2011
- RFC 6173Definitions of Managed Objects for the Internet Fibre Channel Protocol (iFCP)Current
March 2011
- RFC 6181Threat Analysis for TCP Extensions for Multipath Operation with Multiple AddressesCurrent
March 2011
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?