Re: [quicwg/base-drafts] Restrict delayed ACKs (#1662)
mirjak <notifications@github.com> Wed, 15 August 2018 08:55 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 2BCD5130F17 for <quic-issues@ietfa.amsl.com>; Wed, 15 Aug 2018 01:55:24 -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 kQvbCFUIA1kp for <quic-issues@ietfa.amsl.com>; Wed, 15 Aug 2018 01:55:22 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E3C9130E2D for <quic-issues@ietf.org>; Wed, 15 Aug 2018 01:55:22 -0700 (PDT)
Date: Wed, 15 Aug 2018 01:55:20 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1534323320; bh=IRrqe+wfkLWYTcJf0JTlVtQ21SPH2dbd6BMktev0fI4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kucWCksqdpqJC2+spMpatW3IOqv8lAXm2ErU3v7P8gxGFqFwnSWvrFXLpq6bzV9dM eZZ7wS8VPzs0yb86FQvzZ4bdiRGmlhK+DCAugN/S/+5GBKKtXIGRxqozWWjw2DbXBj 3syhXojIa1oaCfxKWiCWqDBNmoHMTfXfVNLO8dHE=
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba31f9b0c79015255b40aeada660e67415abe5cc292cf00000001178bac7892a169ce14e3809a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1662/413136116@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1662@github.com>
References: <quicwg/base-drafts/issues/1662@github.com>
Subject: Re: [quicwg/base-drafts] Restrict delayed ACKs (#1662)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b73ea78ac80d_29213fd9690be61830159e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
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/S_nVui-b2sfSBSAckVaz-lJ8RHQ>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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, 15 Aug 2018 08:55:24 -0000
@ianswett I would like to see that the transport draft sets the normative boundaries while the recovery draft specifies the specifics. This way both drafts are less dependent and could be easier revised in future separately. @martinthomson I would put recommended numbers in the recovery draft but we can try to put lower and upper boundaries in the transport draft. I actually think something like "SHOULD at least send one ACK per RTT" would be good but that might be hard to implement. I think we can easily agree on an upper bound for the delay timer. I guess we can either go with 0.5 seconds as well or even something lower. -- 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/1662#issuecomment-413136116
- [quicwg/base-drafts] Restrict delayed ACKs (#1662) mirjak
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… ianswett
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… Martin Thomson
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… mirjak
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… ianswett
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… mirjak
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… ianswett
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… mirjak
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… ianswett
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… mirjak
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… mirjak
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… ianswett
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… mirjak
- Re: [quicwg/base-drafts] Restrict delayed ACKs (#… ianswett