@techreport{ietf-idr-wide-bgp-communities-11, number = {draft-ietf-idr-wide-bgp-communities-11}, 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-wide-bgp-communities/11/}, author = {Robert Raszuk and Jeffrey Haas and Andrew Lange and Bruno Decraene and Shane Amante and Paul Jakma}, title = {{BGP Community Container Attribute}}, pagetotal = 25, year = 2023, month = mar, day = 9, abstract = {Route tagging plays an important role in external BGP {[}RFC4271{]} relations, in communicating various routing policies between peers. It is also a common best practice among operators to propagate various additional information about routes intra-domain. The most common tool used today to attach various information about routes is through the use of BGP communities {[}RFC1997{]}. This document defines a new encoding that enhances and simplifies what can be accomplished with BGP communities. This specification's most important addition is the ability to specify and advertise an operator's parameters for execution. It also provides an extensible platform for any future community encoding requirements.}, }