IETF Logo Mail Archive

Re: [quicwg/base-drafts] Does InPersistentCongestion calculate a bogus value? (#2694)

MikkelFJ <notifications@github.com> Mon, 13 May 2019 16:30 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 8F73A120100 for <quic-issues@ietfa.amsl.com>; Mon, 13 May 2019 09:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.464
X-Spam-Level:
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: 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 K6gpC5iJFR1m for <quic-issues@ietfa.amsl.com>; Mon, 13 May 2019 09:30:55 -0700 (PDT)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14420120072 for <quic-issues@ietf.org>; Mon, 13 May 2019 09:30:55 -0700 (PDT)
Date: Mon, 13 May 2019 09:30:53 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557765053; bh=s11XZjtk2BGfBs9eEDcNNlyBCHD2DYutAWcdMuavuyc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RNCvdeC3DveD8gLAhzL4rOc1EYYlx+jtJnLS3bHdcYkXWgBpRCjSnsrru3mt5X16C iflxiGYio6GG0RFpn4nm+hyzJUlKilWaqcrZmEiEkL3tGJmN3M07zze99jvm/hC0XW s+wJoMfl58R5zKJDDJHdBJhGhzmLC8swoaBtcwTY=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2BF7ACNEB2B7YGJT5243HD3EVBNHHBU3XTPQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2694/491894322@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2694@github.com>
References: <quicwg/base-drafts/issues/2694@github.com>
Subject: Re: [quicwg/base-drafts] Does InPersistentCongestion calculate a bogus value? (#2694)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd99bbde1c43_26c43fd11a2cd960190295"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/a9WKyks8IrLbeMO6iZWR_OQFF4o>
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, 13 May 2019 16:30:57 -0000

I don't think you can assume integer math 1 second resolution here, if this is what you are suggesting.

Most would likely use floating point here, since that is simple and efficient. And for those who don't, computing in units of milliseconds or microseconds would make sense.

-- 
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/2694#issuecomment-491894322

v2.23.0 | Report a Bug | By Email