Manifests for the Resource Public Key Infrastructure (RPKI)
RFC 9286
Revision differences
Document history
Date | By | Action |
---|---|---|
2022-09-06
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2022-09-05
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
2022-06-30
|
(System) | Received changes through RFC Editor sync (created alias RFC 9286, changed abstract to 'This document defines a "manifest" for use in the Resource Public … Received changes through RFC Editor sync (created alias RFC 9286, changed abstract to '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.', changed pages to 16, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2022-06-30, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-sidrops-6486bis and RFC 6486) |
2022-06-30
|
(System) | RFC published |