This document defines a new 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
traffic filtering in the context of a BGP/MPLS VPN service.
The information is carried via the Border Gateway Protocol (BGP),
thereby reusing protocol algorithms, operational experience and
administrative processes such as inter-provider peering agreements.
Working Group Summary
Consensus on the technology was not an issue. There was an IPR
disclosure that occurred after WG LC.
There are multiple, interoperable implementations. There were no LC
comments during WG LC although the technology and draft have been known,
discussed and available for many years.
Yakov Rekhter is the Document Shepherd for this document. Adrian
Farrel is the Area Director.
RFC editor's note
Please kindly change Robert Raszuk's email address to: firstname.lastname@example.org
And his address to:
170 West Tasman Drive
San Jose, CA 95134
Future assignments beyond what is specified in the draft are to be made
using either the Standards Action process defined in [RFC2434], the Early
IANA Allocation process defined in [RFC4020], or the "First Come First
Served" policy defined in [RFC2434].