IETF Logo Mail Archive

Re: [quicwg/base-drafts] QPACK: instructions and stream description is suboptimal (#2339)

afrind <notifications@github.com> Wed, 16 January 2019 16:35 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 6B6B0130E1C for <quic-issues@ietfa.amsl.com>; Wed, 16 Jan 2019 08:35:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.553
X-Spam-Level:
X-Spam-Status: No, score=-12.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 80Fyrsaxuigo for <quic-issues@ietfa.amsl.com>; Wed, 16 Jan 2019 08:35:43 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8277D12D4EC for <quic-issues@ietf.org>; Wed, 16 Jan 2019 08:35:43 -0800 (PST)
Date: Wed, 16 Jan 2019 08:35:42 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547656542; bh=QVBY9K5OfKMXrc2Un78SLIvnCVGQFedFlrhRdFZY0pM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=L7e+EqQzMCuEyINI6KsT7o0UhK+PmR8s6daqv08xDbdKlA4My5q5ViY5HMFxEyWEf d/n5AzJV0QCV/l8ICd0N1OohSc0VDr6CqIfO1M+kTlj3/sMkwRQ26x/a2wY2ufIPa0 WGfaMeO24TpUA+BIaJomFdHTDeGkWoKM/ucc2ga0=
From: afrind <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf87cda656bd133680942a858d357bde18fd1325c92cf0000000118571f5e92a169ce17d5d58e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2339/454847187@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2339@github.com>
References: <quicwg/base-drafts/issues/2339@github.com>
Subject: Re: [quicwg/base-drafts] QPACK: instructions and stream description is suboptimal (#2339)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c3f5d5e82e42_52e3fe400cd45b434896a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: afrind
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/dsYb4pPutSkaUy70orPJv9Efu2A>
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, 16 Jan 2019 16:35:45 -0000

The big editorial refactor intentionally reordered the sections: the goal was to describe concepts first and specific instructions second.

Regarding whether the encoder/decoder streams are required, there's a separate (design) issue open (#2100). 

Given that the instruction spaces are unique per stream type, and no instruction is allowed on more than one stream, I think it makes sense to keep the instructions organized by the stream on which they are used.  

I can clean up the ambiguous references to unidirectional streams to make it clear that we're talking about the QPACK control streams.

I'll give it another read through with your comments in mind and see what further improvements we can make.

-- 
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/2339#issuecomment-454847187

v2.23.0 | Report a Bug | By Email