%% You should probably cite rfc8704 instead of this I-D.
@techreport{ietf-opsec-urpf-improvements-03,
    number =    {draft-ietf-opsec-urpf-improvements-03},
    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-opsec-urpf-improvements/03/},
    author =    {Kotikalapudi Sriram and Doug Montgomery and Jeffrey Haas},
    title =     {{Enhanced Feasible-Path Unicast Reverse Path Filtering}},
    pagetotal = 18,
    year =      2019,
    month =     jul,
    day =       8,
    abstract =  {This document identifies a need for improvement of the unicast Reverse Path Filtering techniques (uRPF) (see BCP 84) for detection and mitigation of source address spoofing (see BCP 38). The strict uRPF is inflexible about directionality, the loose uRPF is oblivious to directionality, and the current feasible-path uRPF attempts to strike a balance between the two (see BCP 84). However, as shown in this draft, the existing feasible-path uRPF still has shortcomings. This document describes an enhanced feasible-path uRPF technique, which aims to be more flexible (in a meaningful way) about directionality than the feasible-path uRPF. It can potentially alleviate ISPs' concerns about the possibility of disrupting service for their customers, and encourage greater deployment of uRPF techniques.},
}