RFC 4384: BGP Communities for Data Collection
In plain English — editorial summary, not part of the RFC
BGP communities (RFC 1997) are used by service providers for many purposes, including tagging of customer, peer, and geographically originated routes. Such tagging is typically used to control the scope of redistribution of routes within a provider's network and to its peers and customers. With the advent of large-scale BGP data collection (and associated research), it has become clear that the information carried in such communities is essential for a deeper understanding of the global routing system. This memo defines standard (outbound) communities and their encodings for export to BGP route collectors. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC4384
- Published
- February 2006
- Authors
- D. Meyer
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 12
- Also known as
- BCP114
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4451BGP MULTI_EXIT_DISC (MED) ConsiderationsCurrent
March 2006
- RFC 4264BGP WedgiesCurrent
November 2005
- RFC 4098Terminology for Benchmarking BGP Device Convergence in the Control PlaneCurrent
June 2005
- RFC 4486Subcodes for BGP Cease Notification MessageUpdated
April 2006
- RFC 4278Standards Maturity Variance Regarding the TCP MD5 Signature Option (RFC 2385) and the BGP-4 SpecificationCurrent
January 2006
- RFC 4277Experience with the BGP-4 ProtocolCurrent
January 2006
- RFC 4276BGP-4 Implementation ReportCurrent
January 2006
- RFC 4275BGP-4 MIB Implementation SurveyCurrent
January 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?