W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2014

new version trusted-proxy20 draft

From: Salvatore Loreto <salvatore.loreto@ericsson.com>
Date: Fri, 14 Feb 2014 18:56:14 +0000
To: HTTP Working Group <ietf-http-wg@w3.org>
CC: "draft-loreto-httpbis-trusted-proxy20@tools.ietf.org" <draft-loreto-httpbis-trusted-proxy20@tools.ietf.org>
Message-ID: <449272CA-71CB-4D7D-B431-A42140346B27@ericsson.com>
dear wg

we have submitted a new version of the "Explicit Trusted Proxy in HTTP/2.0" draft


I want to highlight that
the only change asked by this draft in order to support an Explicit Trusted Proxy
is the definition of a new ALPN protocol id value as you can read in the Abstract below.
No other changes to HTTP2 spec neither to the TLS protocol are required.


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

  The httpbis wg has agreed on the HTTP2 usage with HTTP URIs, with or
  without TLS, without any constraints from the standard (see: issue
  314).

  To distinguish between an HTTP2 connection meant to transport "https"
  URIs resources and an HTTP2 connection meant to transport "http" URIs
  resource, the draft proposes to

     register a new value in the Application Layer Protocol negotiation
     (ALPN) Protocol IDs registry specific to signal the usage of HTTP2
     to transport "http" URIs resources: h2clr.

  This document describes two alternative methods for an user-agent to
  automatically discover and for an user to provide consent for a
  Trusted Proxy to be securely involved when he or she is requesting an
  HTTP URI resource over HTTP2 with TLS.

   Section 3.1 proposes a solution based on sending a proxy certificate
   in the TLS handshake.

   Section 3.2 proposes a solution based on the presence of a Captive
   Proxy.

  The consent is supposed to be per network access.

  The draft also describes the role of the Trusted
  Proxy in helping the user to fetch HTTP URIs resource when the user
  has provided consent to the Trusted Proxy to be involved.

URL:            http://www.ietf.org/internet-drafts/draft-loreto-httpbis-trusted-proxy20-01.txt
Status:         https://datatracker.ietf.org/doc/draft-loreto-httpbis-trusted-proxy20/
Htmlized:       http://tools.ietf.org/html/draft-loreto-httpbis-trusted-proxy20-01
Diff:           http://www.ietf.org/rfcdiff?url2=draft-loreto-httpbis-trusted-proxy20-01



Comments, suggestion and feedback are really welcome

best regards
Salatore
Received on Friday, 14 February 2014 18:57:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:24 UTC