RFC 5205: Host Identity Protocol (HIP) Domain Name System (DNS) Extensions
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8005.
Current version: RFC 8005 — Host Identity Protocol (HIP) Domain Name System (DNS) Extension
In plain English — editorial summary, not part of the RFC
This document specifies a new resource record (RR) for the Domain Name System (DNS), and how to use it with the Host Identity Protocol (HIP). This RR allows a HIP node to store in the DNS its Host Identity (HI, the public component of the node public-private key pair), Host Identity Tag (HIT, a truncated hash of its public key), and the Domain Names of its rendezvous servers (RVSs). This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5205
- Published
- April 2008
- Authors
- P. Nikander; J. Laganier
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 17
- Also known as
- —
- Obsoleted by:
- RFC 8005
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 8003Host Identity Protocol (HIP) Registration ExtensionCurrent
October 2016
- RFC 8004Host Identity Protocol (HIP) Rendezvous ExtensionCurrent
October 2016
- RFC 5207NAT and Firewall Traversal Issues of Host Identity Protocol (HIP) CommunicationCurrent
April 2008
- RFC 4509Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)Current
May 2006
- RFC 3658Delegation Signer (DS) Resource Record (RR)Obsoleted
December 2003
- RFC 3646DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
December 2003
- RFC 3597Handling of Unknown DNS Resource Record (RR) TypesUpdated
September 2003
- RFC 3596DNS Extensions to Support IP Version 6Current
October 2003
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?