[Webtransport] Use of HTTP priorities in WebTransport
Ian Swett <ianswett@google.com> Thu, 01 April 2021 17:01 UTC
Return-Path: <ianswett@google.com>
X-Original-To: webtransport@ietfa.amsl.com
Delivered-To: webtransport@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F2323A1BAF for <webtransport@ietfa.amsl.com>; Thu, 1 Apr 2021 10:01:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 w8wwmvDQn1x0 for <webtransport@ietfa.amsl.com>; Thu, 1 Apr 2021 10:01:49 -0700 (PDT)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (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 E99E53A1BB1 for <webtransport@ietf.org>; Thu, 1 Apr 2021 10:01:48 -0700 (PDT)
Received: by mail-wm1-x330.google.com with SMTP id b2-20020a7bc2420000b029010be1081172so1250759wmj.1 for <webtransport@ietf.org>; Thu, 01 Apr 2021 10:01:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=OE8BaBwS8QnNovqVz8p4FQCkghYT+hN/C9psivx5cVo=; b=Fvnag01cvHhTJQmmLQCeLeVgZTPgK2ZuB8hU3GwvkZkJdFgD71pssfqDZx8wT6xdOw bQl3Ql6HiwWQSP8M6K2U3/+HBcsMPGj2CWUd3g5a6QypL1CPi17t9QCxKG4jNJ4ziZ8l xJ9lRF5zzReQ4H5MfvPquIh1ewUI2kTyujkKoJ1hpxK/ehmO/S14b5r6Sx6zGuHmm0yO AFimtpOsiopE9jtg/JMKrYyBwiKPdWDz99ol7O8qMiiszB1/GzgjUPV6xN1UKv5gYRJm vb3pRdHrsii0Lm9zM0cgHotM3Y+Er6yjIaguDbIifYvopP8GK5XJGD/p+ilTUu6SrQhg 3thQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=OE8BaBwS8QnNovqVz8p4FQCkghYT+hN/C9psivx5cVo=; b=WLZYEBd5dCqnRd4SQfW8eMnTsnSyaTACbAvyXhllXiMVs/8hxVnzNBLnbuVg33NMSx h96NS1SVwxVNsSQ9p5Nhq539TP+YAmUScswhnrT3lGNWF7YaHxQlzuyKw+t8nBSB6Jb2 QEqSkeaBnhsiFbz6MJ6t5q3NkKaFUz1FQ5b44dZ2gUAtE4fwP3zGMXPSLhyKw87uUISS 2i5vs5PuyVudL4zXJI7O6yNE13CEUE3Ih1b/94oO26m3j3hgaP2DCB1nDwYGBlGQDzWX mTknQIy1rrn7doMK6x5IuhyCudjPS6B+HVJJzpbcgfdaY+iQOtjRGU+PpirMvn53F4nl MDTA==
X-Gm-Message-State: AOAM533XS5qTxLrluwDGdy/0ZoB6HgdYIBXYTat7dg2xOMy3IQrbrxhM ss3iYKU/5MyUBouuGbbY0UaYgerFmx8GXkBLQuplm3u8LIZA4g==
X-Google-Smtp-Source: ABdhPJzTHZ1+daIvzdvGtwFzUIsNqREGPL13vFpu32dFJz9TlkPHyyF7XB07/4bEwLPdU4g2OTTDI0I2Ky4G91v4SFQ=
X-Received: by 2002:a7b:ce91:: with SMTP id q17mr9287406wmj.28.1617296505044; Thu, 01 Apr 2021 10:01:45 -0700 (PDT)
MIME-Version: 1.0
From: Ian Swett <ianswett@google.com>
Date: Thu, 01 Apr 2021 13:00:00 -0400
Message-ID: <CAKcm_gOMcFYF2YROhsbVW15Q+tnWfwGsHhrjxQwq1jJAyvLvVQ@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000aec81b05beec2fb5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/QyzmrD37GhwiPadSZu5FJhKTFIQ>
Subject: [Webtransport] Use of HTTP priorities in WebTransport
X-BeenThere: webtransport@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <webtransport.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webtransport>, <mailto:webtransport-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webtransport/>
List-Post: <mailto:webtransport@ietf.org>
List-Help: <mailto:webtransport-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webtransport>, <mailto:webtransport-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Apr 2021 17:01:54 -0000
Now that WebTransport is targeted at HTTP/3 and not QUIC, it seems logical to build on the prioritization work in the HTTP priorities draft( draft-ietf-httpbis-priority <https://tools.ietf.org/html/draft-ietf-httpbis-priority-03>). This could be particularly important when pooling HTTP/3 with WebTransport, but I think that priority model is a good one for WebTransport by itself as well. Except for bidi streams, most of this priority information wouldn't need to be sent on the wire, but it could be used by local schedulers. Thoughts? Ian
- [Webtransport] Use of HTTP priorities in WebTrans… Ian Swett
- Re: [Webtransport] Use of HTTP priorities in WebT… Lucas Pardue
- Re: [Webtransport] Use of HTTP priorities in WebT… Luke Curley
- Re: [Webtransport] Use of HTTP priorities in WebT… Ian Swett
- Re: [Webtransport] Use of HTTP priorities in WebT… Bernard Aboba
- Re: [Webtransport] Use of HTTP priorities in WebT… Kinuko Yasuda