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

        RFC 9981

        Title:      Resource Public Key Infrastructure (RPKI) Manifest Number 
Handling
        Author:     T. Harrison,
                    G. Michaelson,
                    J. Snijders
        Status:     Proposed Standard
        Stream:     IETF
        Date:       May 2026
        Mailbox:    [email protected],
                    [email protected],
                    [email protected]
        Pages:      7
        Updates:    RFC 9286

        I-D Tag:    draft-ietf-sidrops-manifest-numbers-09

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

        DOI:        10.17487/RFC9981

The Resource Public Key Infrastructure (RPKI) makes use of signed objects 
called "manifests", each of which includes a "manifest number". This document 
updates RFC 9286 by specifying issuer and Relying Party (RP) behaviour when a 
manifest number reaches the largest possible value, a situation not considered 
in RFC 9286.

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

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol 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/series/rfc-download/

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

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to