The Other-Transport Extension: Arbitrary Transports over CONNECT-UDP
draft-duke-masque-other-transport-00

Document Type Active Internet-Draft (individual)
Author Martin Duke 
Last updated 2021-01-25
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Additional Resources
- GitHub Repository
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)
MASQUE                                                           M. Duke
Internet-Draft                                                  F5, Inc.
Intended status: Experimental                            25 January 2021
Expires: 29 July 2021

  The Other-Transport Extension: Arbitrary Transports over CONNECT-UDP
                  draft-duke-masque-other-transport-00

Abstract

   This document describes an extension to the HTTP CONNECT-UDP method
   [CONNECTUDP] that supports tunneling of other transport protocols, as
   long as the first four octets of those protocols encode the source
   and destination ports.

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 https://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 29 July 2021.

Copyright Notice

   Copyright (c) 2021 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 (https://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.

Duke                      Expires 29 July 2021                  [Page 1]
Internet-Draft        The Other-Transport Extension         January 2021

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions and Definitions . . . . . . . . . . . . . . .   3
   2.  Other-Transport Header Definition . . . . . . . . . . . . . .   3
   3.  Datagram Encoding of Proxied Packets  . . . . . . . . . . . .   4
   4.  Stream Encoding of Proxied Packets  . . . . . . . . . . . . .   4
   5.  HTTP Intermediaries . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  HTTP Header . . . . . . . . . . . . . . . . . . . . . . .   5
     7.2.  Stream Chunk Type Registration  . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The HTTP CONNECT method (section 4.3.6 of [RFC7231]) has long
   provided a means of tunneling a TCP connection over an HTTP stream.
   The CONNECT-UDP method [CONNECTUDP] extends this capability to
   include UDP datagrams over a stream.

   As CONNECT-UDP delivers discrete datagrams to each endpoint, it can
   extend conceptually to any packetized protocol.  The Other-Transport
   extension allows a CONNECT-UDP proxy to tunnel packets with non-TCP,
   non-UDP protocol numbers, as long as the corresponding protocol meets
   minimal formatting requirements.

   Specifically, any protocol header where the first four octets encode
   the source and destination ports can be tunneled using this
   framework.  The client and proxy include all other protocol header
   information in the datagrams delivered over the tunnel.  For example,
   33 (DCCP, [RFC4330]); 132 (SCTP, [RFC4960]); and 136 (UDPLite,
   [RFC3828]) would all be valid candidates for Other-Transport.

   In principle, TCP can be proxied using this extension as well.  This
   might provide advantages over traditional HTTP CONNECT if the
   client's TCP implementation has features lacking at the proxy.

Duke                      Expires 29 July 2021                  [Page 2]
Internet-Draft        The Other-Transport Extension         January 2021

1.1.  Conventions and Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.
Show full document text