IETF Logo Mail Archive

Re: [quicwg/base-drafts] HTTP/3 with strict priorities (#2700)

Patrick Meenan <notifications@github.com> Thu, 16 May 2019 15:29 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAED8120176 for <quic-issues@ietfa.amsl.com>; Thu, 16 May 2019 08:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.464
X-Spam-Level:
X-Spam-Status: No, score=-6.464 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 nWII-BF9z2Z9 for <quic-issues@ietfa.amsl.com>; Thu, 16 May 2019 08:29:12 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE7DD120175 for <quic-issues@ietf.org>; Thu, 16 May 2019 08:29:11 -0700 (PDT)
Date: Thu, 16 May 2019 08:29:10 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558020550; bh=ujdeCGf1HaQEW/xEJbivFZI96q5NDyE928lsw8LvnfU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jSn18nVfoOJ6xV3b9sgjmxwYUpJAeRho+AIli4TlGpgJeUf+swBfTeKqxJ/BzLVAg 9GMDyGLCOlljCaWHE2zp+uSH2c7OPJ3COvXNJFniPWSvBdweRUqYbAI45RvHUTFvpL IxgBy42+vq9nUuwJrvaHCAJYjE1iN+xYLqsjm100=
From: Patrick Meenan <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK66PRREYH3ALMHG6WV25K2ENEVBNHHBU6PCKA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2700/c493116073@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2700@github.com>
References: <quicwg/base-drafts/pull/2700@github.com>
Subject: Re: [quicwg/base-drafts] HTTP/3 with strict priorities (#2700)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cdd81c6ae251_7d5f3f7ec88cd9684899d8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: pmeenan
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/m9BWHMXLM-WtvWRKoEJunW2p0oI>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2019 15:29:14 -0000

I'll read through the proposal in a minute but to answer the "interrupt delivery" question, the expectation across the board is yes, lower priority streams will get interrupted by higher priority streams as soon as data for the higher priority stream is available (I'd actually argue that it's critical to be able to interrupt).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2700#issuecomment-493116073

v2.23.0 | Report a Bug | By Email