%% You should probably cite draft-dunbar-idr-sdwan-port-safi-06 instead of this revision.
@techreport{dunbar-idr-sdwan-port-safi-02,
    number =    {draft-dunbar-idr-sdwan-port-safi-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-dunbar-idr-sdwan-port-safi/02/},
    author =    {Linda Dunbar and Susan Hares},
    title =     {{Subsequent Address Family Indicator for SDWAN Ports}},
    pagetotal = 15,
    year =      ** No value found for 'doc.pub_date.year' **,
    month =     ** No value found for 'doc.pub_date' **,
    day =       ** No value found for 'doc.pub_date.day' **,
    abstract =  {The document specifies a new BGP NLRI and SAFI for advertising properties of a SDWAN edge node WAN ports that face untrusted networks, such as the public internet. Those WAN ports may get assigned IP addresses from the Internet Service Providers (ISPs), may get assigned dynamic IP addresses via DHCP, or may have private addresses (e.g. inside third party Cloud DCs). Packets sent over those SDWAN WAN ports might need to be encrypted (depending on the user policies) or need to go through NAT. SDWAN edge needs to propagate those WAN ports properties to its SDWAN controller, which propagates to the authorized peers and manage the IPsec SAs among those peers for encrypting traffic via the untrusted networks. BGP Route Reflectors (RR) are proposed to propagate this information to the controlled group of other edges in order to allow scaling of the WAN ports property propagation in SDWAN Overlay.},
}