[Sidrops] RFC 9286 on Manifests for the Resource Public Key Infrastructure (RPKI)

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

        RFC 9286

        Title:      Manifests for the Resource Public 
                    Key Infrastructure (RPKI) 
        Author:     R. Austein,
                    G. Huston,
                    S. Kent,
                    M. Lepinski
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2022
        Mailbox:    sra@hactrn.net,
                    gih@apnic.net,
                    kent@alum.mit.edu,
                    mlepinski@ncf.edu
        Pages:      16
        Obsoletes:  RFC 6486

        I-D Tag:    draft-ietf-sidrops-6486bis-11.txt

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

        DOI:        10.17487/RFC9286

This document defines a "manifest" for use in the Resource Public Key
Infrastructure (RPKI). A manifest is a signed object (file) that
contains a listing of all the signed objects (files) in the
repository publication point (directory) associated with an authority
responsible for publishing in the repository. For each certificate,
Certificate Revocation List (CRL), or other type of signed objects
issued by the authority that are published at this repository
publication point, the manifest contains both the name of the file
containing the object and a hash of the file content. Manifests are
intended to enable a relying party (RP) to detect certain forms of
attacks against a repository. Specifically, if an RP checks a
manifest's contents against the signed objects retrieved from a
repository publication point, then the RP can detect replay attacks,
and unauthorized in-flight modification or deletion of signed
objects. This document obsoletes RFC 6486.

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-editor@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