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

The information below is for an old version of the document
Document Type Active Internet-Draft (httpbis WG)
Last updated 2014-12-15 (latest revision 2014-08-18)
Replaces draft-hutton-httpbis-connect-protocol
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Aug 2015 - Submit Tunnel Protoc... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                A. Hutton
Internet-Draft                                                     Unify
Intended status: Standards Track                               J. Uberti
Expires: February 19, 2015                                        Google
                                                              M. Thomson
                                                                 Mozilla
                                                         August 18, 2014

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

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.

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 February 19, 2015.

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

Hutton, et al.          Expires February 19, 2015               [Page 1]
Internet-Draft               Tunnel-Protocol                 August 2014

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

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 next protocol label as was
   carried within the TLS handshake.  However, the HTTP-Protocol is an
   indication rather a negotiation since HTTP proxies do not implement
   the tunneled protocol.

1.1.  Requirements Language

   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 RFC 2119 [RFC2119].

2.  The Tunnel-Protocol HTTP Request Header Field

   Clients include the Tunnel-Protocol Request Header field in a HTTP
   Connect request to indicate the application layer protocol used
   within the tunnel.

Hutton, et al.          Expires February 19, 2015               [Page 2]
Internet-Draft               Tunnel-Protocol                 August 2014

2.1.  Header Field Values

   Valid values for the protocol field are taken from the registry
   established in [RFC7301].

2.2.  Syntax

   The ABNF (Augmented Backus-Naur Form) syntax for the Tunnel-Protocol
   header field is given below.  It is based on the Generic Grammar
Show full document text