Re: [quicwg/base-drafts] Negotiate use of timestamps in ACK frame (#774)

ianswett <notifications@github.com> Mon, 18 September 2017 16:14 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 67FCB132D4E for <quic-issues@ietfa.amsl.com>; Mon, 18 Sep 2017 09:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level:
X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 xrie5EhvopE3 for <quic-issues@ietfa.amsl.com>; Mon, 18 Sep 2017 09:14:34 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11A90120720 for <quic-issues@ietf.org>; Mon, 18 Sep 2017 09:14:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=rIftCO+Z4w/NJasc3VJKJgX+scU=; b=VAXhXiXcnthlHe8Q 11v2+h9ChvT0K+OIwXJESsqV3mXwdq/0R3gXPdNmfvj1xYZJ/FGtHFdlAkHo3Uki bADPEfK9x92US72z0NOon2ViFO3axlsucDiep1XXMmevKxC7cO+dQ0VbRdKwqTQ0 UwkI6i0AXSGZ/T60Cm+DKJFKoVk=
Received: by filter1158p1mdw1.sendgrid.net with SMTP id filter1158p1mdw1-19523-59BFF0E9-19 2017-09-18 16:14:33.235504026 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id 1jBrfXUhQiG_AQKYaxWp0w for <quic-issues@ietf.org>; Mon, 18 Sep 2017 16:14:33.173 +0000 (UTC)
Date: Mon, 18 Sep 2017 16:14:33 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd13f800c2b14bfbf4f8acac4cc20fc7a39bd465e92cf0000000115d7b2e892a169ce0f547812@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/774/330274043@github.com>
In-Reply-To: <quicwg/base-drafts/issues/774@github.com>
References: <quicwg/base-drafts/issues/774@github.com>
Subject: Re: [quicwg/base-drafts] Negotiate use of timestamps in ACK frame (#774)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59bff0e8d2ab3_17e33fb31104cf28719af"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2aQnyEfZhnMnmKq4cGm/BUjCuD2irpZhj+hy oIxn5TjKl99Yrmo0JAAzPJOYhh3RonO0wvbNycbJBLpwllZEg/u8cHCiwKOxSPQBczHAfCls5Qet6c a9LrDwq+4CgOz6Ei/nsyuJRhFhJyIj4X1YHYXyv7ZYeGPbrvjQK0Xhr6LVB26tc51hmbGrrbWSWLKT s=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/uQrMZlqLSxT3Xz8Wl3fvkYVlN14>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 18 Sep 2017 16:14:35 -0000

Negotiating timestamps sounds good to me, though I'd hope we can agree on one format for most use cases.

I can see the use case for requesting only 1 timestamp per ack frame vs requesting one timestamp for every newly acked packet.

I would really like to keep timestamps(and ECN when it's added) as parts of the ack frame because it's much more challenging to implement congestion control if the information arrives in sequence(even in different packets) instead of at the same time.  Timestamps in particular are closely related to the acked packets, and given we'll likely want to support multiple ack frames in a single packet in the future, having multiple ack frames and multiple timestamp frames would become really complex.

It does make acks 'more complex' but the overall complexity is lower.

Timestamps are already forbidden from unprotected ack frames, so it should be simple enough to negotiate timestamps and only use them post-handshake.

-- 
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/774#issuecomment-330274043