%% You should probably cite rfc7402 instead of this I-D.
@techreport{ietf-hip-rfc5202-bis-00,
    number =    {draft-ietf-hip-rfc5202-bis-00},
    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-hip-rfc5202-bis/00/},
    author =    {Petri Jokela and Robert Moskowitz and Pekka Nikander and Jan Melen},
    title =     {{Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)}},
    pagetotal = 37,
    year =      2010,
    month =     sep,
    day =       23,
    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). IESG Note The following issues describe IESG concerns about this document. The IESG expects that these issues will be addressed when future versions of HIP are designed. In case of complex Security Policy Databases (SPDs) and the co- existence of HIP and security-related protocols such as IKE, implementors may encounter conditions that are unspecified in these documents. For example, when the SPD defines an IP address subnet to be protected and a HIP host is residing in that IP address area, there is a possibility that the communication is encrypted multiple times. Readers are advised to pay special attention when running HIP with complex SPD settings. Future specifications should clearly define when multiple encryption is intended, and when it should be avoided.},
}