Re: [quicwg/base-drafts] Allow not creating QPACK codec streams (#2529)

Alessandro Ghedini <notifications@github.com> Tue, 02 April 2019 21:36 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 9780B120321 for <quic-issues@ietfa.amsl.com>; Tue, 2 Apr 2019 14:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Level:
X-Spam-Status: No, score=-3.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 c1tkoBBXrAdQ for <quic-issues@ietfa.amsl.com>; Tue, 2 Apr 2019 14:36:16 -0700 (PDT)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B00A12030B for <quic-issues@ietf.org>; Tue, 2 Apr 2019 14:36:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Azml4uhph9vfWOcbjS5g82By29M=; b=OalslhFrwAccT9aT SickWSSWdQxAZ/JauOScAR7HKtR0dO51PUy9WKkvDcb0RZxJcrjgsdDwhpqcmbAW tTOnb8Mr3DC0N1OX/Bm+0B2aquuQ57G59lgIK4w/P+G+gEsvBVbB1JBDoekQOKtg Zfx1vXRVPuah6VL7VRVa0W92HBg=
Received: by filter0559p1iad2.sendgrid.net with SMTP id filter0559p1iad2-21025-5CA3D5CE-2C 2019-04-02 21:36:14.946717637 +0000 UTC m=+1560941.574466488
Received: from github-lowworker-61c4d48.cp1-iad.github.net (unknown [192.30.252.42]) by ismtpd0012p1iad1.sendgrid.net (SG) with ESMTP id SYhN2KzeTeeP7cqIT4aBVA for <quic-issues@ietf.org>; Tue, 02 Apr 2019 21:36:14.877 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-61c4d48.cp1-iad.github.net (Postfix) with ESMTP id D42A51A0005 for <quic-issues@ietf.org>; Tue, 2 Apr 2019 14:36:14 -0700 (PDT)
Date: Tue, 02 Apr 2019 21:36:14 +0000
From: Alessandro Ghedini <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abdb16c53f6f39ebfed207476813c33cba4530a8ea92cf0000000118bb97ce92a169ce1931c3e6@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2529/c479213967@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2529@github.com>
References: <quicwg/base-drafts/pull/2529@github.com>
Subject: Re: [quicwg/base-drafts] Allow not creating QPACK codec streams (#2529)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ca3d5ced2af3_4f373f91b66d45c030372a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ghedo
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0G9pM0WZXma3N+J4PVTFawbvMUSbTZZ0m+nv vTfXZUXgTT+/mxdJyHQQCe+BouVvpNgk2SY9Wm9QZ6QaDuaPvSqTGOZOunv+3YExIO98YAIVys8nRd Z1DWhH5VtpLc8mb9YWKDLhOlTY3J01iVYdHJR4PCFE1Y/sSAF2D0XPra16MHnf1YP/XkVBP/OtxFnE 8=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/5bnYrJzW-rECu9_n2ZQaISp5-CE>
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: Tue, 02 Apr 2019 21:36:19 -0000

I clarified the "An endpoint MAY avoid creating its own encoder stream" part to be more permissive (which was the intention from the beginning, it was just worded wrong).

Things that might need chaning from the above discussions:
1. Should we be explicit about decoder stream creation delay as suggested by @kazuho? I don't think there's anything preventing that right now though.
2. Regarding the "An endpoint MUST allow its peer to create both encoder and decoder streams", the HTTP draft currently says that "Both clients and servers SHOULD send a value of three or greater for the QUIC transport parameter initial_max_uni_streams" but it doesn't talk about `MAX_STREAMS`, so I guess this would be adding a new restriction. I seem to remember that was the consensus for the discussion in Tokyo, but I may be remembering wrong. Thoughts?

-- 
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/2529#issuecomment-479213967