Re: [quicwg/base-drafts] max_ack_delay should be in us, not ms (#3363)

ianswett <> Mon, 20 January 2020 19:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EA73712094B for <>; Mon, 20 Jan 2020 11:18:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.454
X-Spam-Status: No, score=-1.454 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 t7gpExolwbyv for <>; Mon, 20 Jan 2020 11:18:33 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B60FD120958 for <>; Mon, 20 Jan 2020 11:18:33 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id D507A280061 for <>; Mon, 20 Jan 2020 11:18:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1579547912; bh=JGva9+Jb08UpNve5dY8KRoa3hxP6Ozs5tn+sw1FP7Cs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ogV/yJtLM+cyn/o2jAvDaDE1sZVePq9XPXUC4CV+oBaxzcU18UX16Ze+keOtEHNMc P5qZNC7n/AmZLmiqQ2E/WIpLq0z49aAUF+WtnlUj3ohT6v2/d3pDFvkZT3CcfabJ7G i6zdAp4tVdaycPyP7EiCLt3siO+KNYkJ7LU0kEko=
Date: Mon, 20 Jan 2020 11:18:32 -0800
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3363/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] max_ack_delay should be in us, not ms (#3363)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e25fd08c5681_3cf73f87b68cd96c70235"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: Mon, 20 Jan 2020 19:18:38 -0000

Yes, I agree it's a design issue.  

I confirmed with the TCP team at Google and they agreed microseconds was a better choice than millis.

I will say that we can punt this and make the extension Jana and I are working on specify it in us, but that seems a bit hacky to me given we haven't yet shipped QUIC v1.

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