Re: HTTP/3 with strict priorities (PR #2700)

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Fri, 17 May 2019 14:56 UTC

Return-Path: <dtikhonov@litespeedtech.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 C0B001200E3 for <quic@ietfa.amsl.com>; Fri, 17 May 2019 07:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 Znl_fjRTf9Wr for <quic@ietfa.amsl.com>; Fri, 17 May 2019 07:56:07 -0700 (PDT)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (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 8D402120363 for <quic@ietf.org>; Fri, 17 May 2019 07:55:49 -0700 (PDT)
Received: by mail-qt1-x831.google.com with SMTP id h1so8351708qtp.1 for <quic@ietf.org>; Fri, 17 May 2019 07:55:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=1C3KpaWAnC6bLx36qRvXMR+Laj8QYqMDjW3j9/6emQQ=; b=xe0GpPzJrlgFjo8ML9dhvPCSPC+hopAHPeh+4cvC6gmEw+GqcTExa3T/0WUpfKg3Gb paYKpL0vc79Z5KfckhVH8oXe/SJGTUjy+WFy38S+pZflD1wWB2srZPMsqDtoHhdFtUcN c+NuwzY9hNRSIG7uRJXHCYHtdnzoa72lqTJ0EUH37PJMqY2wJrnm6xwnX6UPELW6GmGv 1AHz44qRFd5La2DCD0ciPjgl/v2f4qQ/LUqe1Ick8r0SgDTJXJyn8bWruV49h/aZEU9Z /o7IgvO7AHW3n8IHhoGjfiFfe5eMlpUcvpUZy2UlSsBJwYZiQCs99JgrsWdsB2LzR32B sv+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=1C3KpaWAnC6bLx36qRvXMR+Laj8QYqMDjW3j9/6emQQ=; b=je3r8czhUEJgKqlCjhKQtOvSS+/qA0hZB+jcOQDlRncomZXpxaZAv53R/Oaz5k+phy W0494KK2owS3COr0+oxtkludzHHF7ZCV7nMGnlVj1N/nlm5wTQmEkf2d79uKHP2C+Gnl A1Rn9Wd2ZI+B13Mns0s/3IN+RI1VLXdunJmhV+3znTyw8veTLM2o0i+QbNRcjSj0V81u rdC11jgciib317E92whxL/hO/E6wDhxmqBXctBX/ot+gNvN81to/1tTVahzcda7mDqXz UQussKgDHjYWJ19YioSMO+83DukvWhwKnmJjKHaqwOlBG222ITgZ/QedolvJ8CuttoPE EyNA==
X-Gm-Message-State: APjAAAU5Fjvbj34aa8PzlVcbcOzKx8MQKexSbGR/YqMB/R4R3/8EyoxH zAIA9PcaTQAYeaFiC8COCZ6dJW180rg=
X-Google-Smtp-Source: APXvYqzLE7pfGGYss3MB7KyY/FGYw6xEYn8PSb7DDetGvRsPjyPAxcZ+EJS2q1/TDswA+sgG7LRfug==
X-Received: by 2002:aed:3e57:: with SMTP id m23mr50032004qtf.246.1558104948289; Fri, 17 May 2019 07:55:48 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id p37sm5950259qtj.90.2019.05.17.07.55.47 for <quic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 May 2019 07:55:47 -0700 (PDT)
Date: Fri, 17 May 2019 10:55:41 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: IETF QUIC WG <quic@ietf.org>
Subject: Re: HTTP/3 with strict priorities (PR #2700)
Message-ID: <20190517145540.GA13238@ubuntu-dmitri>
Mail-Followup-To: IETF QUIC WG <quic@ietf.org>
References: <20190515205451.GA32701@ubuntu-dmitri> <CAKcm_gMz=ENz_bKSAa6MOYA39w-+66em1xE=JSt7QoupaNLabA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAKcm_gMz=ENz_bKSAa6MOYA39w-+66em1xE=JSt7QoupaNLabA@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/mNbs205BBc1xk0p1SAYcIsV6EpQ>
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, 17 May 2019 14:56:10 -0000

On Wed, May 15, 2019 at 05:51:27PM -0400, Ian Swett wrote:
> > 1. What is a _strict priority_?
> >
> >     There is no definition of strict priority that I could find
> >     in the diff.  Do strict priorities work outside of the
> >     dependency tree?  For example, which stream has higher priority
> >     in the following figure?
> >
--- 8< --- 8< --- 8< ---
> 
> Strict priorities are only relative to other siblings under the same
> placeholder/root.  I'll clarify that.  Currently the text says "Higher
> priority elements have all available data sent before elements of lower
> priority."

I see, so this is two levels of prioritization, with weights (if present)
serving to determine how resources are allocated to streams that have the
same priority.  This feature is analogous to priority and concurrency in
Patrick Meenan's proposal. [1]

> > 3. What problem do all-or-nothing resources solve?
> >
> >     " When [weight is] absent, indicates the resource should be
> >     " delivered all at once or not at all.
> >
> >     This is new.  I don't believe I've seen it in other prioritization
> >     proposals.  Adding this dimension increases complexity.  What
> >     problem do these all-or-nothing resources solve?
> >
> 
> This is an effort to incorporate Patrick Meenan's Round Robin Sequential
> and Round Robin Interleaved proposal, as outlined on slide 49 here:
> https://github.com/HTTPWorkshop/workshop2019/blob/master/talks/pardue-jones-priorities.pdf
> or
> here: http3-prioritization-proposal
> <https://github.com/pmeenan/http3-prioritization-proposal/blob/master/README.md>
> 
> I'm sure Patrick could rewrite this text more clearly, and I think
> Patrick's explanation for the motivation is solid.

I could not find the "all at once or not at all" concept mentioned
in these documents, nor did I succeed in mapping the "not at all"
part to anything in Patrick's proposal.  Where can I find his
explanation for the motivation?

  - Dmitri.

1. https://github.com/pmeenan/http3-prioritization-proposal