RFC 5575: Dissemination of Flow Specification Rules
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8955.
Current document in this lineage: RFC 8955 — Dissemination of Flow Specification Rules
In plain English — editorial summary, not part of the RFC
This document defines a new Border Gateway Protocol Network Layer Reachability Information (BGP NLRI) encoding format that can be used to distribute traffic flow specifications. This allows the routing system to propagate information regarding more specific components of the traffic aggregate defined by an IP destination prefix. Additionally, it defines two applications of that encoding format: one that can be used to automate inter-domain coordination of traffic filtering, such as what is required in order to mitigate (distributed) denial-of-service attacks, and a second application to provide traffic filtering in the context of a BGP/MPLS VPN service. The information is carried via the BGP, thereby reusing protocol algorithms, operational experience, and administrative processes such as inter-provider peering agreements. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5575
- Published
- August 2009
- Authors
- P. Marques; N. Sheth; R. Raszuk; B. Greene; J. Mauch; D. McPherson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
Topics
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
2 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 9288Recommendations on the Filtering of IPv6 Packets Containing IPv6 Extension Headers at Transit RoutersCurrent
August 2022
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 7705Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH AttributeCurrent
November 2015
- RFC 8538Notification Message Support for BGP Graceful RestartCurrent
March 2019
- RFC 2545Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain RoutingCurrent
March 1999
- RFC 9072Extended Optional Parameters Length for BGP OPEN MessageCurrent
July 2021
- RFC 6092Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet ServiceCurrent
January 2011
- RFC 6192Protecting the Router Control PlaneCurrent
March 2011
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?