RFC 6485: The Profile for Algorithms and Key Sizes for Use in 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 7935.
Current version: RFC 7935 — The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure
In plain English — editorial summary, not part of the RFC
This document specifies the algorithms, algorithms' parameters, asymmetric key formats, asymmetric key size, and signature format for the Resource Public Key Infrastructure (RPKI) subscribers that generate digital signatures on certificates, Certificate Revocation Lists, and signed objects as well as for the relying parties (RPs) that verify these digital signatures. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6485
- Published
- February 2012
- Authors
- G. Huston
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
- Obsoleted by:
- RFC 7935
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 6484Certificate Policy (CP) for the Resource Public Key Infrastructure (RPKI)Current
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 6483Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs)Current
February 2012
- RFC 6482A Profile for Route Origin Authorizations (ROAs)Obsoleted
February 2012
- RFC 6488Signed Object Template for the Resource Public Key Infrastructure (RPKI)Updated
February 2012
- RFC 6481A Profile for Resource Certificate Repository StructureCurrent
February 2012
- RFC 6489Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI)Current
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?