RFC 6481: A Profile for Resource Certificate Repository Structure
In plain English — editorial summary, not part of the RFC
This document defines a profile for the structure of the Resource Public Key Infrastructure (RPKI) distributed repository. Each individual repository publication point is a directory that contains files that correspond to X.509/PKIX Resource Certificates, Certificate Revocation Lists and signed objects. This profile defines the object (file) naming scheme, the contents of repository publication points (directories), and a suggested internal structure of a local repository cache that is intended to facilitate synchronization across a distributed collection of repository publication points and to facilitate certification path construction. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6481
- Published
- February 2012
- Authors
- G. Huston; R. Loomans; G. Michaelson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6483Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs)Current
February 2012
- RFC 6487A Profile for X.509 PKIX Resource CertificatesUpdated
February 2012
- RFC 6916Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)Current
April 2013
- RFC 6480An Infrastructure to Support Secure Internet RoutingCurrent
February 2012
- RFC 6482A Profile for Route Origin Authorizations (ROAs)Obsoleted
February 2012
- RFC 6489Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI)Current
February 2012
- RFC 6472Recommendation for Not Using AS_SET and AS_CONFED_SET in BGPObsoleted
December 2011
- RFC 6491Resource Public Key Infrastructure (RPKI) Objects Issued by IANACurrent
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?