Re: [Masque] Call for MASQUE use cases

Ted Hardie <ted.ietf@gmail.com> Mon, 24 February 2020 17:20 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: masque@ietfa.amsl.com
Delivered-To: masque@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC1853A0EF6 for <masque@ietfa.amsl.com>; Mon, 24 Feb 2020 09:20:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 wZI9fqBOhF6K for <masque@ietfa.amsl.com>; Mon, 24 Feb 2020 09:20:28 -0800 (PST)
Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E2053A0E1F for <masque@ietf.org>; Mon, 24 Feb 2020 09:20:28 -0800 (PST)
Received: by mail-oi1-x235.google.com with SMTP id a22so9642856oid.13 for <masque@ietf.org>; Mon, 24 Feb 2020 09:20:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=A6K8F4a1ddn7qHXOMl0LzXhO3embHl1wF9UEOLRQQjo=; b=tNcGG1zmBSX7KoyDuHS072QcM8flZDZCQHWH2npHDNxzxFAEmEo/LhLMpeQF9g2oRS Ws0Vti7eOureFjyEQ5mNxspZ2EplhwPcZbYU7a5bgRI6IGcd13MR9jkWpsk/hYGDTr2k RZykta6D59Svbf2QI/lMrE6jzw5yZCJk1vpP/1X8eym6zLIp6W7OvzvmSk1/sbhpArGc N4UE1kWNQhpzKwcF+kNr78URtVX2Big9k0X49faEFLIOTpni1WbvbxjsFrojxl+nk6Dc d+O33UrNyQYcilW2CNNeHF0POR6siYz5VWNZFrsdzvehof6/LjMMjdVNwCvhiVe/NGyB H/yA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=A6K8F4a1ddn7qHXOMl0LzXhO3embHl1wF9UEOLRQQjo=; b=M6mzKJhdmx5xOo9ICBxtmUA3X7Q54s5eehSjwADzvhyJwN/0UYk0Y3DaUKHegbIjcr uU8U4NucUkWh6vy1SsSeVSJ0Eu7lboukIPoHo6OEyxrAo4kqN0JH+DOXAYjBjoOTV8yU wTqI7YryocypMCVHx2eh3ZPHrkM9JZasbnmLYVaT+1aIIsT/eggOEFMrGluQmPnTcAaU rAd17mT0CJTXZiLOJNSRJgGUW0BOz8pky0usFONP1wFSY+G8Tjb0wFGh3jbQ1hiPACA1 9myoCegmWEH7VIyICE3xEkdmy/FNnRi6BRZyhrk+CVsFzrimhDy2EbOirjtoscMXsTgr 8eEw==
X-Gm-Message-State: APjAAAViWqC0n6Zxc20QCO2KrNgWcm9WI4E1bLaXOmfUr2ThX7K42Da7 v/apIphNJ/0h+teBj3nPwsd6zDSxhMkbgtD5dYY=
X-Google-Smtp-Source: APXvYqxRhRu6bgJ/CSERaINl6CjSyVU3mAvEjDyN8xFbb0KKiGStSVSCuXdZjiQZb8I/xqHLFNvQFcYsywea2kyi+mU=
X-Received: by 2002:a54:448b:: with SMTP id v11mr105970oiv.74.1582564827576; Mon, 24 Feb 2020 09:20:27 -0800 (PST)
MIME-Version: 1.0
References: <D46D764C-F682-472A-AFDA-32DDF5CA5F6B@heapingbits.net> <CABcZeBPMUNgOVWMS_sXPTsCU2R+EaK9JDuZsJQ5KSQROXE+4Sg@mail.gmail.com> <CAHbrMsAVXmyvqJKNzcmHOvM3NvPqhpfC9MuDEq9kNUBKe7=7=g@mail.gmail.com> <CAKKJt-etTk6CAqbL1MdSV6gdCgqC2Wz8cdUqbdzbM2h3LKAMhw@mail.gmail.com>
In-Reply-To: <CAKKJt-etTk6CAqbL1MdSV6gdCgqC2Wz8cdUqbdzbM2h3LKAMhw@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 24 Feb 2020 09:20:01 -0800
Message-ID: <CA+9kkMAp4J1XAftvU57ZO16X-Nht5KTt4bS4Brgt=G=FnUf3rg@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>, Eric Rescorla <ekr@rtfm.com>, Christopher Wood <caw@heapingbits.net>, MASQUE <masque@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000061be5b059f559613"
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/QrSheNZTcBAWMUPti-LJdhQj-jI>
Subject: Re: [Masque] Call for MASQUE use cases
X-BeenThere: masque@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiplexed Application Substrate over QUIC Encryption <masque.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/masque>, <mailto:masque-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/masque/>
List-Post: <mailto:masque@ietf.org>
List-Help: <mailto:masque-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/masque>, <mailto:masque-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2020 17:20:31 -0000

In-line.

Ted

