Fwd: New Version Notification for draft-ietf-httpbis-expect-ct-02.txt

This version expands the Expect-CT reporting format to support both RFC
6962 and 6962-bis SCTs.

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Mon, Aug 14, 2017 at 3:43 PM
Subject: New Version Notification for draft-ietf-httpbis-expect-ct-02.txt
To: "estark@google.com" <estark@google.com>

A new version of I-D, draft-ietf-httpbis-expect-ct-02.txt
has been successfully submitted by Emily Stark and posted to the
IETF repository.

Name:           draft-ietf-httpbis-expect-ct
Revision:       02
Title:          Expect-CT Extension for HTTP
Document date:  2017-08-14
Group:          httpbis
Pages:          18
URL:            https://www.ietf.org/internet-drafts/draft-ietf-httpbis-expe
Status:         https://datatracker.ietf.org/doc/draft-ietf-httpbis-expect-
Htmlized:       https://tools.ietf.org/html/draft-ietf-httpbis-expect-ct-02
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-ex
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-httpbis-expect

   This document defines a new HTTP header, named Expect-CT, that allows
   web host operators to instruct user agents to expect valid Signed
   Certificate Timestamps (SCTs) to be served on connections to these
   hosts.  When configured in enforcement mode, user agents (UAs) will
   remember that hosts expect SCTs and will refuse connections that do
   not conform to the UA's Certificate Transparency policy.  When
   configured in report-only mode, UAs will report the lack of valid
   SCTs to a URI configured by the host, but will allow the connection.
   By turning on Expect-CT, web host operators can discover
   misconfigurations in their Certificate Transparency deployments and
   ensure that misissued certificates accepted by UAs are discoverable
   in Certificate Transparency logs.

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.

The IETF Secretariat

Received on Monday, 14 August 2017 22:47:24 UTC