%% You should probably cite draft-ietf-ipsecme-eesp-03 instead of this revision.
@techreport{ietf-ipsecme-eesp-02,
    number =    {draft-ietf-ipsecme-eesp-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-ipsecme-eesp/02/},
    author =    {Steffen Klassert and Antony Antony and Christian Hopps},
    title =     {{Enhanced Encapsulating Security Payload (EESP)}},
    pagetotal = 44,
    year =      ,
    month =     ,
    day =       ,
    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 and QoS support based on the inner traffic flow), 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 and a crypt-offset to allow for exposing inner flow information for middlebox use.},
}