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

Kazuho Oku <notifications@github.com> Tue, 12 June 2018 01:28 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 BC7ED130DCC for <quic-issues@ietfa.amsl.com>; Mon, 11 Jun 2018 18:28:37 -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 I5wKvCN2tRus for <quic-issues@ietfa.amsl.com>; Mon, 11 Jun 2018 18:28:34 -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 C322C130EB2 for <quic-issues@ietf.org>; Mon, 11 Jun 2018 18:28:34 -0700 (PDT)
Date: Mon, 11 Jun 2018 18:28:33 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528766913; bh=4H0bRhCrPxFF0PvQc0PCRBiVZFS6TV/dFVuw+Tft/pM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Vnohbiw3yCW/IbH1/gwLq1czK00PxlWQFLw3TUT5ShtjhO/kKdad0mtM0ejB79QDw q2cpBN+xQV5lXzPiVVWStFeEzSBuz+7iSU8t40s37nHtHWj29nkN/XEJx2oT/JGj3K 3L600hwxyjoNAlP5MLn7ZbepeefvalpkbU9Guby0=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf8e0f349130b3abfcd44ac04b0d50c7e8904434792cf000000011736e3c192a169ce13b52edd@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/396436567@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_5b1f21c1dec19_ea333fa0d892ef88284164"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/3dgjs4vX9vE7V54S8AcR8S_weSw>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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, 12 Jun 2018 01:28:38 -0000

@MikeBishop Thank you for the clarification. I can understand the fact that we want to have a way to signal back-pressure when more than one stream is involved.

OTOH, as we all agree, using back-pressure has the danger of seeing a deadlock. It makes sense to have the implications being clarified in the documents.

And I would like to second @martinthomson's argument that the issue is not related to length-prefixes. Consider using HTTP/1 on QUIC. It makes perfect sense for an application to keep the response headers in the receive buffer until CR-LF-CR-LF arrives.

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