RFC 2767: Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6535.
Current document in this lineage: RFC 6535 — Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)
In plain English — editorial summary, not part of the RFC
This memo proposes a mechanism of dual stack hosts using the technique called "Bump-in-the-Stack" in the IP security area. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2767
- Published
- February 2000
- Authors
- K. Tsuchiya; H. Higuchi; Y. Atarashi
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 13
- Also known as
- —
- Obsoleted by:
- RFC 6535
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2767 (2000)
- RFC 3338 (2002)
- RFC 6535 (2012) ✓
Read the full history of Dual-Stack Hosts Using "Bump-in-the-Host" (BIH) →
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 2365Administratively Scoped IP MulticastCurrent
July 1998
- 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
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4305Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
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?