Re: [quicwg/base-drafts] HTTP/3 Zero-weighting (#2723)

Daan De Meyer <> Sat, 18 May 2019 11:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EBDAA120052 for <>; Sat, 18 May 2019 04:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3zR54PgvOpGf for <>; Sat, 18 May 2019 04:09:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AC005120075 for <>; Sat, 18 May 2019 04:09:26 -0700 (PDT)
Date: Sat, 18 May 2019 04:09:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558177765; bh=r0+q7/g6dwKQ78fT8wa2zlcibzq2sEMX+iAZYAYR2Ww=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QtbGPIGUSW+22w3Fezlry7hmi5wMRMRypFDziTlumn52Vz8IZLneMCkfouHqlgZxj VPYMXUjn3UaC6dY2U85oBnyS4GH8x+jajyXlQXxvmXzSkoI0ZszmlHR8MKJYV8U9Ik JlP2tA9FRN9FdiYkP+ftSTWGtJdu1Ho8F5l0RAio=
From: Daan De Meyer <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2723/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] HTTP/3 Zero-weighting (#2723)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cdfe7e5922fa_3def3f8696ccd95c89683f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DaanDeMeyer
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 18 May 2019 11:09:28 -0000

Sequentially sending both before and after non-zero weighted nodes could potentially be supported by hijacking weight 256 for sending sequentially after non-zero weighted nodes and using weight 0 for sending sequentially before non-zero weighted nodes.

I'd imagine there being scenario's where both are applicable. Before for when a high priority resource is discovered and after for when you don't really care about the order a resource is delivered in.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: