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

Lucas Pardue <notifications@github.com> Wed, 16 January 2019 16:53 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 B1CFB12894E for <quic-issues@ietfa.amsl.com>; Wed, 16 Jan 2019 08:53:53 -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 Yik36L9jfPXm for <quic-issues@ietfa.amsl.com>; Wed, 16 Jan 2019 08:53:52 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 078151276D0 for <quic-issues@ietf.org>; Wed, 16 Jan 2019 08:53:52 -0800 (PST)
Date: Wed, 16 Jan 2019 08:53:51 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547657631; bh=GWYAtZxAns443ZLum+JSfyzslPgdCnsPPkpCm4BjTx8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Bmj5gacaxeeT18iWvQ5a/hoxqaVYxGy/vnFhmcglECHEjbuASGp6hqFM/iXERDOWG aXXb0YwjydK213yUVtW12zzaGnHTIlvNAFJ6Sq882Obu5Nw4SJDcxp1vEDaHKukn01 VU9QtUYfu5/QZ9htj0yMtEdoxbneJ5cUFh7C6qyQ=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab809b68864c7b57c666f11f7e24f1aedb1bc8502192cf000000011857239f92a169ce17d5d58e@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/454854127@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_5c3f619f46c8c_1e1a3ffd0e6d45c09548"; 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/CG9aC10Heb-0-T_sSfvO74Hcat0>
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:53:54 -0000

I'm happy to come up with a PR containing some proposals. 

I think we have some diversity in perspective. Coming from a HTTP/3-first position with a background in HTTP/2, my currency is the _header block_. I've been told it can be sent in HEADERS and PUSH_PROMISE, I don't need to be told how those frames are sent (i.e. what streams).

As someone unfamiliar with the specification, the instructions don't leap out. There is not one section in the TOC that mentions the term _instruction_. From my limited appreciation, I'd class the instructions as a primitive of header compression. But I accept that these are perhaps the QPACK data model, with primitives akin to built-in types. 

It still hasn't leapt out to me if the encoder and decoder stream exchange clear header blocks, or just a stream of instructions.

-- 
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-454854127