RFC 9162
Certificate Transparency Version 2.0, December 2021
- File formats:
- Also available: XML file for editing
- Status:
- EXPERIMENTAL
- Obsoletes:
- RFC 6962
- Authors:
- B. Laurie
E. Messeri
R. Stradling - Stream:
- IETF
- Source:
- trans (sec)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9162
Discuss this RFC: Send questions or comments to the mailing list trans@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9162
Abstract
This document describes version 2.0 of the Certificate Transparency (CT) protocol for publicly logging the existence of Transport Layer Security (TLS) server certificates as they are issued or observed, in a manner that allows anyone to audit certification authority (CA) activity and notice the issuance of suspect certificates as well as to audit the certificate logs themselves. The intent is that eventually clients would refuse to honor certificates that do not appear in a log, effectively forcing CAs to add all issued certificates to the logs.
This document obsoletes RFC 6962. It also specifies a new TLS extension that is used to send various CT log artifacts.
Logs are network services that implement the protocol operations for submissions and queries that are defined in this document.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.