RFC 6492: A Protocol for Provisioning Resource Certificates
In plain English — editorial summary, not part of the RFC
This document defines a framework for certificate management interactions between an Internet Number Resource issuer ("issuer") and an Internet Number Resource recipient ("subject") through the specification of a protocol for interaction between the two parties. The protocol supports the transmission of requests from the subject, and corresponding responses from the issuer encompassing the actions of certificate issuance, certificate revocation, and certificate status information reports. This protocol is intended to be limited to the application of Internet Number Resource Certificate management and is not intended to be used as part of a more general certificate management framework. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6492
- Published
- February 2012
- Authors
- G. Huston; R. Loomans; B. Ellacott; R. Austein
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6493The Resource Public Key Infrastructure (RPKI) Ghostbusters RecordCurrent
February 2012
- RFC 6491Resource Public Key Infrastructure (RPKI) Objects Issued by IANACurrent
February 2012
- RFC 6489Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI)Current
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 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?