Re: [quicwg/base-drafts] Add text on flow control deadlocks (Issue #5001)
Lucas Pardue <notifications@github.com> Wed, 26 April 2023 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 224C3C151B1E for <quic-issues@ietfa.amsl.com>; Tue, 25 Apr 2023 18:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.77
X-Spam-Level:
X-Spam-Status: No, score=-3.77 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p6Bsyi36Mhub for <quic-issues@ietfa.amsl.com>; Tue, 25 Apr 2023 18:28:34 -0700 (PDT)
Received: from out-17.smtp.github.com (out-17.smtp.github.com [192.30.252.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BC21C15198A for <quic-issues@ietf.org>; Tue, 25 Apr 2023 18:28:34 -0700 (PDT)
Received: from github-lowworker-c85ce22.va3-iad.github.net (github-lowworker-c85ce22.va3-iad.github.net [10.48.114.58]) by smtp.github.com (Postfix) with ESMTP id 80DE65C009B for <quic-issues@ietf.org>; Tue, 25 Apr 2023 18:28:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2023; t=1682472513; bh=HH+zCcjCJaClzlvlx0x2bhbaARhMJYCwMfQoVsFIU0k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k4qjlWLwEeSOPhG19qLqUQoZU1Pc+faNCoQY+eLvaMcL87qi3a5P6TQNPA01XOpav 88kg5cVg4+qjnNhayDJTVtdlMl3QGMARMQOFesDF7JZ44yQCx0dpBcXzVdxyxe58h5 3Wz29kd/SlXubr7SmNcHuKzvUe/jOByETKaSUD+s=
Date: Tue, 25 Apr 2023 18:28:33 -0700
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5SJIVJ23OO2V5AGZ6CKW7NDEVBNHHGIYDDEU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/5001/1522632456@github.com>
In-Reply-To: <quicwg/base-drafts/issues/5001@github.com>
References: <quicwg/base-drafts/issues/5001@github.com>
Subject: Re: [quicwg/base-drafts] Add text on flow control deadlocks (Issue #5001)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_64487e4174096_1814c9a4894240"; 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/QYWGvE30dmONgu5-Av7lgoYlVb0>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 26 Apr 2023 01:28:38 -0000
WebTransport seems like the prime target audience for the applicability draft. [Section 4.4](https://www.rfc-editor.org/rfc/rfc9308.html#name-flow-control-deadlocks) is titled "Flow Control Deadlocks" and is ~500 words. So a few of questions: 1. Is the text in RFC 9308 sufficiently descriptive? (i.e., does it address the OP issue) 2. We could consider porting the text or referencing it in rfc900-bis work. However, if its current content and location is fine, can we close this? 3. There may be some interplay between streams and datagrams (not flow controlled, but competition for congestion control, which can impact flow control). Would that be in scope of this issue, or something to track separate? -- Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/issues/5001#issuecomment-1522632456 You are receiving this because you are subscribed to this thread. Message ID: <quicwg/base-drafts/issues/5001/1522632456@github.com>
- [quicwg/base-drafts] Add text on flow control dea… Martin Thomson
- Re: [quicwg/base-drafts] Add text on flow control… Martin Thomson
- Re: [quicwg/base-drafts] Add text on flow control… Lucas Pardue
- Re: [quicwg/base-drafts] Add text on flow control… Lucas Pardue