RFC 7030: Enrollment over Secure Transport
In plain English — editorial summary, not part of the RFC
This document profiles certificate enrollment for clients using Certificate Management over CMS (CMC) messages over a secure transport. This profile, called Enrollment over Secure Transport (EST), describes a simple, yet functional, certificate management protocol targeting Public Key Infrastructure (PKI) clients that need to acquire client certificates and associated Certification Authority (CA) certificates. It also supports client-generated public/private key pairs as well as key pairs generated by the CA.
Document record
- Document ID
- RFC7030
- Published
- October 2013
- Authors
- M. Pritikin; P. Yee; D. Harkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 53
- Also known as
- —
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6698The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSAUpdated
August 2012
- RFC 6024Trust Anchor Management RequirementsCurrent
October 2010
- RFC 5758Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSACurrent
January 2010
- RFC 8410Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key InfrastructureUpdated
August 2018
- RFC 8555Automatic Certificate Management Environment (ACME)Current
March 2019
- RFC 8659DNS Certification Authority Authorization (CAA) Resource RecordCurrent
November 2019
- RFC 8737Automated Certificate Management Environment (ACME) TLS Application-Layer Protocol Negotiation (ALPN) Challenge ExtensionCurrent
February 2020
- RFC 5272Certificate Management over CMS (CMC)Obsoleted
June 2008
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?