Last Call: <draft-ietf-sidrops-roa-considerations-08.txt> (Avoidance of ROA Containing Multiple IP Prefixes) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Wed, 26 April 2023 13:18 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-sidrops-roa-considerations-08.txt> (Avoidance of ROA Containing Multiple IP Prefixes) to Best Current Practice
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-sidrops-roa-considerations@ietf.org, housley@vigilsec.com, keyur@arrcus.com, sidrops-chairs@ietf.org, sidrops@ietf.org, warren@kumari.net
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <168251510454.53018.1142837347546465701@ietfa.amsl.com>
Date: Wed, 26 Apr 2023 06:18:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/HsLZzfUo_Sl-CQn2ymx2vMRBZNU>

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
last-call@ietf.org mailing lists by 2023-05-10. Exceptionally, comments may
be sent to iesg@ietf.org 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))

Last Call: <draft-ietf-sidrops-roa-considerations… The IESG