Re: [quicwg/base-drafts] create codec streams only when necessary (#2090)

Luca Niccolini <notifications@github.com> Wed, 19 December 2018 09:37 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 30BCB130DEF for <quic-issues@ietfa.amsl.com>; Wed, 19 Dec 2018 01:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.065
X-Spam-Level:
X-Spam-Status: No, score=-8.065 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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 mgc0xAzEdpOP for <quic-issues@ietfa.amsl.com>; Wed, 19 Dec 2018 01:37:05 -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 656B612F1A5 for <quic-issues@ietf.org>; Wed, 19 Dec 2018 01:37:05 -0800 (PST)
Date: Wed, 19 Dec 2018 01:37:04 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545212224; bh=ETiB1B7TFUYRG+KBktpq9Sts7wZ8EsYl/ejvG5T8SoA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FmoYZruscRedq32DUeDK6Lw1OwZuoqB0x7LbGHgJCF7pI9C3nqLU1uYSRRind3Y3+ M8Im0g88a0A/uYxtTCc/2EHbm5/7CSI/lR3BeqFox9FbUjyT3N4Ioeeh6sknae5f9y KwDqWuYiYJxqU/5TM1sdY9qGLWn8h87OOkkg6Sao=
From: Luca Niccolini <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab3d2e464d83c415bd0e40dc30b92098a22616651e92cf000000011831d34092a169ce170ba08e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2090/c448530612@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2090@github.com>
References: <quicwg/base-drafts/pull/2090@github.com>
Subject: Re: [quicwg/base-drafts] create codec streams only when necessary (#2090)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c1a114035739_f0d3fd8a92d45bc842b9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: lnicco
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/_K0p1P5wlcOnkFWtbg-cnyxZ0QA>
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, 19 Dec 2018 09:37:07 -0000

@dtikhonov yes with the current text, resetting any control stream is illegal. 
However given that we are discussing about making qpack streams kind of special, we _could_ allow resetting them. And that is what I proposed in my first comment.

> Could we instead relax the constraint that qpack streams (being control streams) cannot be closed, and allow an endpoint that doesn’t want to do qpack to not open its control streams and to immediately reset (with a specific error code, yeah I know YAEC) the peer initiated qpack streams?

My original point about the complexity of implementation for little benefit seems to be same that others have, and leaving aside concurrency and implementation specific concerns (which I don't deny exists in our code, but they are easily fixed) my point was more general as I feel like we are trying to bake into the protocol an optimization that in my opinion is better handled in the implementation of the memory constrained devices and we should just make it possible, rather than adding more constraints to the common case. So generally speaking I feel more comfortable relaxing constraints rather than tightening them, if possible and if that does not pose a threat.

-- 
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/2090#issuecomment-448530612