%% You should probably cite draft-ietf-opsec-urpf-improvements instead of this I-D.
@techreport{sriram-opsec-urpf-improvements-01,
	number =	{draft-sriram-opsec-urpf-improvements-01},
	type =		{Internet-Draft},
	institution =	{Internet Engineering Task Force},
	publisher =	{Internet Engineering Task Force},
	note =		{Work in Progress},
	url =		{https://datatracker.ietf.org/doc/html/draft-sriram-opsec-urpf-improvements-01},
        author =	{Kotikalapudi Sriram and Doug Montgomery},
	title =		{{Enhanced Feasible-Path Unicast Reverse Path Filtering}},
	pagetotal =	11,
	year =		,
	month =		,
	day =		,
	abstract =	{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 proposes an enhanced feasible-path uRPF technique, which aims to be more flexible (in a meaningful way) about directionality than the feasible-path uRPF. It is expected to alleviate ISPs' concerns about the possibility of disrupting service for their customers, and encourage greater deployment of uRPF.},
}