RFC 7086: Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)
In plain English — editorial summary, not part of the RFC
This document is the HIP-Based Overlay Networking Environment (HIP BONE) instance specification for the REsource LOcation And Discovery (RELOAD) protocol. The document provides the details needed to build a RELOAD-based overlay that uses HIP.
Document record
- Document ID
- RFC7086
- Published
- January 2014
- Authors
- A. Keranen; G. Camarillo; J. Maenpaa
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7343An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers Version 2 (ORCHIDv2)Updated
September 2014
- RFC 7401Host Identity Protocol Version 2 (HIPv2)Updated
April 2015
- RFC 6316Sockets Application Program Interface (API) for Multihoming ShimCurrent
July 2011
- RFC 8003Host Identity Protocol (HIP) Registration ExtensionCurrent
October 2016
- RFC 8004Host Identity Protocol (HIP) Rendezvous ExtensionCurrent
October 2016
- RFC 8005Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionCurrent
October 2016
- RFC 8046Host Mobility with the Host Identity ProtocolCurrent
February 2017
- RFC 8047Host Multihoming with the Host Identity ProtocolCurrent
February 2017
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?