RFC 6484: Certificate Policy (CP) for the Resource Public Key Infrastructure (RPKI)
In plain English — editorial summary, not part of the RFC
This document describes the certificate policy for a Public Key Infrastructure (PKI) used to support attestations about Internet Number Resource (INR) holdings. Each organization that distributes IP addresses or Autonomous System (AS) numbers to an organization will, in parallel, issue a (public key) certificate reflecting this distribution. These certificates will enable verification that the resources indicated in the certificate have been distributed to the holder of the associated private key and that this organization is the current, unique holder of these resources. This memo documents an Internet Best Current Practice.
Document record
- Document ID
- RFC6484
- Published
- February 2012
- Authors
- S. Kent; D. Kong; K. Seo; R. Watro
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- rtg
- Pages
- 35
- Also known as
- BCP173
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5520Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based MechanismCurrent
April 2009
- RFC 6483Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs)Current
February 2012
- RFC 6485The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure (RPKI)Obsoleted
February 2012
- RFC 6482A Profile for Route Origin Authorizations (ROAs)Obsoleted
February 2012
- RFC 6486Manifests for the Resource Public Key Infrastructure (RPKI)Obsoleted
February 2012
- RFC 6487A Profile for X.509 PKIX Resource CertificatesUpdated
February 2012
- RFC 6481A Profile for Resource Certificate Repository StructureCurrent
February 2012
- RFC 6480An Infrastructure to Support Secure Internet RoutingCurrent
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?