| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 06:57:41 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=3UyqfebqEfaXlJzpY3Sgd9BAVkT.5ao3eyLQ_hCd.YU-1760165861-1.0.1.1-2YP8qIFm0EbBgZrHvxv78loumgONAQrSKBpQdK2KsDTPyI0TCPovhJ2wHLW48AnL4r71k4iFAj5eLy4RFDR.k_aWdOXvzew2yi_sJSWUvWI; path=/; expires=Sat, 11-Oct-25 07:27:41 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cc76f4097e1712-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 5202 » RFC Editor
Search RFCs
RFC 5202
Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP), April 2008
- File formats:
- Status:
- EXPERIMENTAL
- Obsoleted by:
- RFC 7402
- Authors:
- P. Jokela
R. Moskowitz
P. Nikander - Stream:
- IETF
- Source:
- hip (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5202
Discuss this RFC: Send questions or comments to the mailing list hipsec@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5202
Abstract
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us