IETF Logo Mail Archive

Re: [Moq] Exploring HTTP/3

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 09 February 2023 16:00 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: moq@ietfa.amsl.com
Delivered-To: moq@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35515C1575D9 for <moq@ietfa.amsl.com>; Thu, 9 Feb 2023 08:00:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6LF0epwEhfwO for <moq@ietfa.amsl.com>; Thu, 9 Feb 2023 08:00:39 -0800 (PST)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE585C1575D8 for <moq@ietf.org>; Thu, 9 Feb 2023 08:00:39 -0800 (PST)
Received: by mail-pf1-x42d.google.com with SMTP id 144so1594131pfv.11 for <moq@ietf.org>; Thu, 09 Feb 2023 08:00:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3WjhDedxFtkS5Dn4fp5+Xedtbo983rBueB4i4AEqz0k=; b=UNWx2F+0iMKpC6ZeGFrDy7Y907XvLP11z/x/583pw3aK4LRPxi4wBxWOxWg9CNWlrq zTxTG3vyWBuelehsLtAPcnTENDxwp2sxaQRArSCzli4mgIhFNeJhSmztZVsOU/+dcB6N aEQCXze+N9SRJb8yr+R1tEtXYs2IhVXWY+ExdWsLx15/ASJg6ofgC2kngjXhqQe3bEGl isnazmh2EoWrser9FczLYPKNiCsQSde5avI3MBAeovKu/84Bb3uUgVcod8ikDd+IfiEI ggtEbuMHnp9VWQvlzvTrHOxdKMuxY65qxQaZdeRY8xLJF9K9/OKMbVp46M0xo8mqO9fW /MCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3WjhDedxFtkS5Dn4fp5+Xedtbo983rBueB4i4AEqz0k=; b=q0LuMdJd1KcXBHMS7E9snqTN9fmJW9voSzY1UxEiQoaFU39SNHOCcY/e70++fXILxx TSxMMkbJKquUzrcn+HYhoHhYE3GZN3DCFIuwr3g9uOp20o0auUFqb/bkP7o+l0+Ror3a sNX460mozq8im+yoR0jZ00MdT3xa9B/NteaHDsF8cTDBRAHarODlZhh3l/EJKvplZIFV t1k7EjqDtahbGp4ygX15lx0SqpmB6a9fTFrEWc1Oo3tjtqDJ9A9FH11/jdevEDJdMRQ2 Duhh7edJRO+OjpIkh7XPTN7AxGtAfT4KRrdK/BQHS/xgnV5Znf94uCZkjrb4Zl3nvxu5 XeAg==
X-Gm-Message-State: AO0yUKVGIaPpDmVluztTzRrW3q69q8JY9iLo8mdS6skFiYMwBsiPU4HK ppefdpL0Fq5BcDHa9QtaLmeN+1c0V0UjT/KJm3ia3t3b/eY=
X-Google-Smtp-Source: AK7set9sF/IfJIxXqv/e3pgUsmO2LTAtEq/PZnUaqtyXntgF8rSZE8hw4xnlY9PZxtBfXgg3MyNlUapbDBzKeu/H60Q=
X-Received: by 2002:a63:7349:0:b0:4eb:ee7f:baa2 with SMTP id d9-20020a637349000000b004ebee7fbaa2mr2283568pgn.65.1675958438882; Thu, 09 Feb 2023 08:00:38 -0800 (PST)
MIME-Version: 1.0
References: <CAHVo=ZmD7KvKxh2tTeaM2B+0q9=qZPgBydmfaHor5MaPODZf6w@mail.gmail.com> <CALGR9oas8cMBrX1WVf64fH13jr1r-S0KQB5spNzFj41k9Lgk+A@mail.gmail.com> <CAHVo=Z=Nov7B24A=M2pxPnUgyBg3n-AjF8AD2mKwgbTQ81F+mA@mail.gmail.com> <CALGR9ob4i7Z8zuqFVHtzOGV3QMTFjvOK4uZW3Xfvb5ZsoULvMg@mail.gmail.com>
In-Reply-To: <CALGR9ob4i7Z8zuqFVHtzOGV3QMTFjvOK4uZW3Xfvb5ZsoULvMg@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 09 Feb 2023 10:00:12 -0600
Message-ID: <CAKKJt-eC=h20Va4+64r=zkhYXK_ypC+txLqzgpr+YL=HW-DD+g@mail.gmail.com>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Luke Curley <kixelated@gmail.com>, MOQ Mailing List <moq@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000068788a05f4467bc8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/KEi-xgmdFsWZFkjjtg5wlfpNl2o>
Subject: Re: [Moq] Exploring HTTP/3
X-BeenThere: moq@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Media over QUIC <moq.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/moq>, <mailto:moq-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/moq/>
List-Post: <mailto:moq@ietf.org>
List-Help: <mailto:moq-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/moq>, <mailto:moq-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2023 16:00:40 -0000

Lucas,

On Wed, Feb 8, 2023 at 4:55 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

>
>> And yeah, I agree that browsers are the main obstacles when pushing
>> media, but that doesn't change too much with WebTransport. We still need a
>> way to set the priority when pushing a WebTransport stream, much like we
>> would need a way to set the priority when issuing a HTTP PUT. I suppose
>> it's easier to modify WebTransport since it's in development.
>>
>
> The W3C WebTransport WG has been considering the questions of
> prioritization and congestion control feedback for a relatively long time.
> And we have been making progress. It has the right people and the right
> charter to work on it. I'm a little pessimistic about trying to get
> momentum for HTTP upload changes MoQ could require, in the sorts of
> timeframes that MoQ would find useful. For context, fetch *does *even
> support preference of HTTP version, nor exposese connection pooling. But
> maybe I'm too conservative in this regard. Asking ourselves the questions
> is definitely worthwhile.
>

Could this have been "fetch *does NOT* even support preference of HTTP
version"?

I was guessing so, but didn't want to guess when I could ask.

Best,

Spencer

v2.41.0 | Report a Bug | By Email | System Status