On Mon, Feb 24, 2020 at 8:57 AM Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Hi, Ben,
>
> I have a couple of questions about some use cases you described (inline),
> but thank you for sending out your list.
>
> On Sun, Feb 23, 2020 at 10:06 PM Ben Schwartz <bemasc=
> 40google.com@dmarc.ietf.org> wrote:
>
>> I think virtually all the use cases for SOCKS and HTTP CONNECT are also
>> in-scope for MASQUE.  Additionally, there are some cases that they don't
>> handle, or that MASQUE could handle better:
>>
>>  - TCP proxying over congested/lossy client-proxy links.  SOCKS and
>> HTTP/1.1 don't multiplex, so the congestion controllers for each TCP
>> connection fight over this link.  HTTP/2 multiplexes but has head-of-line
>> blocking on loss.  CONNECT over HTTP/3 would get us unified
>> congestion control without blocking.
>>
>
> IIRC, CONNECT currently doesn't know how to do HTTP/3 over QUIC, right? So
> is what you're thinking about
>
>    - Connect can do HTTP/3 - proxy - HTTP/3 or HTTP/2 - proxy - HTTP/2, OR
>    - Connect can do HTTP - proxy - HTTP, where the HTTP versions don't
>    have to match?
>
>  - Proxied WebRTC (or RTC generally).  Currently, using a proxy generally
> forces WebRTC to use TCP, which generally also forces it to route through a
> TURN server (another proxy!).  This adds up to significantly impaired
> latency and quality.  By supporting UDP, MASQUE could do better.
>
>>
>> - Virtual machine running in a webpage.  MASQUE could enable standardized
>> networking for virtual machines in WebAssembly.
>>
>> - Network debugging when using a proxy.  HTTP CONNECT doesn't provide any
>> indication of why a connection failed, e.g. to distinguish RST, FIN,
>> timeout, or an ICMP error.
>>
>
> We've come some distance since I was introducing myself at IESG meetings
> as "AD for the spin bit", but we haven't come a really long way - the spin
> bit is in and optional, which is fine, and we are noticing
> https://datatracker.ietf.org/doc/draft-ferrieuxhamchaoui-quic-lossbits/
> as a related draft, but we haven't had it on a QUIC working group agenda in
> the past year (IIRC),
>
It was the last item discussed at the last interim, see the minutes here:
https://github.com/quicwg/wg-materials/blob/master/interim-20-02/minutes.md

regards,

Ted Hardie


> even though it gets talked about in places like MOPS. And that's just one
> more (almost certainly optional) bit of information, if it does move
> forward.
>
> I'm intrigued by your proposed use case on network debugging, especially
> if proxying HTTP/3 using CONNECT becomes a common mode of operation - have
> you started to hash out details for this use case, what might be visible
> without revealing too much, etc.? If not, would you like to work on
> something with me (and, one hopes, smarter and more realistic QUIC people)?
>
> Best,
>
> Spencer
>
>
>> On Sat, Feb 22, 2020 at 6:14 PM Eric Rescorla <ekr@rtfm.com> wrote:
>>
>>> I am interested in this as an alternative transport for securely
>>> proxying HTTP traffic (cf. https://fpn.firefox.com/)
>>>
>>> -Ekr
>>>
>>>
>>> On Thu, Feb 20, 2020 at 7:13 PM Christopher Wood <caw@heapingbits.net>
>>> wrote:
>>>
>>>> The core MASQUE protocol [1] describes a simple negotiation mechanism
>>>> for various
>>>> applications. However, it omits use cases for these applications.
>>>> MASQUE
>>>> obfuscation
>>>> in support of a "hidden VPN" service is one use case [2]. Tunneling
>>>> QUIC
>>>> is another [3].
>>>>
>>>> Given that MASQUE and the upcoming BoF will be successful insofar as it
>>>> addresses important
>>>> use cases, I think it'd be useful to discuss these application use
>>>> cases
>>>> in more detail
>>>> before Vancouver. To that end, let's use this time before the meeting
>>>> to
>>>> discuss them!
>>>>
>>>> I'd like to ask interested parties to please surface use cases they
>>>> know
>>>> of (and care about).
>>>>
>>>> Thanks!
>>>> Chris
>>>>
>>>> [1] https://tools.ietf.org/html/draft-schinazi-masque-02
>>>> [2] https://tools.ietf.org/html/draft-schinazi-masque-obfuscation-00
>>>> [3] https://tools.ietf.org/html/draft-kuehlewind-quic-substrate-02
>>>>
>>>> --
>>>> Masque mailing list
>>>> Masque@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/masque
>>>>
>>> --
>>> Masque mailing list
>>> Masque@ietf.org
>>> https://www.ietf.org/mailman/listinfo/masque
>>>
>> --
>> Masque mailing list
>> Masque@ietf.org
>> https://www.ietf.org/mailman/listinfo/masque
>>
> --
> Masque mailing list
> Masque@ietf.org
> https://www.ietf.org/mailman/listinfo/masque
>