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

        
        RFC 9324

        Title:      Policy Based on the Resource Public Key
                    Infrastructure (RPKI) without Route Refresh 
        Author:     R. Bush,
                    K. Patel,
                    P. Smith,
                    M. Tinka
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2022
        Mailbox:    ra...@psg.com,
                    ke...@arrcus.com,
                    pfsi...@gmail.com,
                    mark@tinka.africa
        Pages:      7
        Updates:    RFC 8481

        I-D Tag:    draft-ietf-sidrops-rov-no-rr-08.txt

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

        DOI:        10.17487/RFC9324

A BGP speaker performing policy based on the Resource Public Key
Infrastructure (RPKI) should not issue route refresh to its neighbors
because it has received new RPKI data. This document updates RFC 8481
by describing how to avoid doing so by either keeping a full
Adj-RIB-In or saving paths dropped due to ROV (Route Origin
Validation) so they may be reevaluated with respect to new RPKI data.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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 rfc-edi...@rfc-editor.org.  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
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Reply via email to