RFC 6486: Manifests for the Resource Public Key Infrastructure (RPKI)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9286.
Current version: RFC 9286 — Manifests for the Resource Public Key Infrastructure (RPKI)
In plain English — editorial summary, not part of the RFC
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 "stale" (valid) data and deletion of signed objects. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6486
- Published
- February 2012
- Authors
- R. Austein; G. Huston; S. Kent; M. Lepinski
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
- Obsoleted by:
- RFC 9286
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6485The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure (RPKI)Obsoleted
February 2012
- RFC 6487A Profile for X.509 PKIX Resource CertificatesUpdated
February 2012
- RFC 6484Certificate Policy (CP) for the Resource Public Key Infrastructure (RPKI)Current
February 2012
- RFC 6488Signed Object Template for the Resource Public Key Infrastructure (RPKI)Updated
February 2012
- RFC 6483Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs)Current
February 2012
- RFC 6489Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI)Current
February 2012
- RFC 6482A Profile for Route Origin Authorizations (ROAs)Obsoleted
February 2012
- RFC 6490Resource Public Key Infrastructure (RPKI) Trust Anchor LocatorObsoleted
February 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?