IETF Logo Mail Archive

[quicwg/base-drafts] Discuss considerations for max_ack_delay (#2186)

janaiyengar <notifications@github.com> Fri, 14 December 2018 20:22 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 67D23130E3C for <quic-issues@ietfa.amsl.com>; Fri, 14 Dec 2018 12:22:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.842
X-Spam-Level:
X-Spam-Status: No, score=-7.842 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 L79TAVP2pbPi for <quic-issues@ietfa.amsl.com>; Fri, 14 Dec 2018 12:22:19 -0800 (PST)
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 59B29130E3F for <quic-issues@ietf.org>; Fri, 14 Dec 2018 12:22:19 -0800 (PST)
Date: Fri, 14 Dec 2018 12:22:18 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544818938; bh=uIVv7YZDilm29VUjdzE8zJV6pj5PWDacXrBd5lq6gZI=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=y6zqWz/ZI6jN1kdU9dX99c24/b/MSoejGBSRA3tu3gW88HFc5dw9TDoSmJCNkSNgE yXqr8xJmJv1DoYfHwUR5kyB+3yXRP/7BEoWPKmRXHqOIpQlodpeBoePSKR5NRuLTju qxvb2eTWPa8xPxPxyAw7UvCCF0J5EyGp/XiN/kZQ=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6d490e8ec2f9392478015cbba9acdcc3bbf8f0bc92cf00000001182bd2fa92a169ce175240ec@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2186@github.com>
Subject: [quicwg/base-drafts] Discuss considerations for max_ack_delay (#2186)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c1410fa5b105_517a3ff1d42d45b41204de"; 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/BIP3iqisgZ3YRfOAJYRbnUSTqw4>
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: Fri, 14 Dec 2018 20:22:21 -0000

Conversations with implementers suggests that it might be useful to clearly discuss considerations for how a receiver might choose max_ack_delay. Specifically, the receiver should  communicate worst case delay, since communicating something smaller can result in spurious retransmissions. Some guidance should be added.


-- 
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/2186

v2.23.0 | Report a Bug | By Email