The IESG has received a request from the SIDR Operations WG (sidrops) to consider the following document: - 'Avoidance of ROA Containing Multiple IP Prefixes' <draft-ietf-sidrops-roa-considerations-08.txt> as Best Current Practice
Note that this is the second IETF LC for this document - this first one went through as Informational, but the (strong) feedback from the IESG Eval was that it read much more like a BCP. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the [email protected] mailing lists by 2023-05-10. Exceptionally, comments may be sent to [email protected] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract When using the Resource Public Key Infrastructure (RPKI), address space holders need to issue Route Origin Authorization (ROA) object(s) to authorize one or more Autonomous Systems (ASes) to originate routes to IP address prefix(es). This memo discusses operational problems which may arise from ROAs containing multiple IP prefixes and recommends that each ROA contains a single IP prefix. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-sidrops-roa-considerations/ No IPR declarations have been submitted directly on this I-D. The document contains these normative downward references. See RFC 3967 for additional information: rfc3779: X.509 Extensions for IP Addresses and AS Identifiers (Proposed Standard - Internet Engineering Task Force (IETF)) rfc6482: A Profile for Route Origin Authorizations (ROAs) (Proposed Standard - Internet Engineering Task Force (IETF)) rfc8211: Adverse Actions by a Certification Authority (CA) or Repository Manager in the Resource Public Key Infrastructure (RPKI) (Informational - Internet Engineering Task Force (IETF)) _______________________________________________ IETF-Announce mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-announce
