Skip to main content

Packet Content Filter for BGP FlowSpec
draft-cui-idr-content-filter-flowspec-05

Document Type Replaced Internet-Draft (idr WG)
Expired & archived
Authors Yong Cui , Yujia Gao , Susan Hares
Last updated 2026-10-30 (Latest revision 2026-10-14)
Replaced by draft-ietf-idr-fsv2-content-filter
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd Keyur Patel
Shepherd write-up Show Last changed 2026-10-30
IESG IESG state Replaced by draft-ietf-idr-fsv2-content-filter
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to keyur@arrcus.com

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

The BGP FlowSpec mechanism enables the distribution of traffic filter policies (traffic filters and actions) via BGP, facilitating DDoS traffic filtering. The IP filter components defined for FSv1 and the FSv2 IP Basic Filter Families primarily match fields in the IP and transport-layer headers, which may not adequately address volumetric DDoS attack traffic characterized by fixed patterns within the packet content. This document defines a Packet Content Filter Component for FSv1 and FSv2. The match is encoded using OType, Offset, Content Length, Content, and Mask fields in the FlowSpec NLRI. The FSv1 encoding additionally carries a PType field. This new component aims to leverage network devices such as routers and switches to support controlled traffic handling, traffic optimization, and mitigation of simple volumetric DDoS attacks, reducing the overall processing cost of carrier networks.

Authors

Yong Cui
Yujia Gao
Susan Hares

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)