Re: [quicwg/base-drafts] Discussion in quic-recovery of delayed ack being 25ms does not seem to relate to anything (#3075)

Johannes Rudolph <notifications@github.com> Sat, 12 October 2019 12:33 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 A262312084F for <quic-issues@ietfa.amsl.com>; Sat, 12 Oct 2019 05:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 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_20=1.546, 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 qwGZTldle65S for <quic-issues@ietfa.amsl.com>; Sat, 12 Oct 2019 05:33:05 -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 C4F9212004C for <quic-issues@ietf.org>; Sat, 12 Oct 2019 05:33:04 -0700 (PDT)
Received: from github-lowworker-5825cd4.ac4-iad.github.net (github-lowworker-5825cd4.ac4-iad.github.net [10.52.22.68]) by smtp.github.com (Postfix) with ESMTP id AE75D96045B for <quic-issues@ietf.org>; Sat, 12 Oct 2019 05:33:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1570883583; bh=Ps2hWq2oAtMQ1uZxLKM5qFw6tcy3h3ZhQNYEanKm4ZM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZqHZaVkfIUVrh13q5KdzZlsdQttezwlD3J+2gUrgU4kfwwGuPtOlmRMGrU11cqyTy HiKGRL1FeE3Y1p6M73U4jcvNvQ+k6KbRixpyhTObhtPzh8AwQVJeEEcOvr1AzSimSY I7R0Lw6DCTBSgGw4Dmdn1xl1nyzOHTadgXKLI2gk=
Date: Sat, 12 Oct 2019 05:33:03 -0700
From: Johannes Rudolph <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5QDSK2ASHTYLYFVAN3V4EI7EVBNHHB34GMIM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3075/541320810@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3075@github.com>
References: <quicwg/base-drafts/issues/3075@github.com>
Subject: Re: [quicwg/base-drafts] Discussion in quic-recovery of delayed ack being 25ms does not seem to relate to anything (#3075)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5da1c7ff9f26f_55ca3ffd18acd960362052"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: jrudolph
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/j8qFldx5TCNNR_inMIfnW-CRX_8>
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, 12 Oct 2019 12:33:07 -0000

> I realized that the 25ms recommendation is in transport, so this is just out of place now.

Ah, I see, I remember I went looking for it in transport, but I think I looked for "delayed ack" and didn't come up with anything fitting. I've got no concrete suggestion how to resolve it but moving the notice to transport in some form would probably make sense.

-- 
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/3075#issuecomment-541320810