Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)
draft-jokela-hip-rfc5202-bis-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Petri Jokela , Robert Moskowitz , Jan Melen | ||
| Last updated | 2013-01-16 (Latest revision 2012-07-15) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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).
Authors
Petri Jokela
Robert Moskowitz
Jan Melen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)