BGP Communities for Data Collection
RFC 4384, “BGP Communities for Data Collection”, is a Best Current Practice document published in February 2006 by D. Meyer. The canonical text is published by the RFC Editor.
Abstract
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.
What “Best Current Practice” means
Documents the IETF community's recommended operational or procedural practice rather than a protocol specification.
The canonical text of RFC 4384 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4383 The Use of Timed Efficient Stream Loss-Tolerant Authentication in the Secure Real-time Transport Protocol
- RFC 4385 Pseudowire Emulation Edge-to-Edge Control Word for Use over an MPLS PSN
- RFC 4382 MPLS/BGP Layer 3 Virtual Private Network Management Information Base
- RFC 4386 Internet X.509 Public Key Infrastructure Repository Locator Service
- RFC 4381 Analysis of the Security of BGP/MPLS IP Virtual Private Networks
- RFC 4387 Internet X.509 Public Key Infrastructure Operational Protocols: Certificate Store Access via HTTP
- RFC 4380 Teredo: Tunneling IPv6 over UDP through Network Address Translations
- RFC 4388 Dynamic Host Configuration Protocol Leasequery