%% You should probably cite draft-ietf-idr-flowspec-redirect-ip-16 instead of this revision.
@techreport{ietf-idr-flowspec-redirect-ip-10,
    number =    {draft-ietf-idr-flowspec-redirect-ip-10},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-idr-flowspec-redirect-ip/10/},
    author =    {Jeff Haas and Wim Henderickx and Adam Simpson},
    title =     {{BGP Flow-Spec Redirect-to-IP Action}},
    pagetotal = 17,
    year =      2026,
    month =     apr,
    day =       28,
    abstract =  {Flow-spec is an extension to BGP that allows for the dissemination of traffic flow specification rules. This has many possible applications, but the primary one for many network operators is the distribution of traffic filtering actions for distributed denial of service (DDoS) mitigation. The flow-spec standard, RFC 8955, defines a redirect-to-VRF action for policy-based forwarding. This mechanism can be difficult to use, particularly in networks without L3 VPN infrastructure. This document defines a new redirect-to-IP flow-spec action that provides a simpler method of policy-based forwarding. The details of the action, including the IPv4 or IPv6 target address, are encoded in newly defined BGP extended communities.},
}