IETF Logo Mail Archive

Re: [quicwg/base-drafts] Unidirectional stream (some or) all the control things in HTTP/3 (#2678)

Lucas Pardue <notifications@github.com> Wed, 08 May 2019 16:31 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 B20CD120158 for <quic-issues@ietfa.amsl.com>; Wed, 8 May 2019 09:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.392
X-Spam-Level:
X-Spam-Status: No, score=-6.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, 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 RwLCuNILAi-a for <quic-issues@ietfa.amsl.com>; Wed, 8 May 2019 09:31:41 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 255F2120172 for <quic-issues@ietf.org>; Wed, 8 May 2019 09:31:41 -0700 (PDT)
Date: Wed, 08 May 2019 09:31:39 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557333100; bh=2rWlPwcRhlkhCMYseDJva3a/UoGuEgpix9WFUoEbmxI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rhWk9Z5d4Iat3kxY9f65ZbTAhfdc3tJ05TJIjAKlWZtMbhFOGQyv7ZA3c3UnSkSNM s3/TKZLklTyH+L2FkdyU03oXe2JBSCjnBOswGcp9OftQ07JvDpCcRqNH51FS3S+Pey zKFuyomJ++D+JAws5GQztSo5IUU3T0UPlAzxeUC0=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2DE55QAVVQLSWZNFF24A3OXEVBNHHBUVMWDQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2678/490557581@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2678@github.com>
References: <quicwg/base-drafts/issues/2678@github.com>
Subject: Re: [quicwg/base-drafts] Unidirectional stream (some or) all the control things in HTTP/3 (#2678)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd3046be57d4_583c3ff327ccd9682033e7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/WIynJnzTFAkE-b7pYF6rWPO8yf0>
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: Wed, 08 May 2019 16:31:43 -0000

> Note that this would make #2559 even more of a problem. What do you do without enough unidirectional stream ID space to send your GOAWAY, for example?

One mitigation is to get more explicit with how these "very important" streams are made. I.e. for the standard profile of QUIC we state that there is an absolute minimum number of streams and, more importantly, the peer's create them in a standard and deterministic way.

This backtracks a little, to how things were before unidirectional stream type, but it still allows extension streams to be deployed in a less coordinated way.


-- 
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/issues/2678#issuecomment-490557581

v2.23.0 | Report a Bug | By Email