Subject: Re: [Trans] I-D Action: draft-ietf-trans-rfc6962-bis-19.txt

From: Eran Messeri <[email-masked]>
Date: Fri, 9 Sep 2016 11:09:33 +0100

Changelog between draft 18 and 19:

* Redaction has been moved to a separate document.
* STH Signature is over  TreeHeadDataV2 rather than TransItem (simplifying
signature checking on the client side).
* Addressed feedback from David Drysdale.
* Rename get-entry-for-certificate to get-entry-for-tbscertificate. Clarify
which TBSCertificate to hash.
* Indicate TLS clients may only evaluate compliance if they send both the
transparency_info and status_request TLS extensions.
* Indicate that TLS client certs are not in scope.
* Made NodeHash variable-length, so it's simpler to decode structures.
* Ticket 111: Use cached_info to indicate prior knowledge of CT compliance.

Future contributions should be made to the kramdown format of the -bis
document, which was converted from the XML format.

Eran

On Wed, Aug 31, 2016 at 9:39 PM, <[email-masked]> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Public Notary Transparency  of the IETF.
>
>         Title           : Certificate Transparency
>         Authors         : Ben Laurie
>                           Adam Langley
>                           Emilia Kasper
>                           Eran Messeri
>                           Rob Stradling
>         Filename        : draft-ietf-trans-rfc6962-bis-19.txt
>         Pages           : 53
>         Date            : 2016-08-31
>
> Abstract:
>    This document describes a 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.
>
>    Logs are network services that implement the protocol operations for
>    submissions and queries that are defined in this document.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-trans-rfc6962-bis-19
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-trans-rfc6962-bis-19
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> Trans mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/trans
>