[Trans] I-D Action: draft-ietf-trans-rfc6962-bis-40.txt

internet-drafts@ietf.org Wed, 28 July 2021 22:16 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: trans@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: trans@ietf.org
Message-ID: <162751057508.32078.1841339552487272986@ietfa.amsl.com>
Date: Wed, 28 Jul 2021 15:16:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/IhJfr3qk4Jlf7op0wjAMlsoDnUs>
Subject: [Trans] I-D Action: draft-ietf-trans-rfc6962-bis-40.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Public Notary Transparency WG of the IETF.

        Title           : Certificate Transparency Version 2.0
        Authors         : Ben Laurie
                          Adam Langley
                          Emilia Kasper
                          Eran Messeri
                          Rob Stradling
	Filename        : draft-ietf-trans-rfc6962-bis-40.txt
	Pages           : 63
	Date            : 2021-07-28

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.

   [RFC Editor: please update 'RFCXXXX' to refer to this document, once
   its RFC number is known, through the document.]


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-trans-rfc6962-bis-40

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-trans-rfc6962-bis-40


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[Trans] I-D Action: draft-ietf-trans-rfc6962-bis-… internet-drafts