RFC 6535: Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)
In plain English — editorial summary, not part of the RFC
Bump-in-the-Host (BIH) is a host-based IPv4 to IPv6 protocol translation mechanism that allows a class of IPv4-only applications that work through NATs to communicate with IPv6-only peers. The host on which applications are running may be connected to IPv6-only or dual-stack access networks. BIH hides IPv6 and makes the IPv4-only applications think they are talking with IPv4 peers by local synthesis of IPv4 addresses. This document obsoletes RFC 2767 and RFC 3338. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6535
- Published
- February 2012
- Authors
- B. Huang; H. Deng; T. Savolainen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 25
- 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 2767 (2000)
- RFC 3338 (2002)
- RFC 6535 (2012)
Read the full history of Dual-Stack Hosts Using "Bump-in-the-Host" (BIH) →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6619Scalable Operation of Address Translators with Per-Interface BindingsCurrent
June 2012
- RFC 6081Teredo ExtensionsCurrent
January 2011
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 7984Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP NetworkCurrent
September 2016
- RFC 8305Happy Eyeballs Version 2: Better Connectivity Using ConcurrencyCurrent
December 2017
- RFC 9224Finding the Authoritative Registration Data Access Protocol (RDAP) ServiceCurrent
March 2022
- RFC 6145IP/ICMP Translation AlgorithmObsoleted
April 2011
- RFC 6052IPv6 Addressing of IPv4/IPv6 TranslatorsCurrent
October 2010
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?