Certificate Transparency (CT) System Architecture
draft-kent-trans-architecture-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Stephen Kent , David Mandelberg , Karen Seo | ||
| Last updated | 2016-08-04 (Latest revision 2016-02-01) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes the architecture for Certificate Transparency (CT) focusing on the Web PKI context. It defines the goals of CT and the elements that comprise the CT system. It also describes the major features of these elements. Other documents, cited in the References, establish requirements for these CT system elements and describe their operation in greater detail.
Authors
Stephen Kent
David Mandelberg
Karen Seo
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)