<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.yan-sidrops-roa-considerations" target="https://datatracker.ietf.org/doc/html/draft-yan-sidrops-roa-considerations-06">
   <front>
      <title>Problem Statement and Considerations for ROAs issued with Multiple Prefixes</title>
      <author initials="Z." surname="Yan" fullname="Zhiwei Yan">
         <organization>CNNIC</organization>
      </author>
      <author initials="R." surname="Bush" fullname="Randy Bush">
         <organization>Internet Initiative Japan</organization>
      </author>
      <author initials="G." surname="Geng" fullname="Guanggang Geng">
         <organization>Jinan University</organization>
      </author>
      <author initials="J." surname="Yao" fullname="Jiankang Yao">
         <organization>CNNIC</organization>
      </author>
      <date month="March" day="25" year="2021" />
      <abstract>
	 <t>   The address space holder needs to issue an ROA object when it
   authorizes one or more ASes to originate routes to multiple prefixes.
   During the process of ROA issuance, the address space holder needs to
   specify an origin AS for a list of IP prefixes.  Besides, the address
   space holder has a free choice to put multiple prefixes into a single
   ROA or issue separate ROAs for each prefix based on the current
   specification.  This memo analyzes and presents some operational
   problems which may be caused by the misconfigurations of ROAs
   containing multiple IP prefixes.  Some suggestions and considerations
   also have been proposed.

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