IETF Logo Mail Archive

Re: [Masque] HTTP DATA frames for HTTP CONNECT?

Kazuho Oku <kazuhooku@gmail.com> Wed, 21 October 2020 01:31 UTC

Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D6783A08CD; Tue, 20 Oct 2020 18:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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] 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 zRhZZv9lUW5l; Tue, 20 Oct 2020 18:31:57 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (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 D09823A08D3; Tue, 20 Oct 2020 18:31:56 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id o26so501458ejc.8; Tue, 20 Oct 2020 18:31:56 -0700 (PDT)
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=UwsjeZwpPz4CVW9PWYq0eGMJOfCRQLMayH1Icuv76Nw=; b=rrJDPMGT2wa/tLwA6hvdEj9C8cw0K+9Frhl6Sb3vRHbnPaq1sf04MOdgkeCIjkDs5e V/5yJPfZl38icMNG6wjeokuukZMsdi4yVjfUOIx+JKI7IqBhXNxMQTV8NMOmVma27q9g VAoKfPMHsBD6WEV7FW3VLiibtWF+ht38uR7ndtaenLjJ2xrfRACL8RPEj5O22ntUg5la HZ/J6Po/jxfnvJtNNk6SctTdo88UhO0mAf50p3FKzUCteBa3lm4P5bcbb+JhZCSh/Au1 Wp7I0FE7HL1CIpZYs2dPNJeWoMbi7V9qpj2rzxm3XnSUeKx2R0mq4l+C14Z9ImpaG5a5 Pfhg==
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=UwsjeZwpPz4CVW9PWYq0eGMJOfCRQLMayH1Icuv76Nw=; b=oPfoAApSq2mC+Mf4lXD5nJoWyGEwiOI5+AYv+bQbEn7OiRRdbr16P0DTUAJ6or3ZKm TQWMrribaZnTgVJzkQzS/Ns9sJRapArLiaP8WFMTCMcdhsoAxnnQs1psmZoZIUgP8XKs t5irksLKzYnogZd7+08DtH7hSKrEH3cRZEeF1y5u/6NkqPdfaeb3i+wKqKBzQHpt7klC tAhtCetosZizq/oHRj2YGsZv2kTPREzuEQW8n/Q8CtXRrgTLtPUxr36BJuOVVivujhoG 2rXLYxYynW6GzRCLUv9MquStXcrz/JPfcMhPuuuXJFuO2sl2SM7uHXDrPDKJ0gKWeAxF Ve0w==
X-Gm-Message-State: AOAM532meQTLdtUQpPSyZPj+vWQsqYaNO/JiFtaDvGGkffHX381BPiLD hR/0cn8Endgr6MZcg6GsuP8TpUoRpclQbs2WdTE=
X-Google-Smtp-Source: ABdhPJy0UD/2UhggAyzjjZ7/pfsiQ5l9Yf3LdZEWfyNo1qLMjIF1HqB9vW/xliLVQR5jlxDv8kuCu5YXzsZA0a/8fik=
X-Received: by 2002:a17:906:68c4:: with SMTP id y4mr968346ejr.197.1603243915267; Tue, 20 Oct 2020 18:31:55 -0700 (PDT)
MIME-Version: 1.0
References: <A92255DF-F477-4DE6-9AA2-33373959E792@ericsson.com> <MN2PR22MB20934245C43D7DDA5BC8F5D4DA020@MN2PR22MB2093.namprd22.prod.outlook.com> <MN2PR22MB20933D2E25F5425EA848E0D7DA020@MN2PR22MB2093.namprd22.prod.outlook.com> <CAPDSy+62-q83vK0zuPs9kQXP4Akm6KX5Khp1q4PD_2wDpacKNw@mail.gmail.com> <A50ACE49-E067-44ED-988D-B70E261482ED@ericsson.com> <CALGR9oa9_OapmpK721SQG4iOboJiTgnmNfSEO9Rwb4Mq110bNA@mail.gmail.com> <2CEC578A-32A5-45C4-B3A9-F615C9EB9DBE@ericsson.com> <CALGR9obHNAvKgTM97uhK+KAEf1ua6D3dW5x2HUOoV0QVUROY9w@mail.gmail.com> <B92228CD-6AA0-40BE-AFA3-223AD17285F2@ericsson.com> <CALGR9oZKJ7vbmZDh74k0gsX2r4nkeEE3VRrrywozT0iqQRGfGA@mail.gmail.com> <CAKcm_gNeRs9zCyEFweiwPFV_wYXf4LAjYE9q+AoGEnqnTjeq=w@mail.gmail.com> <CAKcm_gPBjs1Dwx8L8=9g_gK79Ey29LX6Y-nFBYhfspP66VJ06Q@mail.gmail.com> <CALGR9oZERzWy6si5dtrgdcbMv4WGhAGTzV7TzjNfT_J_XKHApw@mail.gmail.com>
In-Reply-To: <CALGR9oZERzWy6si5dtrgdcbMv4WGhAGTzV7TzjNfT_J_XKHApw@mail.gmail.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 21 Oct 2020 10:31:44 +0900
Message-ID: <CANatvzwPT3gVu0kg6oRkuCMrkU6RwWEXwkZsfvWZe_2qwGDHAg@mail.gmail.com>
Subject: Re: [Masque] HTTP DATA frames for HTTP CONNECT?
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Ian Swett <ianswett@google.com>, David Schinazi <dschinazi.ietf@gmail.com>, QUIC WG <quic@ietf.org>, Mike Bishop <mbishop@evequefou.be>, Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>, MASQUE <masque@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000ed34505b2245038"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/SyK7Dj9A8-yyfG3ViJ8aP3mWarw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 01:31:58 -0000

I agree with others that we do not need to revisit the issue we discussed
in #1885. The conclusion there was that HTTP/3 will always use
application-layer framing.

Regarding how we might fix the issue *in the future*, my preferences goes,
as stated in one of the issue comments, to adding a transport-level
extension that allows "messages" (instead of bytes) to be sent over a QUIC
stream, then use that to send frames in HTTP/3. Doing so reduces the wire
overhead for any frame being sent, reduces the total complexity.

But what we should do *now* is ship QUIC and H3, they do not have to be
changed.


2020年10月21日(水) 8:07 Lucas Pardue <lucaspardue.24.7@gmail.com>:

> An extension seems entirely reasonable to me.
>
>
>

-- 
Kazuho Oku

v2.23.0 | Report a Bug | By Email