%% You should probably cite draft-dunbar-idr-sdwan-port-safi-06 instead of this revision.
@techreport{dunbar-idr-sdwan-port-safi-05,
    number =    {draft-dunbar-idr-sdwan-port-safi-05},
    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/05/},
    author =    {Linda Dunbar and Susan Hares},
    title =     {{SDWAN WAN Ports Property Advertisement in BGP UPDATE}},
    pagetotal = 15,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {The document specifies information encoded in BGP UPDATE for advertising WAN ports properties of a SDWAN edge node to its controller. SDWAN edge node's WAN ports may face untrusted networks, such as the public internet, 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 forwarded through those SDWAN WAN ports might need to be encrypted (depending on the user policies) or need to go through NAT. SDWAN edge nodes need to propagate those WAN ports properties to its controller which in turn distribute to the peers who are authorized to communicate across different types of underlay networks including the untrusted networks. This document assumes the BGP Route Reflectors (RR) as the controller, i.e. SDWAN edges send the WAN ports properties encoded in BGP UPDATE to the RR which in turns propagate the information to a group of authorized SDWAN edges reachable via overlay networks.},
}