RFC 8549: Export of BGP Community Information in IP Flow Information Export (IPFIX)
In plain English — editorial summary, not part of the RFC
By introducing new Information Elements (IEs), this document extends the existing BGP-related IEs to enable IP Flow Information Export (IPFIX) to export BGP community information, including the BGP Standard Communities defined in RFC 1997, BGP Extended Communities defined in RFC 4360, and BGP Large Communities defined in RFC 8092. According to the network operator's BGP community planning, network traffic information can then be accumulated and analyzed at the BGP community granularity, which represents the traffic of different kinds of customers, services, or geographical regions. Network traffic information at the BGP community granularity is useful for network traffic analysis and engineering.
Document record
- Document ID
- RFC8549
- Published
- April 2019
- Authors
- Z. Li; R. Gu; J. Dong
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7133Information Elements for Data Link Layer Traffic MeasurementCurrent
May 2014
- RFC 8704Enhanced Feasible-Path Unicast Reverse Path ForwardingCurrent
February 2020
- RFC 8327Mitigating the Negative Impact of Maintenance through BGP Session CullingCurrent
March 2018
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 8212Default External BGP (EBGP) Route Propagation Behavior without PoliciesCurrent
July 2017
- RFC 8195Use of BGP Large CommunitiesCurrent
June 2017
- RFC 9069Support for Local RIB in the BGP Monitoring Protocol (BMP)Updated
February 2022
- RFC 7908Problem Definition and Classification of BGP Route LeaksCurrent
June 2016
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?