Explicit Trusted Proxy in HTTP/2.0
draft-loreto-httpbis-trusted-proxy20-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-01-10
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)
HTTPBis Working Group                                          S. Loreto
Internet-Draft                                               J. Mattsson
Intended status: Standards Track                                 R. Skog
Expires: July 14, 2014                                          H. Spaak
                                                                Ericsson
                                                        January 10, 2014

                   Explicit Trusted Proxy in HTTP/2.0
                draft-loreto-httpbis-trusted-proxy20-00

Abstract

   The purpose of this Internet Draft is to continue the discussion on
   explicit and trusted proxy as intermediary of HTTP2S traffic.

   This document describes a method for an user agent to automatically
   discover, configure a proxy via a secure HTTP2.0 session.  The draft
   also proposes two alternative mechanisms allowing the presence of
   HTTP2.0 secure proxies for TLS protected traffic when an user-agent
   is requesting an http resource.

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 July 14, 2014.

Copyright Notice

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

Loreto, et al.            Expires July 14, 2014                 [Page 1]
Internet-Draft              Trusted Proxy 2.0               January 2014

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  How the Proxy establish the trust  . . . . . . . . . . . . . .  3
     3.1.  TLS Proxy Announcement . . . . . . . . . . . . . . . . . .  3
   4.  Use Explicit Proxy . . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  Tunelling  . . . . . . . . . . . . . . . . . . . . . . . .  5
       4.1.1.  Flow Control . . . . . . . . . . . . . . . . . . . . .  7
       4.1.2.  TLS Key Frame  . . . . . . . . . . . . . . . . . . . .  7
     4.2.  Secure Forward Proxy . . . . . . . . . . . . . . . . . . .  8
       4.2.1.  Secure Forward: contacting HTTPS resource  . . . . . . 11
   5.  Signalling the presence of a Proxy in between  . . . . . . . . 13
   6.  Cache  . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 13
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 13
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 14
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14

Loreto, et al.            Expires July 14, 2014                 [Page 2]
Internet-Draft              Trusted Proxy 2.0               January 2014

1.  Introduction

   This document describes two mechanisms that allows HTTP2.0 secure
   proxies for TLS protected traffic when an user-agent is requesting an
   http resource.  The proposed solutions are based the first on the
   ideas of [I-D.rpeon-httpbis-exproxy], the second on the experience
   done while testing the Ericsson 2.0 Proxy draft-06 implementation
   with the Chrome browser: this allows the user-agent to connect to the
   proxy and then allowing the proxy in turn to connect via a secure
   HTTP2.0 session to the origin server on the user-agent's behalf.
   Moreover both the mechanisms try to meet the goals listed in
   [I-D.vidya-httpbis-explicit-proxy-ps].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Terminology

3.  How the Proxy establish the trust

   An explicit and trusted proxy is preferable to a transparent MITM
Show full document text