Re: [quicwg/base-drafts] Does a timestamp for a packet implicity ACK it (#698)
martinduke <notifications@github.com> Wed, 06 September 2017 19:13 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 2B4171329AB for <quic-issues@ietfa.amsl.com>; Wed, 6 Sep 2017 12:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.799
X-Spam-Level:
X-Spam-Status: No, score=-4.799 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_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, 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 q6O3P8jL29XY for <quic-issues@ietfa.amsl.com>; Wed, 6 Sep 2017 12:12:59 -0700 (PDT)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 7FA55132964 for <quic-issues@ietf.org>; Wed, 6 Sep 2017 12:12:59 -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=08ug9xpeq6UhQ9pgZKoEffR2H0o=; b=pXjd35oI8nqjWkhP 945PnECTvjBfHxy389u9px9bKQXeC1PIm9JYta+sqmqIENnzwbi8rw5KN/DLphOm qHJDN97c6jgVSDO2RzsxpHfqXnzLCowXlcKgT3hyefS6lvNDW4QCbEZ18CxImT/w OQU7R4fOgW/Jfym3wn7q6BnXzCk=
Received: by filter0459p1mdw1.sendgrid.net with SMTP id filter0459p1mdw1-4906-59B048BA-4 2017-09-06 19:12:58.087919471 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0040p1mdw1.sendgrid.net (SG) with ESMTP id nrwOT4BHRMWakoIyBotqIg for <quic-issues@ietf.org>; Wed, 06 Sep 2017 19:12:58.108 +0000 (UTC)
Date: Wed, 06 Sep 2017 19:12:58 +0000
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab629b72cf46b36140b4d28516b1cebdfe0290e77e92cf0000000115c80ab992a169ce0ea843fe@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/698/327584965@github.com>
In-Reply-To: <quicwg/base-drafts/issues/698@github.com>
References: <quicwg/base-drafts/issues/698@github.com>
Subject: Re: [quicwg/base-drafts] Does a timestamp for a packet implicity ACK it (#698)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59b048b9ce1d3_76a13fac2f7f5c2c67714"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3+l58WzHDVkE5KXk/q6NurwHwHv0De6kgZNE 5UFWFxkSVDl4AgULU7RTPIZJ4g8nJUuAsxUHlvU4uQjRn8dlBfYQZxsDQvBSM/PsoseSYh3B/Hxz7E wX/C0oNeLiR/W6WGN7WT6TyWlXDiejJToO/+i0QTLbiabftqpLHw4Y4YoCE8E9yTd12jKUDgbovlOr E=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/0xRbB9F4iW1EgcgavP0QAfyyuCU>
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: Wed, 06 Sep 2017 19:13:01 -0000
> to say that one MUST not specify timestamps that don't have corresponding ack blocks I actually would go the other way on this. If we are expected to send timestamps in most cases anyway, there is zero information added to also have a sack block for that data. If the ACK frame is lost, it's perfectly fine to later represent the receipt of that packet as an ack block. But IMO receivers MUST interpret timestamps as an acknowledgement. Senders: - MUST represent receipt of a packet as either a timestamp OR an ack block in a single ACK frame. - SHOULD represent it as a timestamp when first attempting to ack the packet; -- 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/698#issuecomment-327584965
- [quicwg/base-drafts] Does a timestamp for a packe… Subodh Iyengar
- Re: [quicwg/base-drafts] Does a timestamp for a p… ianswett
- Re: [quicwg/base-drafts] Does a timestamp for a p… Subodh Iyengar
- Re: [quicwg/base-drafts] Does a timestamp for a p… ianswett
- Re: [quicwg/base-drafts] Does a timestamp for a p… MikkelFJ
- Re: [quicwg/base-drafts] Does a timestamp for a p… ianswett
- Re: [quicwg/base-drafts] Does a timestamp for a p… martinduke
- Re: [quicwg/base-drafts] Does a timestamp for a p… martinduke
- Re: [quicwg/base-drafts] Does a timestamp for a p… janaiyengar
- Re: [quicwg/base-drafts] Does a timestamp for a p… martinduke
- Re: [quicwg/base-drafts] Does a timestamp for a p… ekr
- Re: [quicwg/base-drafts] Does a timestamp for a p… Martin Thomson