Manifests for the Resource Public Key Infrastructure
RFC 9286, “Manifests for the Resource Public Key Infrastructure”, is a Proposed Standard document published in June 2022 by R. Austein, G. Huston, S. Kent, M. Lepinski. It obsoletes RFC 6486. It has since been updated by RFC 9981. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 9286 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9285 The Base45 Data Encoding
- RFC 9287 Greasing the QUIC Bit
- RFC 9284 Multihoming Deployment Considerations for DDoS Open Threat Signaling
- RFC 9288 Recommendations on the Filtering of IPv6 Packets Containing IPv6 Extension Headers at Transit Routers
- RFC 9283 IAB Charter Update for RFC Editor Model
- RFC 9289 Towards Remote Procedure Call Encryption by Default
- RFC 9282 Responsibility Change for the RFC Series
- RFC 9290 Concise Problem Details for Constrained Application Protocol APIs