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

Martin Thomson <notifications@github.com> Fri, 03 August 2018 01:59 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 D49C7130E9F for <quic-issues@ietfa.amsl.com>; Thu, 2 Aug 2018 18:59:42 -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 OfBE6r4dglkz for <quic-issues@ietfa.amsl.com>; Thu, 2 Aug 2018 18:59:40 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7308130E60 for <quic-issues@ietf.org>; Thu, 2 Aug 2018 18:59:40 -0700 (PDT)
Date: Thu, 02 Aug 2018 18:59:39 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1533261579; bh=qF/sXJurkMjeCKbt++I224z/TIYLoyzxclenLiiUGss=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Cw2WlnxmbomYB6NQjw9CghPlz9pV2/0goYoyjlZ+puuQeMsAO7FuNJC++sU1E7Gph beEozs75mRvn9a7tBke1LF1WMXV/cPtgxTxPot6OFaCEnVrERCeWfQbzzUVrnvdmci QNp4xv2aiG8LMkaomnIjeBVE1Z/b0jXTK3atI43Y=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab80a840f114142b47aff45f7a84e6d40c3260394f92cf00000001177b790b92a169ce13b52edd@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/410121095@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_5b63b70b9568f_30a43fcff94be624146454"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/wSn3k7E0pBS82BpDCqGgqSfg35I>
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: Fri, 03 Aug 2018 01:59:43 -0000

This isn't a question of a particular construct; I'm more concerned about what advice we might give generally.  Ryan's advice is only really part of that (though it's pretty solid and pragmatic advice).

There are probably other things to say about what a sender might do that help.  For instance, if you think that something might be parsed as a single unit, then it's probably not a good idea to only send part of it.  Waiting until flow control credit is available - while it might risk a stall in the event that credits never arrive - might be a good idea.

It's also probably necessary to say something about inter-stream dependencies along the lines of: "If you have a dependency between the content of two streams, then you need to ensure that the dependent information is not sent until the information it depends on can be sent.  In particular, the necessary flow control credit needs to have been consumed."

-- 
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-410121095