IETF Logo Mail Archive

RE: HTTP proposal for UDP proxying: HELIUM

Lucas Pardue <Lucas.Pardue@bbc.co.uk> Mon, 02 July 2018 22:26 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68B8F1313F0 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 2 Jul 2018 15:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.649
X-Spam-Level:
X-Spam-Status: No, score=-7.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JRmiZljam7YI for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 2 Jul 2018 15:26:31 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E9A21311DC for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 2 Jul 2018 15:26:29 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1fa7EZ-0004MY-3n for ietf-http-wg-dist@listhub.w3.org; Mon, 02 Jul 2018 22:23:47 +0000
Resent-Date: Mon, 02 Jul 2018 22:23:47 +0000
Resent-Message-Id: <E1fa7EZ-0004MY-3n@frink.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <Lucas.Pardue@bbc.co.uk>) id 1fa7EX-0004Lw-JA for ietf-http-wg@listhub.w3.org; Mon, 02 Jul 2018 22:23:45 +0000
Received: from mailout0.telhc.bbc.co.uk ([132.185.161.179]) by titan.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <Lucas.Pardue@bbc.co.uk>) id 1fa7EV-00030C-5G for ietf-http-wg@w3.org; Mon, 02 Jul 2018 22:23:45 +0000
Received: from BGB01XI1008.national.core.bbc.co.uk (bgb01xi1008.national.core.bbc.co.uk [10.161.14.22]) by mailout0.telhc.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w62MNJNn011980; Mon, 2 Jul 2018 23:23:19 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1008.national.core.bbc.co.uk ([10.161.14.22]) with mapi id 14.03.0389.001; Mon, 2 Jul 2018 23:23:19 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: HTTP Working Group <ietf-http-wg@w3.org>
CC: Ben Schwartz <bemasc@google.com>
Thread-Topic: HTTP proposal for UDP proxying: HELIUM
Thread-Index: AQHUDMW0/U3LDyKFzkSOOoCWf0ClAKR8iaTg
Date: Mon, 02 Jul 2018 22:23:18 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BB5EB4A@bgb01xud1012>
References: <CAHbrMsCVtGwQWvSyov0EK84a7+ac-25eC=am5YyqmcLJSQoZWg@mail.gmail.com>
In-Reply-To: <CAHbrMsCVtGwQWvSyov0EK84a7+ac-25eC=am5YyqmcLJSQoZWg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.161.213]
x-exclaimer-md-config: c91d45b2-6e10-4209-9543-d9970fac71b7
Content-Type: multipart/alternative; boundary="_000_7CF7F94CB496BF4FAB1676F375F9666A3BB5EB4Abgb01xud1012_"
MIME-Version: 1.0
X-W3C-Hub-Spam-Status: No, score=-4.7
X-W3C-Hub-Spam-Report: AWL=1.492, BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1fa7EV-00030C-5G ecc2360f00593862c3317c6db66a920e
X-Original-To: ietf-http-wg@w3.org
Subject: RE: HTTP proposal for UDP proxying: HELIUM
Archived-At: <https://www.w3.org/mid/7CF7F94CB496BF4FAB1676F375F9666A3BB5EB4A@bgb01xud1012>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/35605
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

To follow Ben’s previous email, I have published another draft in the UDP proxying family.

This one takes a broader look at today’s TCP tunnelling that uses the HTTP CONNECT method. It generalises the tunnelling concepts and surveys options that may be suited toward UDP or IP tunnels. Design considerations are captured, and some technical solutions are specced out for illustrative purposes. Four candidate solutions are proposed to help direct discussion, although the matrix of options supports many permutations.

Title:
   HTTP-initiated Network Tunnelling

Abstract:

   The HTTP CONNECT method allows an HTTP client to initiate, via a

   proxy, a TCP-based tunnel to a single destination origin.  This memo

   explores options for expanding HTTP-initiated Network Tunnelling

   (HiNT) to cater for diverse UDP and IP associations.



https://tools.ietf.org/html/draft-pardue-httpbis-http-network-tunnelling-00

Questions and reviews are welcomed. Ben and I will are scheduled to present our drafts at the HTTPbis session on Tuesday 17 July.

Kind regards
Lucas


From: Ben Schwartz [mailto:bemasc@google.com]
Sent: 25 June 2018 21:44
To: HTTP Working Group <ietf-http-wg@w3.org>
Subject: HTTP proposal for UDP proxying: HELIUM

Hello HTTPBIS,

In a thread a few months ago [1], there was call for interest in extending HTTP proxying (e.g. HTTP CONNECT) to support UDP traffic, motivated by the growth of QUIC and WebRTC.  Since then, the people who expressed interest have brainstormed some possible use cases and solutions.  I am emailing to present the first of what I hope will be several drafts that we will present on the topic and discuss at IETF 102.  This draft presents one possible solution enabling HTTP proxying of UDP.

https://www.ietf.org/id/draft-schwartz-httpbis-helium-00.txt

Title:
   Hybrid Encapsulation Layer for IP and UDP Messages (HELIUM)
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.

Questions and reviews much appreciated.

--Ben Schwartz

[1] https://www.ietf.org/mail-archive/web/httpbisa/current/msg30667.html

v2.23.0 | Report a Bug | By Email