IETF Logo Mail Archive

Re: [quicwg/base-drafts] Add pacing note to flow control and other edits (#3301)

Jana Iyengar <notifications@github.com> Sat, 14 December 2019 08:09 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 B782312013F for <quic-issues@ietfa.amsl.com>; Sat, 14 Dec 2019 00:09:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
X-Spam-Status: No, score=-6.596 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, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 olh_iU2MFyom for <quic-issues@ietfa.amsl.com>; Sat, 14 Dec 2019 00:09:10 -0800 (PST)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D88F120086 for <quic-issues@ietf.org>; Sat, 14 Dec 2019 00:09:10 -0800 (PST)
Received: from github-lowworker-3a0df0f.ac4-iad.github.net (github-lowworker-3a0df0f.ac4-iad.github.net [10.52.25.92]) by smtp.github.com (Postfix) with ESMTP id 6DD898C0027 for <quic-issues@ietf.org>; Sat, 14 Dec 2019 00:09:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1576310949; bh=5+KqJ61k5jidJ/+44/hNBVtNfzWcDskFJDkTDsgSDwU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iZrAS6abnVkkyYTj2K4IBibo3cvfwdrsyxTWkOCGzBak0wSuxcNaTRfEriy6pUUoW SwB8lvswYrzuocS20rFVtE6RI8SCGfOvM0ZiqdH4OoV1TSdbr6ZNbg4DjfhDo4wDik 4H/yt+HxdbeuMpPb8BAV1un/trkP3xFIGVrCEYxA=
Date: Sat, 14 Dec 2019 00:09:09 -0800
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7FMDL5DMQHGWS7ND54AHFSLEVBNHHCADX3MM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3301/c565694181@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3301@github.com>
References: <quicwg/base-drafts/pull/3301@github.com>
Subject: Re: [quicwg/base-drafts] Add pacing note to flow control and other edits (#3301)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5df498a55e0f1_5c693fb396ccd95c15069d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/KF0yAAR-4knjQdGCVP0Q8yR25O4>
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: Sat, 14 Dec 2019 08:09:12 -0000

Yeah I was wondering that too.  We do talk about application limited in the
recovery doc, so maybe that's the place to clarify this. I'll see (after
the weekend) if it makes sense to add anything there.

On Fri, Dec 13, 2019, 8:15 PM Marten Seemann <notifications@github.com>
wrote:

> Is this the right place to discuss pacing? In my mind, we’re talking about
> different layers here. Bursty sending could happen due to many reasons,
> only one of them is due to increased flow control credit.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/pull/3301?email_source=notifications&email_token=ACUOBVAKHV35WISVUFEYPJTQYRMXBA5CNFSM4J2YHBAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG3ZVWI#issuecomment-565680857>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACUOBVHIJVMTCFUFMKF75NDQYRMXBANCNFSM4J2YHBAA>
> .
>


-- 
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/pull/3301#issuecomment-565694181

v2.23.0 | Report a Bug | By Email