IETF Logo Mail Archive

Re: [quicwg/base-drafts] compensation of ack_delay is fragile against errors (#2060)

janaiyengar <notifications@github.com> Thu, 29 November 2018 03:50 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 BA274130DDD for <quic-issues@ietfa.amsl.com>; Wed, 28 Nov 2018 19:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 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_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 yCucJvNW2bWP for <quic-issues@ietfa.amsl.com>; Wed, 28 Nov 2018 19:50:56 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B11812F1A5 for <quic-issues@ietf.org>; Wed, 28 Nov 2018 19:50:56 -0800 (PST)
Date: Wed, 28 Nov 2018 19:50:55 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543463455; bh=xueuzo3qtT2zY87nhWnGkUJ9PWdWnjJd5dmDxsAvC5A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=inOF2R5y1aSsqQvhnnOtdIaLWcz5WCp8FJCDRdvPAYM/Lz10t+DE5y9ktIuBmD3ck 6amZLD+gsXMYR/IEswY66l32SP5r5F5oTv4EnJC+pVQG2JLOrVT+02hQfutNEJDwj9 sES0Xi4iDSxWgoBQYAnek1ru59/PD5D0MBmtcIkU=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abdb2afcb3ea8aa4f21b5b3ed94fddcee8311c7e4992cf000000011817241f92a169ce16f4226e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2060/442696945@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2060@github.com>
References: <quicwg/base-drafts/issues/2060@github.com>
Subject: Re: [quicwg/base-drafts] compensation of ack_delay is fragile against errors (#2060)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bff621f69b4d_51953fd6ab2d45bc2029da"; 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/zrVnmSqHMfQxym1ZA5ihK3pPNlk>
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: Thu, 29 Nov 2018 03:50:58 -0000

If folks feel strongly about this, I'm fine with it. I don't think it makes
sense, but it does seem like I'm in the minority, and if you all think it
makes sense, that's what we'll do.

On Wed, Nov 28, 2018, 7:47 PM Jana Iyengar <jri.ietf@gmail.com wrote:

> In general, yes, but in this case, I don't see a reason to use any part of
> ack_delay when we know it's incorrect.
>
> On Wed, Nov 28, 2018, 7:44 PM Martin Thomson <notifications@github.com
> wrote:
>
>> I thought that we had accepted the costs of integrating ack_delay in
>> calculations (it might be wrong) against the benefits (we get better
>> accounting in the majority of the cases where it is set accurately).
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly, view it on GitHub
>> <https://github.com/quicwg/base-drafts/issues/2060#issuecomment-442695905>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/AKjg1Oht0XwTGilWqn_4uqKhZpD4eg1Lks5uz1gCgaJpZM4Y22J5>
>> .
>>
>


-- 
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/2060#issuecomment-442696945

v2.27.6 | Report a Bug | By Email | System Status