RFC 6316: Sockets Application Program Interface (API) for Multihoming Shim
In plain English — editorial summary, not part of the RFC
This document specifies sockets API extensions for the multihoming shim layer. The API aims to enable interactions between applications and the multihoming shim layer for advanced locator management, and access to information about failure detection and path exploration. This document is based on an assumption that a multihomed host is equipped with a conceptual sub-layer (hereafter called "shim sub- layer") inside the IP layer that maintains mappings between identifiers and locators. Examples of the shim are Shim6 and the Host Identity Protocol (HIP). This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6316
- Published
- July 2011
- Authors
- M. Komu; M. Bagnulo; K. Slavov; S. Sugimoto
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 44
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6317Basic Socket Interface Extensions for the Host Identity Protocol (HIP)Current
July 2011
- RFC 7086Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)Current
January 2014
- RFC 5535Hash-Based Addresses (HBA)Current
June 2009
- RFC 5534Failure Detection and Locator Pair Exploration Protocol for IPv6 MultihomingCurrent
June 2009
- RFC 5338Using the Host Identity Protocol with Legacy ApplicationsCurrent
September 2008
- 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 5206End-Host Mobility and Multihoming with the Host Identity ProtocolObsoleted
April 2008
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?