RFC 5204: Host Identity Protocol (HIP) Rendezvous Extension
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8004.
Current version: RFC 8004 — Host Identity Protocol (HIP) Rendezvous Extension
In plain English — editorial summary, not part of the RFC
This document defines a rendezvous extension for the Host Identity Protocol (HIP). The rendezvous extension extends HIP and the HIP registration extension for initiating communication between HIP nodes via HIP rendezvous servers. Rendezvous servers improve reachability and operation when HIP nodes are multi-homed or mobile. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5204
- Published
- April 2008
- Authors
- J. Laganier; L. Eggert
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 15
- Also known as
- —
- Obsoleted by:
- RFC 8004
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 5203Host Identity Protocol (HIP) Registration ExtensionObsoleted
April 2008
- RFC 5205Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionsObsoleted
April 2008
- RFC 5202Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)Obsoleted
April 2008
- RFC 5206End-Host Mobility and Multihoming with the Host Identity ProtocolObsoleted
April 2008
- RFC 5201Host Identity ProtocolObsoleted
April 2008
- RFC 5213Proxy Mobile IPv6Updated
August 2008
- RFC 5193Protocol for Carrying Authentication for Network Access (PANA) FrameworkCurrent
May 2008
- RFC 5192DHCP Options for Protocol for Carrying Authentication for Network Access (PANA) Authentication AgentsCurrent
May 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?