A new Request for Comments is now available in online RFC libraries.

        BCP 238        
        RFC 9455

        Title:      Avoiding Route Origin Authorizations (ROAs) 
                    Containing Multiple IP Prefixes 
        Author:     Z. Yan,
                    R. Bush,
                    G. Geng,
                    T. de Kock,
                    J. Yao
        Status:     Best Current Practice
        Stream:     IETF
        Date:       August 2023
        Mailbox:    [email protected],
                    [email protected],
                    [email protected],
                    [email protected],
                    [email protected]
        Pages:      6
        See Also:   BCP 238

        I-D Tag:    draft-ietf-sidrops-roa-considerations-08.txt

        URL:        https://www.rfc-editor.org/info/rfc9455

        DOI:        10.17487/RFC9455

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 BGP routes to IP address prefix(es). This memo discusses
operational problems that may arise from ROAs containing multiple IP
prefixes and recommends that each ROA contain a single IP prefix.

This document is a product of the SIDR Operations Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
IETF-Announce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-announce

Reply via email to