HTTP Strict Transport Security (HSTS)
draft-ietf-websec-strict-transport-sec-11

The information below is for an old version of the document
Document Type Active Internet-Draft (websec WG)
Last updated 2012-07-25 (latest revision 2012-07-10)
Replaces draft-hodges-strict-transport-sec
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
Shepherd write-up Show (last changed 2012-07-06)
IESG IESG state Waiting for AD Go-Ahead::Revised I-D Needed
Telechat date
Responsible AD Barry Leiba
Send notices to websec-chairs@tools.ietf.org, draft-ietf-websec-strict-transport-sec@tools.ietf.org
WEBSEC Working Group                                           J. Hodges
Internet-Draft                                                    PayPal
Intended status: Standards Track                              C. Jackson
Expires: January 11, 2013                     Carnegie Mellon University
                                                                A. Barth
                                                            Google, Inc.
                                                            Jul 10, 2012

                 HTTP Strict Transport Security (HSTS)
               draft-ietf-websec-strict-transport-sec-11

Abstract

   This specification defines a mechanism enabling web sites to declare
   themselves accessible only via secure connections, and/or for users
   to be able to direct their user agent(s) to interact with given sites
   only over secure connections.  This overall policy is referred to as
   HTTP Strict Transport Security (HSTS).  The policy is declared by web
   sites via the Strict-Transport-Security HTTP response header field,
   and/or by other means, such as user agent configuration, for example.

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 January 11, 2013.

Copyright Notice

   Copyright (c) 2012 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Hodges, et al.          Expires January 11, 2013                [Page 1]
Internet-Draft    HTTP Strict Transport Security (HSTS)         Jul 2012

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Organization of this specification . . . . . . . . . . . .  5
     1.2.  Document Conventions . . . . . . . . . . . . . . . . . . .  5
   2.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     2.1.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . .  5
     2.2.  HTTP Strict Transport Security Policy Effects  . . . . . .  6
     2.3.  Threat Model . . . . . . . . . . . . . . . . . . . . . . .  6
       2.3.1.  Threats Addressed  . . . . . . . . . . . . . . . . . .  6
         2.3.1.1.  Passive Network Attackers  . . . . . . . . . . . .  6
         2.3.1.2.  Active Network Attackers . . . . . . . . . . . . .  7
         2.3.1.3.  Web Site Development and Deployment Bugs . . . . .  7
       2.3.2.  Threats Not Addressed  . . . . . . . . . . . . . . . .  8
         2.3.2.1.  Phishing . . . . . . . . . . . . . . . . . . . . .  8
         2.3.2.2.  Malware and Browser Vulnerabilities  . . . . . . .  8
     2.4.  Requirements . . . . . . . . . . . . . . . . . . . . . . .  8
       2.4.1.  Overall Requirement  . . . . . . . . . . . . . . . . .  8
         2.4.1.1.  Detailed Core Requirements . . . . . . . . . . . .  8
         2.4.1.2.  Detailed Ancillary Requirements  . . . . . . . . .  9
   3.  Conformance Criteria . . . . . . . . . . . . . . . . . . . . . 10
   4.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . . 10
   5.  HSTS Mechanism Overview  . . . . . . . . . . . . . . . . . . . 12
   6.  Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     6.1.  Strict-Transport-Security HTTP Response Header Field . . . 13
       6.1.1.  The max-age Directive  . . . . . . . . . . . . . . . . 14
       6.1.2.  The includeSubDomains Directive  . . . . . . . . . . . 14
     6.2.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . 14
   7.  Server Processing Model  . . . . . . . . . . . . . . . . . . . 15
     7.1.  HTTP-over-Secure-Transport Request Type  . . . . . . . . . 15
     7.2.  HTTP Request Type  . . . . . . . . . . . . . . . . . . . . 15
Show full document text