Re: [OPSEC] Reminder: Call for WG adoption of draft-sriram-opsec-urpf-improvements

> On Apr 18, 2018, at 8:20 AM, Sriram, Kotikalapudi (Fed) > wrote: >> Let me mention that I think the WG should also consider potential use of >> RPKI as a complementary mechanism to improve uRPF. Namely, if there is an >> ROA for the prefix-origin pair, it should

Re: [OPSEC] Reminder: Call for WG adoption of draft-sriram-opsec-urpf-improvements

Amir, >I support the adoption of "draft-sriram-opsec-urpf-improvements" as an >OPSEC Working Group document. Thank you. > >Let me mention that I think the WG should also consider potential use of >RPKI as a complementary mechanism to improve uRPF. Namely, if there is an >ROA for the

Re: [OPSEC] Reminder: Call for WG adoption of draft-sriram-opsec-urpf-improvements

Hi, On Wed, Apr 18, 2018 at 08:21:48AM +1200, Barry Greene wrote: > Then you have this statement "It is well known that this method has > limitations when networks are multi-homed and there is asymmetric routing of > packets.??? That is false. BCP84 is wrong. uRPF has been deployed with >

Re: [OPSEC] Reminder: Call for WG adoption of draft-sriram-opsec-urpf-improvements

> On Apr 18, 2018, at 7:50 AM, Jeff Haas wrote: > > It should be noted that my contribution isn't intended to say "Juniper can > support this out the door". Rather, the intent is to start discussion of the > framework that addresses the problem space in a way that's more

Re: [OPSEC] Reminder: Call for WG adoption of draft-sriram-opsec-urpf-improvements

Barry, On Apr 17, 2018, at 3:21 PM, Barry Raveendran Greene > wrote: On Apr 18, 2018, at 01:48, Ron Bonica > wrote: Any comments, positive, negative or indifferent would be appreciated. It is difficult

Re: [OPSEC] Reminder: Call for WG adoption of draft-sriram-opsec-urpf-improvements

> On Apr 18, 2018, at 01:48, Ron Bonica wrote: > > Any comments, positive, negative or indifferent would be appreciated. It is > difficult to judge consensus in the face of silence. Since you asked. Feasible path was build around the capabilities of Juniper’s FIB

Re: [OPSEC] Reminder: Call for WG adoption of draft-sriram-opsec-urpf-improvements

Behalf Of Eric Vyncke (evyncke) Sent: Monday, April 16, 2018 8:03 PM To: opsec@ietf.org Cc: draft-sriram-opsec-urpf-improveme...@ietf.org Subject: [OPSEC] Reminder: Call for WG adoption of draft-sriram-opsec-urpf-improvements Still two days to state whether you want this I-D adopted by our OPSEC WG

[OPSEC] Reminder: Call for WG adoption of draft-sriram-opsec-urpf-improvements

Still two days to state whether you want this I-D adopted by our OPSEC WG -éric & -ron From: OPSEC on behalf of Eric Vyncke Date: Wednesday 4 April 2018 at 12:15 To: "opsec@ietf.org" Cc: