Re: [quicwg/base-drafts] http deadlock with stream FIN choices (#1972)

Lucas Pardue <notifications@github.com> Tue, 06 November 2018 17:30 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 E9182130934 for <quic-issues@ietfa.amsl.com>; Tue, 6 Nov 2018 09:30:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, 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 qRyexwgfpB1j for <quic-issues@ietfa.amsl.com>; Tue, 6 Nov 2018 09:30:04 -0800 (PST)
Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8805A12F1AB for <quic-issues@ietf.org>; Tue, 6 Nov 2018 09:30:04 -0800 (PST)
Date: Tue, 06 Nov 2018 09:30:03 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1541525403; bh=WSastA4qVl3nikB40EnHnafKENedX8sPEVhvD5Nc0B0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=J9u6GHvqODm45ISQWQ5wS/Ei1hnKfTKcAJ3wE22NpihSRLiQMhGplUIiVHbtrjOEq gWO5lzZjcurHO5mYwUGGAzyQKivKorAwaZh9wXaW6fBm5/0dhjgeDFpgkj7eY5e6QS MODomHNXYKlzOqgX8hGNlWzkawPuplViG4VzhsqQ=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab06dc55b9aff21bc60d4adf0bd1f1e78e6b9ee2f392cf0000000117f9919b92a169ce1683c825@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1972/436338486@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1972@github.com>
References: <quicwg/base-drafts/issues/1972@github.com>
Subject: Re: [quicwg/base-drafts] http deadlock with stream FIN choices (#1972)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5be1cf9b87911_7c183fe9e86d45b81252c0"; 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/VucX0HRKeOh3vMYTFoeKCacTmbI>
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, 06 Nov 2018 17:30:06 -0000

OK that makes sense. As you point out in the 2nd comment @nibanks this isn't really a spec issue, this was a subtlety I missed when skimming.

As someone that doesn't do interop, raising issues specific to it (and not the core documents) is awfully confusing. Especially so in future when search engine crawlers bring up old discussions as new implementers jump on board to build HTTP/QUIC software.

-- 
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/1972#issuecomment-436338486