Opportunistic Security for HTTP/2
draft-ietf-httpbis-http2-encryption-11

Document Type Active Internet-Draft (httpbis WG)
Last updated 2017-03-21 (latest revision 2017-03-17)
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 (wg milestone: Dec 2015 - Submit HTTP Opportun... )
Document shepherd Mike Bishop
Shepherd write-up Show (last changed 2017-02-15)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to michael.bishop@microsoft.com
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
HTTP Working Group                                         M. Nottingham
Internet-Draft
Intended status: Experimental                                 M. Thomson
Expires: September 18, 2017                                      Mozilla
                                                          March 17, 2017

                   Opportunistic Security for HTTP/2
                 draft-ietf-httpbis-http2-encryption-11

Abstract

   This document describes how "http" URIs can be accessed using
   Transport Layer Security (TLS) and HTTP/2 to mitigate pervasive
   monitoring attacks.  This mechanism not a replacement for "https"
   URIs; it is vulnerable to active attacks.

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 September 18, 2017.

Copyright Notice

   Copyright (c) 2017 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
   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.

Nottingham & Thomson   Expires September 18, 2017               [Page 1]
Internet-Draft        Opportunistic HTTP/2 Security           March 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Goals and Non-Goals . . . . . . . . . . . . . . . . . . .   2
     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 . . . . . . . . . . . . . . . . . . . .   6
     4.3.  Privacy Considerations  . . . . . . . . . . . . . . . . .   6
     4.4.  Confusion Regarding Request Scheme  . . . . . . . . . . .   7
     4.5.  Server Controls . . . . . . . . . . . . . . . . . . . . .   7
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   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.  It allows an "http" URI to be accessed using
   HTTP/2 [RFC7230] and Transport Layer Security (TLS) [RFC5246] with
   Opportunistic Security [RFC7435].

   This document describes a usage model whereby sites can serve "http"
   URIs over TLS, thereby avoiding the problem of serving Mixed Content
   (described in [W3C.CR-mixed-content-20160802]) while still providing
   protection against passive attacks.

   Opportunistic Security does not provide the same guarantees as using
   TLS with "https" URIs, because it is vulnerable to active attacks,
   and does not change the security context of the connection.
   Normally, users will not be able to tell that it is in use (i.e.,
   there will be no "lock icon").

1.1.  Goals and Non-Goals

   The immediate goal is to make the use of HTTP more robust in the face
   of pervasive passive monitoring [RFC7258].

   A secondary (but significant) goal is to provide for ease of
Show full document text