IETF Logo Mail Archive

Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432)

mirjak <notifications@github.com> Mon, 06 August 2018 09:31 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 B748F130EB4 for <quic-issues@ietfa.amsl.com>; Mon, 6 Aug 2018 02:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 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] 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 5X5YwhlfgzRs for <quic-issues@ietfa.amsl.com>; Mon, 6 Aug 2018 02:31:53 -0700 (PDT)
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 44521130E77 for <quic-issues@ietf.org>; Mon, 6 Aug 2018 02:31:53 -0700 (PDT)
Date: Mon, 06 Aug 2018 02:31:52 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1533547912; bh=npa5TA+b6C8ItzoBfp328yCm/lwmUM+7b6/c6xbnRC0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1wgFLZ5uL9syasgCxnH05CcBy1ab17cA2KCV7EH8UUCavK0uhleJaUHceWMqENMNU SuCSvcC/DcDflLRLV2kU7o8tORStTFbMMYrsvURrLkQ21IwGNk53YGoKjac5qBPZWu 3YKGqfd3lnoW7H3F+3SU57ZjsZ7njjRc0nIMKF6s=
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab9dacc8f64fb29b2a7e63c79d44fe0f645870536592cf00000001177fd78892a169ce13b52edd@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1432/410647505@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1432@github.com>
References: <quicwg/base-drafts/issues/1432@github.com>
Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b681588435e3_10d8f3ffa246be61812226c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
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/_tvY3dnTKKQPttXVxb4sAFxjlYM>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Mon, 06 Aug 2018 09:31:55 -0000

I guess it could be a good idea to give some more general advise (not only HTTP-specific) in the applicability statement. There is a section on "Use of Streams" and we could add another subsection to explain how this deadlock can happen and given some guidance inline with what @RyanAtGoogle and @martinthomson said. Anybody willing to send a PR directly or should I just open an ops-draft issue for now?

-- 
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/1432#issuecomment-410647505

v2.23.0 | Report a Bug | By Email