RFC 6317: Basic Socket Interface Extensions for the Host Identity Protocol (HIP)
In plain English — editorial summary, not part of the RFC
This document defines extensions to the current sockets API for the Host Identity Protocol (HIP). The extensions focus on the use of public-key-based identifiers discovered via DNS resolution, but also define interfaces for manual bindings between Host Identity Tags (HITs) and locators. With the extensions, the application can also support more relaxed security models where communication can be non-HIP-based, according to local policies. The extensions in this document are experimental and provide basic tools for further experimentation with policies. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6317
- Published
- July 2011
- Authors
- M. Komu; T. Henderson
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9063Host Identity Protocol ArchitectureCurrent
July 2021
- RFC 6316Sockets Application Program Interface (API) for Multihoming ShimCurrent
July 2011
- RFC 5535Hash-Based Addresses (HBA)Current
June 2009
- RFC 5534Failure Detection and Locator Pair Exploration Protocol for IPv6 MultihomingCurrent
June 2009
- RFC 7343An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers Version 2 (ORCHIDv2)Updated
September 2014
- RFC 9079Source-Specific Routing in the Babel Routing ProtocolCurrent
August 2021
- RFC 9464Internet Key Exchange Protocol Version 2 (IKEv2) Configuration for Encrypted DNSCurrent
November 2023
- RFC 6320Protocol for Access Node Control Mechanism in Broadband NetworksUpdated
October 2011
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?