Re: [Sidrops] New Version Notification for draft-sriram-sidrops-drop-invalid-policy-00.txt

["Borchert, Oliver (Fed)" <[e-mail]>]

I believe, the end goal in mind should be "drop invalid". 
Said that, I also don’t believe we are there yet. In my opinion, during the deployment
stage, DISR allows a safe “drop invalid” as long as it is still routable. 

And yes, DISR clearly does poke holes into the draconian “drop invalid policy”. I also 
believe that address owners should have to capability to specify their address space as a 
“DISR free zone”. 

For this I look at AS-0 in a somewhat more simplistic way:

What if regarding to DISR, AS 0 is defined the following way:
- “Any prefix with the validation state ‘invalid’ and covered by an AS-0 ROA 
    must be dropped or ignored!”

And if DISR gets extended by:
- “Drop or ignore routes with validation state ‘invalid’ if still routable and 
    NOT covered by an AS 0 ROA!”

Another simpler definition for both above in one could be:
- “DISR will not be employed for address space covered by an AS-0 ROA”

In the later one, an AS-0 ROA disables DISR for the specific address space and if DISR is not
deployed at all, AS-0 ROA ROV just does the same as it already does today!

This is simple, to the point and not really difficult to implement. 

Thanks,
Oliver