Re: [quicwg/base-drafts] Remove ack_delay_exponent TP (#2670)

MikkelFJ <> Thu, 09 May 2019 17:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A65371200E5 for <>; Thu, 9 May 2019 10:18:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.464
X-Spam-Status: No, score=-1.464 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xWgyv_R1sAZ1 for <>; Thu, 9 May 2019 10:18:28 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A1564120141 for <>; Thu, 9 May 2019 10:18:28 -0700 (PDT)
Date: Thu, 09 May 2019 10:18:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1557422307; bh=H+zXqskDcZk7vkPY1py+nBTkrbDmBx3HnGthES6nVPY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GCvBK+50OT6utXYVTrTooZ3bTa7HEkCbRu7g2OHR88SybB1l9HRlYOSo0NXB+Bo6r N1KeVbQSe+7SSrQx/g9huogyCgQefq2OIXiT6eti4XbNB2b2AyuSywQlIjJ/Cjy5qR 2vBJ43EwPHU98CtZoP2Vhn5WqIHRqH439I1P0ecc=
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2670/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Remove ack_delay_exponent TP (#2670)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd460e3c110e_370e3fb96a2cd9647557a5"; 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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 May 2019 17:18:31 -0000

not really, because except for rare RTOS systems used in ABS breaking systems and such, there is no such thing as a 1ms granularity. It may be that you best resolution is 1ms, but you might wake up 2500ms later after disk swap is done, or at half the expected sleep time because of some Unix signal and you don't care to rewait after that, or just general noise of kernel processes, interrupts, TLB misses, etc. Of course, the smaller the RTT the more critical this gets. For 25ms the chance of staying within a few percentage reasonable.

I still think the float16 approach is better. It takes all the guessing out be introducing an exponent per timestamp, and it can be decoded in a few nanoseconds.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: