RFC 8003: Host Identity Protocol (HIP) Registration Extension
In plain English — editorial summary, not part of the RFC
This document specifies a registration mechanism for the Host Identity Protocol (HIP) that allows hosts to register with services, such as HIP rendezvous servers or middleboxes. This document obsoletes RFC 5203.
Document record
- Document ID
- RFC8003
- Published
- October 2016
- Authors
- J. Laganier; L. Eggert
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 16
- Also known as
- —
- Obsoletes:
- RFC 5203
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8004Host Identity Protocol (HIP) Rendezvous ExtensionCurrent
October 2016
- RFC 8005Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionCurrent
October 2016
- RFC 5205Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionsObsoleted
April 2008
- RFC 5207NAT and Firewall Traversal Issues of Host Identity Protocol (HIP) CommunicationCurrent
April 2008
- RFC 8046Host Mobility with the Host Identity ProtocolCurrent
February 2017
- RFC 8047Host Multihoming with the Host Identity ProtocolCurrent
February 2017
- RFC 7401Host Identity Protocol Version 2 (HIPv2)Updated
April 2015
- RFC 7343An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers Version 2 (ORCHIDv2)Updated
September 2014
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?