RFC 8704: Enhanced Feasible-Path Unicast Reverse Path Forwarding
In plain English — editorial summary, not part of the RFC
This document identifies a need for and proposes improvement of the unicast Reverse Path Forwarding (uRPF) techniques (see RFC 3704) for detection and mitigation of source address spoofing (see BCP 38). 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 RFC 3704). However, as shown in this document, the existing feasible-path uRPF still has shortcomings. This document describes enhanced feasible-path uRPF (EFP-uRPF) techniques that are more flexible (in a meaningful way) about directionality than the feasible-path uRPF (RFC 3704). The proposed EFP-uRPF methods aim to significantly reduce false positives regarding invalid detection in source address validation (SAV). Hence, they can potentially alleviate ISPs' concerns about the possibility of disrupting service for their customers and encourage greater deployment of uRPF techniques. This document updates RFC 3704.
Document record
- Document ID
- RFC8704
- Published
- February 2020
- Authors
- K. Sriram; D. Montgomery; J. Haas
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 17
- Also known as
- BCP84
- Updates:
- RFC 3704
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8549Export of BGP Community Information in IP Flow Information Export (IPFIX)Current
April 2019
- RFC 9069Support for Local RIB in the BGP Monitoring Protocol (BMP)Updated
February 2022
- RFC 8327Mitigating the Negative Impact of Maintenance through BGP Session CullingCurrent
March 2018
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 8212Default External BGP (EBGP) Route Propagation Behavior without PoliciesCurrent
July 2017
- RFC 8195Use of BGP Large CommunitiesCurrent
June 2017
- RFC 9324Policy Based on the Resource Public Key Infrastructure (RPKI) without Route RefreshCurrent
December 2022
- RFC 7908Problem Definition and Classification of BGP Route LeaksCurrent
June 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?