RFC 5203: Host Identity Protocol (HIP) Registration Extension
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8003.
Current version: 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 memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5203
- Published
- April 2008
- Authors
- J. Laganier; T. Koponen; L. Eggert
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 13
- Also known as
- —
- Obsoleted by:
- RFC 8003
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3680A Session Initiation Protocol (SIP) Event Package for RegistrationsUpdated
March 2004
- RFC 3608Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During RegistrationUpdated
October 2003
- RFC 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated
December 2002
- RFC 5202Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)Obsoleted
April 2008
- RFC 5204Host Identity Protocol (HIP) Rendezvous ExtensionObsoleted
April 2008
- RFC 5205Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionsObsoleted
April 2008
- RFC 5201Host Identity ProtocolObsoleted
April 2008
- 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?