The Tunnel-Protocol HTTP Request Header Field
draft-ietf-httpbis-tunnel-protocol-01

The information below is for an old version of the document
Document Type Active Internet-Draft (httpbis WG)
Last updated 2015-02-10 (latest revision 2015-01-19)
Replaces draft-hutton-httpbis-connect-protocol
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Aug 2015 - Submit Tunnel Protoc... )
Document shepherd Mark Nottingham
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Mark Nottingham" <mnot@mnot.net>
HTTPbis Working Group                                          A. Hutton
Internet-Draft                                                     Unify
Intended status: Standards Track                               J. Uberti
Expires: July 23, 2015                                            Google
                                                              M. Thomson
                                                                 Mozilla
                                                        January 19, 2015

             The Tunnel-Protocol HTTP Request Header Field
                 draft-ietf-httpbis-tunnel-protocol-01

Abstract

   This specification allows HTTP CONNECT requests to indicate what
   protocol will be used within the tunnel once established, using the
   Tunnel-Protocol request header field.

Editorial Note (To be removed by RFC Editor)

   Discussion of this draft takes place on the HTTPBIS working group
   mailing list (ietf-http-wg@w3.org), which is archived at [1].

   Working Group information can be found at [2] and [3]; source code
   and issues list for this draft can be found at [4].

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 23, 2015.

Copyright Notice

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

Hutton, et al.            Expires July 23, 2015                 [Page 1]
Internet-Draft               Tunnel-Protocol                January 2015

   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.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  The Tunnel-Protocol HTTP Request Header Field . . . . . . . .   3
     2.1.  Header Field Values . . . . . . . . . . . . . . . . . . .   3
     2.2.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   5
     5.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The HTTP CONNECT method (Section 4.3.6 of [RFC7231]) requests that
   the recipient establish a tunnel to the identified origin server and
   thereafter forward packets, in both directions, until the tunnel is
   closed.  Such tunnels are commonly used to create end-to-end virtual
   connections, through one or more proxies, which may then be secured
   using TLS (Transport Layer Security, [RFC5246]).

   The HTTP Tunnel-Protocol header field identifies the protocol that
   will be spoken within the tunnel, using the application layer next
   protocol identifier [RFC7301] specified for TLS [RFC5246].

   When CONNECT is used to establish a TLS tunnel, the Tunnel-Protocol
   header field may be used to carry the same application protocol label
   as will be carried within the TLS handshake.  If there are multiple
   possible application protocols, all of those application protocols
   are indicated.

   The Tunnel-Protocol header field carries an indication only.  In TLS,
   the final choice of application protocol is made by the server.
   Proxies do not implement the tunneled protocol, though they might
   choose to make policy decisions based on the value of the header
   field.

Hutton, et al.            Expires July 23, 2015                 [Page 2]
Internet-Draft               Tunnel-Protocol                January 2015

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
Show full document text