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

Praveen Balasubramanian <notifications@github.com> Mon, 15 April 2019 15:56 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 ABF0B12039A for <quic-issues@ietfa.amsl.com>; Mon, 15 Apr 2019 08:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Level:
X-Spam-Status: No, score=-6.383 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_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 PtBEwlzXGN1i for <quic-issues@ietfa.amsl.com>; Mon, 15 Apr 2019 08:56:57 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24353120397 for <quic-issues@ietf.org>; Mon, 15 Apr 2019 08:56:57 -0700 (PDT)
Date: Mon, 15 Apr 2019 08:56:56 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1555343816; bh=WjGiVM/gXKDtpVa2hMkiBzQ4sW7p8hDYJ/x+ZUtjaeg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hA/cXGtn2dvR5t0ThemjdHRtnZT47BvggoOfw1JyXk26Joy9JOVtgKdiBJiZ1xQpZ DSWk8cubBO4G2zehg6s7QZCFiMGTKw2ltc4L9NEoD/ZjFz4fo315iqRnQvWqD7Nr4F RnbY8mWPq/3maHkdCr6AjZ8wy9oLtpM5OAIVyQUw=
From: Praveen Balasubramanian <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5bc1efc8e331765fdf0f20b7cb450aedc3c42f7592cebac1dc4892a169ce175240ec@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/483312095@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2186@github.com>
References: <quicwg/base-drafts/issues/2186@github.com>
Subject: Re: [quicwg/base-drafts] Discuss considerations for max_ack_delay (#2186)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cb4a9c8bf3f_366d3f9b0bad45b82758f4"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: pravb
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/8gHjgg7YibVYM57k419lGlhnV8w>
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: Mon, 15 Apr 2019 15:56:59 -0000

What about scheuler delays? I've been thinking about max_ack_delay and I think we need more than just one timer tick here since its supposed to be the worst case. If we get this wrong then we will have lot of unnecessary firing of the TLP timer when only the tail packet is due. 

-- 
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#issuecomment-483312095