UpdatedPROPOSED STANDARDIETF stream

RFC 7401: Host Identity Protocol Version 2 (HIPv2)

Still current, but amended. Parts of this document are changed or extended by RFC 8002, RFC 9374. Read both.

In plain English — editorial summary, not part of the RFC

This document specifies the details of the Host Identity Protocol (HIP). HIP allows consenting hosts to securely establish and maintain shared IP-layer state, allowing separation of the identifier and locator roles of IP addresses, thereby enabling continuity of communications across IP address changes. HIP is based on a Diffie-Hellman key exchange, using public key identifiers from a new Host Identity namespace for mutual peer authentication. The protocol is designed to be resistant to denial-of-service (DoS) and man-in-the-middle (MitM) attacks. When used together with another suitable security protocol, such as the Encapsulating Security Payload (ESP), it provides integrity protection and optional encryption for upper-layer protocols, such as TCP and UDP. This document obsoletes RFC 5201 and addresses the concerns raised by the IESG, particularly that of crypto agility. It also incorporates lessons learned from the implementations of RFC 5201.

Document record

Document ID
RFC7401
Published
April 2015
Authors
R. Moskowitz; T. Heer; P. Jokela; T. Henderson
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
128
Also known as
Obsoletes:
RFC 5201
Updated by:
RFC 8002, RFC 9374

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/7401-host-identity-protocol-version-2-hipv2