<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.sriram-sidrops-drop-invalid-policy" target="https://datatracker.ietf.org/doc/html/draft-sriram-sidrops-drop-invalid-policy-03">
   <front>
      <title>Origin Validation Policy Considerations for Dropping Invalid Routes</title>
      <author initials="K." surname="Sriram" fullname="Kotikalapudi Sriram">
         <organization>USA NIST</organization>
      </author>
      <author initials="O." surname="Borchert" fullname="Oliver Borchert">
         <organization>USA NIST</organization>
      </author>
      <author initials="D." surname="Montgomery" fullname="Doug Montgomery">
         <organization>USA NIST</organization>
      </author>
      <date month="April" day="22" year="2019" />
      <abstract>
	 <t>   Deployment of Resource Public Key Infrastructure (RPKI) and Route
   Origin Authorizations (ROAs) is expected to occur gradually over
   several or many years.  During the incremental deployment period,
   network operators would wish to have a meaningful policy for dropping
   Invalid routes.  Their goal is to balance (A) dropping Invalid routes
   so hijacked routes can be eliminated, versus (B) tolerance for
   missing or erroneously created ROAs for customer prefixes.  This
   document considers a Drop Invalid if Still Routable (DISR) policy
   that is based on these considerations.  The key principle of DISR
   policy is that an Invalid route can be dropped if a Valid or NotFound
   route exists for a subsuming less specific prefix.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-sriram-sidrops-drop-invalid-policy-03" />
   
</reference>
