%% You should probably cite rfc9012 instead of this I-D. @techreport{ietf-idr-tunnel-encaps-22, number = {draft-ietf-idr-tunnel-encaps-22}, 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-idr-tunnel-encaps/22/}, author = {Keyur Patel and Gunter Van de Velde and Srihari R. Sangli and John Scudder}, title = {{The BGP Tunnel Encapsulation Attribute}}, pagetotal = 41, year = 2021, month = jan, day = 7, abstract = {This document defines a BGP path attribute known as the "Tunnel Encapsulation attribute", which can be used with BGP UPDATEs of various Subsequent Address Family Identifiers (SAFIs) to provide information needed to create tunnels and their corresponding encapsulation headers. It provides encodings for a number of tunnel types, along with procedures for choosing between alternate tunnels and routing packets into tunnels. This document obsoletes RFC 5512, which provided an earlier definition of the Tunnel Encapsulation attribute. RFC 5512 was never deployed in production. Since RFC 5566 relies on RFC 5512, it is likewise obsoleted. This document updates RFC 5640 by indicating that the Load-Balancing Block sub-TLV may be included in any Tunnel Encapsulation attribute where load balancing is desired.}, }