RFC 5202: Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7402.
Current version: RFC 7402 — Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)
In plain English — editorial summary, not part of the RFC
This memo specifies an Encapsulated Security Payload (ESP) based mechanism for transmission of user data packets, to be used with the Host Identity Protocol (HIP). This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5202
- Published
- April 2008
- Authors
- P. Jokela; R. Moskowitz; P. Nikander
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 30
- Also known as
- —
- Obsoleted by:
- RFC 7402
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 5201Host Identity ProtocolObsoleted
April 2008
- RFC 5204Host Identity Protocol (HIP) Rendezvous ExtensionObsoleted
April 2008
- RFC 5205Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionsObsoleted
April 2008
- RFC 5206End-Host Mobility and Multihoming with the Host Identity ProtocolObsoleted
April 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
- RFC 5191Protocol for Carrying Authentication for Network Access (PANA)Updated
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?