This version incorporates changes based on comments received
at the IETF-97 GROW WG meeting and 
also on the GROW and OPSEC lists back in November 2016.
Please see the next couple of posts from me for the details of the changes made.

Sriram 


-----Original Message-----
From: [email protected] [mailto:[email protected]] 
Sent: Wednesday, May 03, 2017 7:37 PM
To: Sriram, Kotikalapudi (Fed) <[email protected]>; Montgomery, 
Douglas (Fed) <[email protected]>
Subject: New Version Notification for 
draft-sriram-opsec-urpf-improvements-01.txt

A new version of I-D, draft-sriram-opsec-urpf-improvements-01.txt
has been successfully submitted by Kotikalapudi Sriram and posted to the IETF 
repository.

Name:           draft-sriram-opsec-urpf-improvements
Revision:       01
Title:          Enhanced Feasible-Path Unicast Reverse Path Filtering
Document date:  2017-05-03
Group:          Individual Submission
Pages:          11
URL:            
https://www.ietf.org/internet-drafts/draft-sriram-opsec-urpf-improvements-01.txt
Status:         
https://datatracker.ietf.org/doc/draft-sriram-opsec-urpf-improvements/
Htmlized:       
https://tools.ietf.org/html/draft-sriram-opsec-urpf-improvements-01
Htmlized:       
https://datatracker.ietf.org/doc/html/draft-sriram-opsec-urpf-improvements-01
Diff:           
https://www.ietf.org/rfcdiff?url2=draft-sriram-opsec-urpf-improvements-01

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.

                                                                                
  


Please note that it may take a couple of minutes from the time of submission 
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

_______________________________________________
OPSEC mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsec

Reply via email to