%% You should probably cite draft-ietf-bess-secure-evpn instead of this I-D.
@techreport{sajassi-bess-secure-evpn-06,
    number =    {draft-sajassi-bess-secure-evpn-06},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-sajassi-bess-secure-evpn/06/},
    author =    {Ali Sajassi and Ayan Banerjee and Samir Thoria and David Carrel and Brian Weis and John Drake},
    title =     {{Secure EVPN}},
    pagetotal = 37,
    year =      2023,
    month =     mar,
    day =       13,
    abstract =  {The applications of EVPN-based solutions ({[}RFC7432{]} and {[}RFC8365{]}) have become pervasive in Data Center, Service Provider, and Enterprise segments. It is being used for fabric overlays and inter- site connectivity in the Data Center market segment, for Layer-2, Layer-3, and IRB VPN services in the Service Provider market segment, and for fabric overlay and WAN connectivity in Enterprise networks. For Data Center and Enterprise applications, there is a need to provide inter-site and WAN connectivity over public Internet in a secured manner with same level of privacy, integrity, and authentication for tenant's traffic as IPsec tunneling using IKEv2. This document presents a solution where BGP point-to-multipoint signaling is leveraged for key and policy exchange among PE devices to create private pair-wise IPsec Security Associations without IKEv2 point-to-point signaling or any other direct peer-to-peer session establishment messages.},
}