<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.sriram-opsec-urpf-improvements" target="https://datatracker.ietf.org/doc/html/draft-sriram-opsec-urpf-improvements-03">
   <front>
      <title>Enhanced Feasible-Path Unicast Reverse Path Filtering</title>
      <author initials="K." surname="Sriram" fullname="Kotikalapudi Sriram">
         <organization>USA NIST</organization>
      </author>
      <author initials="D." surname="Montgomery" fullname="Doug Montgomery">
         <organization>USA NIST</organization>
      </author>
      <author initials="J." surname="Haas" fullname="Jeffrey Haas">
         <organization>Juniper Networks</organization>
      </author>
      <date month="March" day="5" year="2018" />
      <abstract>
	 <t>   This document identifies a need for improvement of the unicast
   Reverse Path Filtering techniques (uRPF) [BCP84] for source address
   validation (SAV) [BCP38].  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 [BCP84].  However, as shown in this draft, the existing
   feasible-path uRPF still has short comings.  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&#x27; concerns
   about the possibility of disrupting service for their customers, and
   encourage greater deployment of uRPF techniques.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-sriram-opsec-urpf-improvements-03" />
   
</reference>
