<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-sidrops-roa-considerations" target="https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-roa-considerations-07">
   <front>
      <title>Avoidance for ROA Containing Multiple IP Prefixes</title>
      <author initials="Z." surname="Yan" fullname="Zhiwei Yan">
         <organization>CNNIC</organization>
      </author>
      <author initials="R." surname="Bush" fullname="Randy Bush">
         <organization>IIJ Research Lab &amp; Arrcus, Inc.</organization>
      </author>
      <author initials="G." surname="Geng" fullname="Guanggang Geng">
         <organization>Jinan University</organization>
      </author>
      <author initials="T." surname="de Kock" fullname="Ties de Kock">
         <organization>RIPE NCC</organization>
      </author>
      <author initials="J." surname="Yao" fullname="Jiankang Yao">
         <organization>CNNIC</organization>
      </author>
      <date month="February" day="9" year="2023" />
      <abstract>
	 <t>   When using the RPKI, address space holders need to issue ROA
   object(s) to authorize one or more ASes to originate routes to IP
   prefix(es).  This memo discusses operational problems which may arise
   from ROAs containing multiple IP prefixes and recommends that each
   ROA contain a single IP prefix.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-sidrops-roa-considerations-07" />
   
</reference>
