<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-sidrops-rov-no-rr" target="https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-rov-no-rr-08">
   <front>
      <title>Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh</title>
      <author initials="R." surname="Bush" fullname="Randy Bush">
         <organization>IIJ Research Lab &amp; Arrcus, Inc.</organization>
      </author>
      <author initials="K." surname="Patel" fullname="Keyur Patel">
         <organization>Arrcus, Inc.</organization>
      </author>
      <author initials="P. F." surname="Smith" fullname="Dr. Philip F. Smith">
         <organization>PFS Internet Development Pty Ltd</organization>
      </author>
      <author initials="M." surname="Tinka" fullname="Mark Tinka">
         <organization>SEACOM</organization>
      </author>
      <date month="September" day="19" year="2022" />
      <abstract>
	 <t>A BGP speaker performing policy based on the Resource Public Key Infrastructure (RPKI) should not issue route refresh to its neighbors because it has received new RPKI data.  This document updates RFC 8481 by describing how to avoid doing so by either keeping a full Adj-RIB-In or saving paths dropped due to ROV (Route Origin Validation) so they may be reevaluated with respect to new RPKI data.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-sidrops-rov-no-rr-08" />
   
</reference>
