Expect-CT
draft-stark-expect-ct-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-10-30
Replaced by draft-ietf-httpbis-expect-ct
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           E. Stark
Internet-Draft                                                    Google
Intended status: Experimental                           October 30, 2016
Expires: May 3, 2017

                               Expect-CT
                        draft-stark-expect-ct-00

Abstract

   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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 3, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents

Stark                      Expires May 3, 2017                  [Page 1]
Internet-Draft                  Expect-CT                   October 2016

   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Server and Client Behavior  . . . . . . . . . . . . . . . . .   3
     2.1.  Response Header Field Syntax  . . . . . . . . . . . . . .   3
       2.1.1.  The report-uri Directive  . . . . . . . . . . . . . .   4
       2.1.2.  The enforce Directive . . . . . . . . . . . . . . . .   5
       2.1.3.  The max-age Directive . . . . . . . . . . . . . . . .   5
     2.2.  Server Processing Model . . . . . . . . . . . . . . . . .   6
       2.2.1.  HTTP-over-Secure-Transport Request Type . . . . . . .   6
       2.2.2.  HTTP Request Type . . . . . . . . . . . . . . . . . .   6
     2.3.  User Agent Processing Model . . . . . . . . . . . . . . .   6
       2.3.1.  Expect-CT Header Field Processing . . . . . . . . . .   7
       2.3.2.  Noting an Expect-CT Host - Storage Model  . . . . . .   7
       2.3.3.  HTTP-Equiv <meta> Element Attribute . . . . . . . . .   8
     2.4.  Noting Expect-CT  . . . . . . . . . . . . . . . . . . . .   9
     2.5.  Evaluating Expect-CT Connections for CT Compliance  . . .   9
   3.  Reporting Expect-CT Failure . . . . . . . . . . . . . . . . .  10
     3.1.  Generating a violation report . . . . . . . . . . . . . .  10
     3.2.  Sending a violation report  . . . . . . . . . . . . . . .  12
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
     4.1.  Maximum max-age . . . . . . . . . . . . . . . . . . . . .  12
   5.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  12
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   7.  Usability Considerations  . . . . . . . . . . . . . . . . . .  12
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     8.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   This document defines a new HTTP header that enables UAs to identify
   web hosts that expect the presence of Signed Certificate Timestamps
   (SCTs) [RFC6962] in future Transport Layer Security (TLS) [RFC5246]
Show full document text