RFC 1933: Transition Mechanisms for IPv6 Hosts and Routers
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2893.
Current document in this lineage: RFC 4213 — Basic Transition Mechanisms for IPv6 Hosts and Routers
In plain English — editorial summary, not part of the RFC
This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1933
- Published
- April 1996
- Authors
- R. Gilligan; E. Nordmark
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 22
- Also known as
- —
- Obsoleted by:
- RFC 2893
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1933 (1996)
- RFC 2893 (2000)
- RFC 4213 (2005) ✓
Read the full history of Basic Transition Mechanisms for IPv6 Hosts and Routers →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4213Basic Transition Mechanisms for IPv6 Hosts and RoutersCurrent
October 2005
- RFC 2365Administratively Scoped IP MulticastCurrent
July 1998
- RFC 2765Stateless IP/ICMP Translation Algorithm (SIIT)Obsoleted
February 2000
- RFC 2766Network Address Translation - Protocol Translation (NAT-PT)Obsoleted
February 2000
- RFC 2767Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)Obsoleted
February 2000
- RFC 3056Connection of IPv6 Domains via IPv4 CloudsCurrent
February 2001
- RFC 3574Transition Scenarios for 3GPP NetworksCurrent
August 2003
- RFC 4942IPv6 Transition/Co-existence Security ConsiderationsCurrent
September 2007
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?