Re: [quicwg/base-drafts] Allow repeat ACK's (#1234)

MikkelFJ <notifications@github.com> Mon, 19 March 2018 13:00 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 E46D312778E for <quic-issues@ietfa.amsl.com>; Mon, 19 Mar 2018 06:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.606
X-Spam-Level:
X-Spam-Status: No, score=-0.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 NsgDZvpuA0TO for <quic-issues@ietfa.amsl.com>; Mon, 19 Mar 2018 06:00:25 -0700 (PDT)
Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEA8F12778D for <quic-issues@ietf.org>; Mon, 19 Mar 2018 06:00:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=zVJy8PZpWIyUm9U0ONdm6RTGa/Q=; b=uz0wrJ3xBQ8gHQa/ IbvpPuZ1t07yKQFKUbWMEmLGZdeSv+KOtl5sCyUQniHjfIhbN5VsgcWhISDWkABs OwBlKHlUKZn2bKEZX5YAElR4fotXFus+z53aw0yX3b1je+qXU0LgIdHWVQ0MlWWi GJFTry/twbhIcNMkRsc7dZ5gKVw=
Received: by filter0021p1las1.sendgrid.net with SMTP id filter0021p1las1-13405-5AAFB466-10 2018-03-19 13:00:22.338794287 +0000 UTC
Received: from smtp.github.com (out-2.smtp.github.com [192.30.252.193]) by ismtpd0048p1mdw1.sendgrid.net (SG) with ESMTP id Y3qF2TgJTsmbNYAiHx56oA for <quic-issues@ietf.org>; Mon, 19 Mar 2018 13:00:22.190 +0000 (UTC)
Date: Mon, 19 Mar 2018 13:00:22 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab99b42c40d4223ca03924ddf5b2720298edd6352f92cf0000000116c7766592a169ce1243d7d3@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1234/374203003@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1234@github.com>
References: <quicwg/base-drafts/issues/1234@github.com>
Subject: Re: [quicwg/base-drafts] Allow repeat ACK's (#1234)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5aafb465eee58_60b62ab5c18a0ed4607024"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1VITqoUOAiL8oGgqSuqIf0bQoZTDOnECoyXC w0Nh1oix1d805FBueSSyl+cCM8bEZUYAuEGPXoCg7VcOC5VfcbyBIgNaawUFVcwcAm/pRZHOjtk93O KXm540Xm2hvYJOillWogt1/UZ8goLMu+E36Akz5bZM5O9SVUwgdZ8alVlZCVd6PpU6JGgvfRISmzc+ E=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/2BDjwh7yrN0B3Qn9TGP--cpP5XA>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 19 Mar 2018 13:00:27 -0000

Does this hold for ultra low latency networks? The retransmission logic may not necessarily follow guidance, and why require tracking this. An ACK'might not be ACK'ed for quite a while anyway.

It is a lot simpler to state that an ACK frame should not transmit more than one RTT worth of packets, or what is deemed suitable for the current network conditions.

-- 
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/1234#issuecomment-374203003