Hybrid Encapsulation Layer for IP and UDP Messages (HELIUM)
draft-schwartz-httpbis-helium-00

Document Type Active Internet-Draft (individual)
Last updated 2018-06-25
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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                                                      B. Schwartz
Internet-Draft                                                    Google
Intended status: Standards Track                           June 25, 2018
Expires: December 27, 2018

      Hybrid Encapsulation Layer for IP and UDP Messages (HELIUM)
                    draft-schwartz-httpbis-helium-00

Abstract

   HELIUM is a protocol that can be used to implement a UDP proxy, a
   VPN, or a hybrid of these.  It is intended to run over a reliable,
   secure substrate transport.  It can serve a variety of use cases, but
   its initial purpose is to enable HTTP proxies to forward non-TCP
   flows.

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 December 27, 2018.

Copyright Notice

   Copyright (c) 2018 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Schwartz                Expires December 27, 2018               [Page 1]
Internet-Draft                   HELIUM                        June 2018

Table of Contents

   1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  HELIUM Inner Protocol (HIP) . . . . . . . . . . . . . . . . .   3
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Abstract Structure  . . . . . . . . . . . . . . . . . . .   4
       2.3.1.  Error codes . . . . . . . . . . . . . . . . . . . . .   6
     2.4.  CBOR-based Encoding (HIP-CBOR)  . . . . . . . . . . . . .   7
     2.5.  Addressing  . . . . . . . . . . . . . . . . . . . . . . .   8
       2.5.1.  IP Header . . . . . . . . . . . . . . . . . . . . . .   9
       2.5.2.  UDP Header  . . . . . . . . . . . . . . . . . . . . .   9
     2.6.  Example Configurations  . . . . . . . . . . . . . . . . .   9
       2.6.1.  Single IP tunnel  . . . . . . . . . . . . . . . . . .   9
       2.6.2.  Multiple source IPs in one context  . . . . . . . . .   9
       2.6.3.  Domain-based proxy  . . . . . . . . . . . . . . . . .  10
       2.6.4.  UDP proxy with PMTUD and traceroute . . . . . . . . .  10
       2.6.5.  Advanced DNS queries  . . . . . . . . . . . . . . . .  10
       2.6.6.  UDP Server Application  . . . . . . . . . . . . . . .  11
       2.6.7.  High-Performance Delay-based Congestion Control . . .  11
     2.7.  Optimizations . . . . . . . . . . . . . . . . . . . . . .  11
   3.  WebSocket as a HELIUM Substrate (HELIUM-WebSocket)  . . . . .  12
     3.1.  Direct Configuration  . . . . . . . . . . . . . . . . . .  12
     3.2.  Implicit Configuration from an HTTP proxy . . . . . . . .  12
     3.3.  Optimizations . . . . . . . . . . . . . . . . . . . . . .  13
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Overview

   This proposal describes a network tunnel that is intended as a
   natural extension or complement to existing HTTP proxies.  It has two
   components

   o  A flexible packet-oriented tunneling protocol that can act as
      either a VPN or a UDP proxy (Section 2)

   o  A substrate for this protocol that allows it to run as part of an
      HTTPS server (Section 3)

   This design combines the benefits of several existing protocols, such
   as [OpenConnect] and [TURN].  Like OpenConnect, this protocol gains
   the privacy, authentication, and management benefits of HTTPS.  Like

Schwartz                Expires December 27, 2018               [Page 2]
Show full document text