%% You should probably cite draft-ietf-idr-wide-bgp-communities-11 instead of this revision.
@techreport{ietf-idr-wide-bgp-communities-08,
    number =    {draft-ietf-idr-wide-bgp-communities-08},
    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/08/},
    author =    {Robert Raszuk and Jeffrey Haas and Andrew Lange and Bruno Decraene and Shane Amante and Paul Jakma},
    title =     {{BGP Community Container Attribute}},
    pagetotal = 24,
    year =      2022,
    month =     jul,
    day =       11,
    abstract =  {Route tagging plays an important role in external BGP relations, communicating various routing policies between peers. It is also a very common best practice for operators to propagate various additional route information between internal peers. The most common tool used today to attach various information about routes is through the use of BGP communities. This document defines a new encoding which will enhance and simplify what can be accomplished today with the use of BGP communities. The most important addition this specification makes over currently defined BGP communities 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.},
}