Re: [quicwg/base-drafts] Tracking of header blocks for reset streams (#1371)
afrind <notifications@github.com> Tue, 22 May 2018 17:04 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 E9F9412778E for <quic-issues@ietfa.amsl.com>; Tue, 22 May 2018 10:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 Oh0vsk5SiqB9 for <quic-issues@ietfa.amsl.com>; Tue, 22 May 2018 10:04:42 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56F31127444 for <quic-issues@ietf.org>; Tue, 22 May 2018 10:04:42 -0700 (PDT)
Date: Tue, 22 May 2018 10:04:41 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527008681; bh=RodGbXxKQk0/A9EUI4g0gmzfX255W8r34xszS7W3wyQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RHoaJWhOx6+G5RWF+ec9OuF/zuq2X4WO2et1QH2sihlIeaHbO4+bxUACR5utZHkyr v1cx0OTsHMfrXaHWMo5F9773bHvBNIQc7j3t++tIPYy0bjnAKKLyZkn0JziDdd1XkN 7XnbhpZPiw+4LrCItcmc0iMWEw5wQCcbcn6nudtQ=
From: afrind <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd357e00a24e322583e415eaaf895672913c8310692cf00000001171c0fa992a169ce13638f00@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1371/391067065@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1371@github.com>
References: <quicwg/base-drafts/issues/1371@github.com>
Subject: Re: [quicwg/base-drafts] Tracking of header blocks for reset streams (#1371)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b044da923247_1d143f8bf902ef8014606f"; 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/rNh6vbpLUKO4Osg77CfajfjI7GU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 22 May 2018 17:04:44 -0000
Yes I raised this earlier (which @MikeBishop filed as #1176). That got closed by making the consequence of the race condition a stream error rather than a connection error, since the race is likely to be quite rare. eg: the encoder can reset all its state when it sends the RST_STREAM, rather than when it is acknowledged. I think when we added the setting for number of blocked streams we re-introduced the connection level error. I wasn't really thrilled with that solution but I'm not thrilled by adding an application level stream-reset-ack either. Assuming we have to do this, do you think this should be an HTTP frame sent on the control stream or a QPACK instruction sent on the decoder stream? -- 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/1371#issuecomment-391067065
- Re: [quicwg/base-drafts] Tracking of header block… afrind
- Re: [quicwg/base-drafts] Tracking of header block… afrind
- [quicwg/base-drafts] Tracking of header blocks fo… Martin Thomson
- Re: [quicwg/base-drafts] Tracking of header block… afrind
- Re: [quicwg/base-drafts] Tracking of header block… Mike Bishop
- Re: [quicwg/base-drafts] Tracking of header block… Martin Thomson
- Re: [quicwg/base-drafts] Tracking of header block… Mike Bishop
- Re: [quicwg/base-drafts] Tracking of header block… ianswett