BGP Flowspec Explicit Term Ordering
draft-haas-idr-flowspec-term-order-00

Document Type Expired Internet-Draft (individual)
Authors Jeffrey Haas  , Susan Hares  , Sven Maduschke 
Last updated 2021-11-08 (latest revision 2021-04-27)
Stream (None)
Formats
Expired & archived
pdf htmlized bibtex
Additional Resources
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-haas-idr-flowspec-term-order-00.txt

Abstract

BGP Flowspec (RFC 8955) provides a mechanism for matching traffic flows. The ordering of the Flow Specifications defined by that RFC is provided by a sorting function that uses the contents of the received BGP NLRI; that NLRI does not contain an explicit ordering component. The RFC's sorting function permits for origination of Flowspec NLRI from multiple BGP Speakers and is generally appropriate for mitigating distributed denial-of-service (DDoS) attacks. There are circumstances where the implicit RFC 8955 sorting order is not appropriate. This document defines a mechanism that permits individual Flowspec NLRI to influence their sort order.

Authors

Jeffrey Haas (jhaas@juniper.net)
Susan Hares (shares@ndzh.com)
Sven Maduschke (sven.maduschke@de.verizon.com)

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