Opportunistic Security for HTTP
draft-ietf-httpbis-http2-encryption-10

Document Type Active Internet-Draft (httpbis WG)
Last updated 2017-02-20 (latest revision 2017-01-31)
Replaces draft-nottingham-http2-encryption
Stream IETF
Intended RFC status Experimental
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication Dec 2015
Document shepherd Mike Bishop
Shepherd write-up Show (last changed 2017-02-15)
IESG IESG state In Last Call (ends 2017-03-06)
Consensus Boilerplate Yes
Telechat date On agenda of 2017-03-16 IESG telechat
Responsible AD Alexey Melnikov
Send notices to michael.bishop@microsoft.com
IANA IANA review state IANA - Review Needed
IANA action state None
HTTP Working Group                                         M. Nottingham
Internet-Draft
Intended status: Experimental                                 M. Thomson
Expires: August 4, 2017                                          Mozilla
                                                        January 31, 2017

                    Opportunistic Security for HTTP
                 draft-ietf-httpbis-http2-encryption-10

Abstract

   This document describes how "http" URIs can be accessed using
   Transport Layer Security (TLS) to mitigate pervasive monitoring
   attacks.

Note to Readers

   Discussion of this draft takes place on the HTTP working group
   mailing list (ietf-http-wg@w3.org), which is archived at
   https://lists.w3.org/Archives/Public/ietf-http-wg/ .

   Working Group information can be found at http://httpwg.github.io/ ;
   source code and issues list for this draft can be found at
   https://github.com/httpwg/http-extensions/labels/opp-sec .

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 August 4, 2017.

Copyright Notice

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

Nottingham & Thomson     Expires August 4, 2017                 [Page 1]
Internet-Draft         Opportunistic HTTP Security          January 2017

   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
   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.  Goals and Non-Goals . . . . . . . . . . . . . . . . . . .   3
     1.2.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
   2.  Using HTTP URIs over TLS  . . . . . . . . . . . . . . . . . .   3
     2.1.  Alternative Server Opt-In . . . . . . . . . . . . . . . .   4
     2.2.  Interaction with "https" URIs . . . . . . . . . . . . . .   5
     2.3.  The "http-opportunistic" well-known URI . . . . . . . . .   5
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
     4.1.  Security Indicators . . . . . . . . . . . . . . . . . . .   6
     4.2.  Downgrade Attacks . . . . . . . . . . . . . . . . . . . .   7
     4.3.  Privacy Considerations  . . . . . . . . . . . . . . . . .   7
     4.4.  Confusion Regarding Request Scheme  . . . . . . . . . . .   7
     4.5.  Server Controls . . . . . . . . . . . . . . . . . . . . .   7
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   This document describes a use of HTTP Alternative Services [RFC7838]
   to decouple the URI scheme from the use and configuration of
   underlying encryption, allowing a "http" URI [RFC7230] to be accessed
   using Transport Layer Security (TLS) [RFC5246] opportunistically.

   Serving "https" URIs requires avoiding Mixed Content
   [W3C.CR-mixed-content-20160802], which is problematic in many
   deployments.  This document describes a usage model whereby sites can
   serve "http" URIs over TLS, thereby avoiding these issues, while
   still providing protection against passive attacks.

   Opportunistic Security [RFC7435] does not provide the same guarantees
   as using TLS with "https" URIs; it is vulnerable to active attacks,
   and does not change the security context of the connection.
Show full document text