{"draft":"draft-ietf-sidrops-roa-considerations-08","doc_id":"RFC9455","title":"Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes","authors":["Z. Yan","R. Bush","G. Geng","T. de Kock","J. Yao"],"format":["HTML","TEXT","PDF","XML"],"page_count":"6","pub_status":"BEST CURRENT PRACTICE","status":"BEST CURRENT PRACTICE","source":"SIDR Operations","abstract":"When using the Resource Public Key Infrastructure (RPKI), address\r\nspace holders need to issue Route Origin Authorization (ROA)\r\nobject(s) to authorize one or more Autonomous Systems (ASes) to\r\noriginate BGP routes to IP address prefix(es). This memo discusses\r\noperational problems that may arise from ROAs containing multiple IP\r\nprefixes and recommends that each ROA contain a single IP prefix.","pub_date":"August 2023","keywords":["ROA","Route Origin Authorization"],"obsoletes":[],"obsoleted_by":[],"updates":[],"updated_by":[],"see_also":["BCP0238"],"doi":"10.17487\/RFC9455","errata_url":null}