Enhanced Encapsulating Security Payload (EESP)
draft-klassert-ipsecme-eesp-02
| Document | Type |
Replaced Internet-Draft
(ipsecme WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Steffen Klassert , Antony Antony , Christian Hopps | ||
| Last updated | 2025-04-25 (Latest revision 2025-02-26) | ||
| Replaced by | draft-ietf-ipsecme-eesp | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ipsecme-eesp | |
| Consensus boilerplate | Unknown | ||
| 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 document describes the Enhanced Encapsulating Security Payload (EESP) protocol, which builds on the existing IP Encapsulating Security Payload (ESP) protocol. It is designed to modernize and overcome limitations in the ESP protocol. EESP adds Session IDs (e.g., to support CPU pinning), changes some previously mandatory fields to optional, and moves the ESP trailer into the EESP header. Additionally, EESP adds header options adapted from IPv6 to allow for future extension. New header options are defined which add Flow IDs (e.g., for CPU pinning and QoS support), and a crypt-offset to allow for exposing inner flow information for middlebox use.
Authors
Steffen Klassert
Antony Antony
Christian Hopps
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)