<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-wide-bgp-communities" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-wide-bgp-communities-11">
   <front>
      <title>BGP Community Container Attribute</title>
      <author initials="R." surname="Raszuk" fullname="Robert Raszuk">
         <organization>Arrcus</organization>
      </author>
      <author initials="J." surname="Haas" fullname="Jeffrey Haas">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="A." surname="Lange" fullname="Andrew Lange">
         <organization>Nokia</organization>
      </author>
      <author initials="B." surname="Decraene" fullname="Bruno Decraene">
         <organization>Orange</organization>
      </author>
      <author initials="S." surname="Amante" fullname="Shane Amante">
         <organization>Apple, Inc.</organization>
      </author>
      <author initials="P." surname="Jakma" fullname="Paul Jakma">
         <organization>Huawei Ireland Research Centre</organization>
      </author>
      <date month="March" day="9" year="2023" />
      <abstract>
	 <t>   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&#x27;s
   most important addition is the ability to specify and advertise an
   operator&#x27;s parameters for execution.  It also provides an extensible
   platform for any future community encoding requirements.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-wide-bgp-communities-11" />
   
</reference>
