IETF Logo Mail Archive

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

Lucas Pardue <lucaspardue.24.7@gmail.com> Fri, 16 October 2020 11:25 UTC

Return-Path: <lucaspardue.24.7@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 E7FC43A0EB9; Fri, 16 Oct 2020 04:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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_ENVFROM_END_DIGIT=0.25, 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 2UdeWlrCedmL; Fri, 16 Oct 2020 04:25:14 -0700 (PDT)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 33E723A0EBD; Fri, 16 Oct 2020 04:25:14 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id l16so1937262eds.3; Fri, 16 Oct 2020 04:25:14 -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=oTN2/xtDfPfAFWGr+AEDF+0UJqB7arK2Y7gYutgv1UM=; b=rKXP/ZF+Wuw3ytX/BRVTRp6z7HXl8TjxuPaw/M07NxWCb5Yv6IPIJWA5rFIc131cHe P5OAdMQ0wHS60Tat9k5HvSHpetv9aWnUCOeNT3JfoddRF4q8IH/RZd9bpi/VvM3eyQXT OoV5y9wkpcvwU2HWJYoNQE+6G5xTz+WzzwlsxTwvLlUo0kyKZR9vJ7ScSKOmr3vGKouf BP0WGObytwBr4rj6HqbQGRLBJEap8TM7zLcFhutg1YP1UAhPYeyfsHY3ctMRtJnVMDx/ IetjFIgZt516gJ8EBNX8KFZS3KEaqCjpMnZcM3bQGTV44WsDbYN+bvkkS3JQD3XMXHOP opxQ==
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=oTN2/xtDfPfAFWGr+AEDF+0UJqB7arK2Y7gYutgv1UM=; b=FwEDC4ZyGx65KX9ao/opnxmB1fI6ip/B0vVZKbB4KdDakEKbV1BaHMNeloyzFJ7qZG 8+n93qlIgVpyD9dNhHJaH9wS3cyWWj9MQyCBwPWSmdbRxSNqMk1MUM3EIkfYNQNHtw8L qt1aGOwfJH2FdEHYsqZ0h9BICo37peyBbcLKxORGM8UABMEHP1YI1sBw+MW1ahAJFCA9 madY2n0ssbZ06GNv8j8moW0H82t0PZRKzJ6OZZxlQcvWqe05g5H/mDOy+Ha88hLCspf1 RbEDoH8bMtfuVNq9kXik0446gHeVToRLYx5r6zsnIW4XlHv+8w2JMJZQ1Tsr+9GHgPZi 6gJQ==
X-Gm-Message-State: AOAM5331E3P5agy9ITBFtSlUn50ejPIp5ZJ43jOJZDbersbrzDyPdrc4 LaA7uifSNUBPtH2vdQOPqjtzwrJwMA0oaMb3LBc=
X-Google-Smtp-Source: ABdhPJxUm17ciwm/90y7d9N9z/wVrerVCGNHno7Kc5wlXsTDp4pGLLV1+o4+EYekRIlNB6LM9VFEB+fzFKfLwb2akhw=
X-Received: by 2002:aa7:cad6:: with SMTP id l22mr3249931edt.229.1602847512752; Fri, 16 Oct 2020 04:25:12 -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>
In-Reply-To: <A50ACE49-E067-44ED-988D-B70E261482ED@ericsson.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Fri, 16 Oct 2020 12:25:03 +0100
Message-ID: <CALGR9oa9_OapmpK721SQG4iOboJiTgnmNfSEO9Rwb4Mq110bNA@mail.gmail.com>
Subject: Re: [Masque] HTTP DATA frames for HTTP CONNECT?
To: Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>
Cc: David Schinazi <dschinazi.ietf@gmail.com>, Mike Bishop <mbishop@evequefou.be>, QUIC WG <quic@ietf.org>, MASQUE <masque@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a074cd05b1c8042a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/w1leklC4XLXLaRav5Ug5V6BHHxs>
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: Fri, 16 Oct 2020 11:25:16 -0000

On Fri, 16 Oct 2020, 09:45 Mirja Kuehlewind, <mirja.kuehlewind=
40ericsson.com@dmarc.ietf.org> wrote:

> Hi David,
>
>
>
> I was sending this request to exactly understand if or what the issues
> are/could be in not having the DATA frame. Can you maybe further explain
> which issue you see?
>
I can't speak for David but the issues I forsee come from additional code
paths needed to support the feature. The frame parsing code needs to become
HTTP method-aware, which is not the case in the implementation I own.

With QUIC chair hat on: this is very late to be proposing design changes.
It might even be too late. I'm setting a high bar here for compelling
evidence or support that something needs to be changed.

Cheers
Lucas



masque <https://www.ietf.org/mailman/listinfo/masque>
>
>

v2.23.0 | Report a Bug | By Email