RFC 2510: Internet X.509 Public Key Infrastructure Certificate Management Protocols
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4210.
Current document in this lineage: RFC 9810 — Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP); RFC 9811 — Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP)
In plain English — editorial summary, not part of the RFC
This document describes the Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocols. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2510
- Published
- March 1999
- Authors
- C. Adams; S. Farrell
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 72
- Also known as
- —
- Obsoleted by:
- RFC 4210
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
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 3129Requirements for Kerberized Internet Negotiation of KeysCurrent
June 2001
- RFC 2527Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkObsoleted
March 1999
- RFC 2528Internet X.509 Public Key Infrastructure Representation of Key Exchange Algorithm (KEA) Keys in Internet X.509 Public Key Infrastructure CertificatesCurrent
March 1999
- RFC 2539Storage of Diffie-Hellman Keys in the Domain Name System (DNS)Updated
March 1999
- RFC 2540Detached Domain Name System (DNS) InformationCurrent
March 1999
- RFC 2409The Internet Key Exchange (IKE)Obsoleted
November 1998
- RFC 2404The Use of HMAC-SHA-1-96 within ESP and AHCurrent
November 1998
- RFC 1828IP Authentication using Keyed MD5Current
August 1995
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?