RFC 8955: Dissemination of Flow Specification Rules
In plain English — editorial summary, not part of the RFC
This document defines a Border Gateway Protocol Network Layer Reachability Information (BGP NLRI) encoding format that can be used to distribute (intra-domain and inter-domain) traffic Flow Specifications for IPv4 unicast and IPv4 BGP/MPLS VPN services. This allows the routing system to propagate information regarding more specific components of the traffic aggregate defined by an IP destination prefix. It also specifies BGP Extended Community encoding formats, which can be used to propagate Traffic Filtering Actions along with the Flow Specification NLRI. Those Traffic Filtering Actions encode actions a routing system can take if the packet matches the Flow Specification. This document obsoletes both RFC 5575 and RFC 7674.
Document record
- Document ID
- RFC8955
- Published
- December 2020
- Authors
- C. Loibl; S. Hares; R. Raszuk; D. McPherson; M. Bacher
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 36
- Also known as
- —
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 5575 (2009)
- RFC 7674 (2015)
- RFC 8955 (2020)
Read the full history of Dissemination of Flow Specification Rules →
Referenced by
3 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8957Synonymous Flow Label FrameworkCurrent
January 2021
- RFC 8960A YANG Data Model for MPLS BaseCurrent
December 2020
- RFC 8950Advertising IPv4 Network Layer Reachability Information (NLRI) with an IPv6 Next HopCurrent
November 2020
- RFC 8964Deterministic Networking (DetNet) Data Plane: MPLSCurrent
January 2021
- RFC 8965Applicability of the Babel Routing ProtocolCurrent
January 2021
- RFC 8966The Babel Routing ProtocolCurrent
January 2021
- RFC 8944A YANG Data Model for Layer 2 Network TopologiesCurrent
November 2020
- RFC 8967MAC Authentication for the Babel Routing ProtocolUpdated
January 2021
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?