RFC 6145: IP/ICMP Translation Algorithm
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7915.
Current document in this lineage: RFC 7915 — IP/ICMP Translation Algorithm
In plain English — editorial summary, not part of the RFC
This document describes the Stateless IP/ICMP Translation Algorithm (SIIT), which translates between IPv4 and IPv6 packet headers (including ICMP headers). This document obsoletes RFC 2765. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6145
- Published
- April 2011
- Authors
- X. Li; C. Bao; F. Baker
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 33
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2765 (2000)
- RFC 6145 (2011)
- RFC 7915 (2016) ✓
Referenced by
3 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 4835Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
April 2007
- RFC 4305Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 2767Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)Obsoleted
February 2000
- RFC 2406IP Encapsulating Security Payload (ESP)Obsoleted
November 1998
- RFC 2402IP Authentication HeaderObsoleted
November 1998
- RFC 2365Administratively Scoped IP MulticastCurrent
July 1998
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?