Caching Secure HTTP Content using Blind Caches
draft-thomson-http-bc-01

Document Type Active Internet-Draft (individual)
Last updated 2016-10-30
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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                                         M. Thomson
Internet-Draft                                                   Mozilla
Intended status: Standards Track                             G. Eriksson
Expires: May 3, 2017                                         C. Holmberg
                                                                Ericsson
                                                        October 30, 2016

             Caching Secure HTTP Content using Blind Caches
                        draft-thomson-http-bc-01

Abstract

   A mechanism is described whereby a server can use client-selected
   shared cache.

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
   (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.

Thomson, et al.            Expires May 3, 2017                  [Page 1]
Internet-Draft                 Blind Cache                  October 2016

Table of Contents

   1.  Shared Caching for HTTPS  . . . . . . . . . . . . . . . . . .   2
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
   2.  Same-Host Secure Content Delegation . . . . . . . . . . . . .   3
     2.1.  Signaling Presence of a Proxy . . . . . . . . . . . . . .   3
     2.2.  Proxy Identification and Authentication . . . . . . . . .   4
   3.  Performance Optimizations . . . . . . . . . . . . . . . . . .   5
     3.1.  Proxy Cache Priming . . . . . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Shared Caching for HTTPS

   Shared caches allow an HTTP server to offload the responsibility for
   delivering certain content.  Content in the shared cache can be
   accessed efficiently by multiple clients, saving the origin server
   from having to serve those requests and ensuring that clients receive
   responses to cached requests more quickly.

   Proxy caching is the most common configuration for shared caching.  A
   proxy cache is either explicitly configured by a client, discovered
   as a result of being automatically configured.

   HTTPS [RFC2818] prevents the use of proxies by creating an
   authenticated end-to-end connection to the origin server or its
   gateway that is authenticated.  This provides a critical protection
   against man-in-the-middle attacks, but it also prevents the proxy
   from acting as a shared cache.

   Clients do not direct queries for "https" URIs to proxies.  Clients
   configured with a proxy use the CONNECT pseudo-method (Section 4.3.6
   of [RFC7231]) with any explicitly configured or discovered proxies to
   create an end-to-end tunnel.  Transparent proxies are unable to
   intercept connections that are protected with TLS.

   This document describes a method that enables shared caching for a
   limited set of "https" resources, as selected by the server.  The
   server conditionally delegates the hosting of secure content to
   itself.  This delegation includes a marker that signals permission
   for a client to send a request for an "https" resource via a proxy
   rather than insisting on an end-to-end TLS connection.

Show full document text