Skip to main content

BGP Community Container Attribute

Document Type Expired Internet-Draft (idr WG)
Expired & archived
Authors Robert Raszuk , Jeffrey Haas , Andrew Lange, Bruno Decraene , Shane Amante , Paul Jakma
Last updated 2023-11-06 (Latest revision 2023-03-09)
Replaces draft-raszuk-wide-bgp-communities
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd Keyur Patel
Shepherd write-up Show Last changed 2022-04-30
IESG IESG state Expired (IESG: Dead)
Consensus boilerplate Yes
Telechat date (None)
Responsible AD Andrew Alston
Send notices to,,

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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.


Robert Raszuk
Jeffrey Haas
Andrew Lange
Bruno Decraene
Shane Amante
Paul Jakma

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)