%% You should probably cite rfc9061 instead of this I-D.
@techreport{ietf-i2nsf-sdn-ipsec-flow-protection-13,
    number =    {draft-ietf-i2nsf-sdn-ipsec-flow-protection-13},
    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-i2nsf-sdn-ipsec-flow-protection/13/},
    author =    {Rafael Marin-Lopez and Gabriel Lopez-Millan and Fernando Pereniguez-Garcia},
    title =     {{Software-Defined Networking (SDN)-based IPsec Flow Protection}},
    pagetotal = 95,
    year =      2021,
    month =     feb,
    day =       19,
    abstract =  {This document describes how to provide IPsec-based flow protection (integrity and confidentiality) by means of an Interface to Network Security Function (I2NSF) controller. It considers two main well- known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to- host. The service described in this document allows the configuration and monitoring of IPsec Security Associations (IPsec SAs) from a I2NSF Controller to one or several flow-based Network Security Functions (NSFs) that rely on IPsec to protect data traffic. The document focuses on the I2NSF NSF-facing Interface by providing YANG data models for configuring the IPsec databases, namely Security Policy Database (SPD), Security Association Database (SAD), Peer Authorization Database (PAD), and IKEv2. This allows IPsec SA establishment with minimal intervention by the network administrator. It defines three YANG modules but it does not define any new protocol.},
}