Re: [quicwg/base-drafts] What to ack in an ACK frame (#764)
janaiyengar <notifications@github.com> Tue, 12 September 2017 23:57 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 DDD3D1320C9 for <quic-issues@ietfa.amsl.com>; Tue, 12 Sep 2017 16:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.396
X-Spam-Level:
X-Spam-Status: No, score=-3.396 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_28=1.404, 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 70aIfdIzj9NO for <quic-issues@ietfa.amsl.com>; Tue, 12 Sep 2017 16:57:14 -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 5D542133188 for <quic-issues@ietf.org>; Tue, 12 Sep 2017 16:57:14 -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=QmoXov+josAUASnR1FVRzXfXJ1w=; b=iTeMjtNV1IOSkuEG jYTbx000TfGHwW7/ZbN0cGt4fKrwlEcV3y6ZEoF0ROWoI0W97yST6NFTG6p64Rvb WjxEP6uZ8HASax0/WQwysOMd693Nk+bX+v8vRUI7zidfQjZXUOXjkIqd9T3rTY94 hqQ+xD/TSsNXIuiQ7w0KMUseEA0=
Received: by filter0405p1mdw1.sendgrid.net with SMTP id filter0405p1mdw1-17440-59B87459-36 2017-09-12 23:57:13.35156072 +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 ismtpd0024p1mdw1.sendgrid.net (SG) with ESMTP id xBcjJmsCTimtGap4mTWljQ for <quic-issues@ietf.org>; Tue, 12 Sep 2017 23:57:13.287 +0000 (UTC)
Date: Tue, 12 Sep 2017 23:57:13 +0000
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab143a8855ea65884ac9a158f14c2772412f8074d992cf0000000115d0365892a169ce0f3e649b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/764/329017624@github.com>
In-Reply-To: <quicwg/base-drafts/issues/764@github.com>
References: <quicwg/base-drafts/issues/764@github.com>
Subject: Re: [quicwg/base-drafts] What to ack in an ACK frame (#764)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59b87458f1493_1f0a3fbecec63c30330eb"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1kiE7KEAnoEmK18oEwNo83UTlqGkiNf4iEwK WzoznimN1ddd9BxwAIpVK+xOhTsRV0FadCCVHyiAcAqmorI0zjJsfNFDVcfI3wfWzeHkB7kl47NH+E BF4/9/TzGhz4x8/MdKXirs2KAXlZLkoBCp7vS0wBLnVY+suIpR2LNYUDcCzr9AqJQaGxBl5kCnmg3X w=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/V6bBbzAN-2UlBUBpggtvFCzZyxc>
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: Tue, 12 Sep 2017 23:57:16 -0000
Just a quick comment on (A): That implies that you have generated timestamps and queued them for sending. I think you'd be better off generating timestamps on the fly, when you're generating the ack. In general, I would very much argue in favor of repeating until unnecessary (ack of ack is received). From a loss recovery perspective, it's really helpful to ensure this. There's not a tremendous amount of cost in the common case to doing this anyways. -- 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/764#issuecomment-329017624
- [quicwg/base-drafts] What to ack in an ACK frame … janaiyengar
- Re: [quicwg/base-drafts] What to ack in an ACK fr… martinduke
- Re: [quicwg/base-drafts] What to ack in an ACK fr… janaiyengar
- Re: [quicwg/base-drafts] What to ack in an ACK fr… martinduke
- Re: [quicwg/base-drafts] What to ack in an ACK fr… ianswett
- Re: [quicwg/base-drafts] What to ack in an ACK fr… martinduke
- Re: [quicwg/base-drafts] What to ack in an ACK fr… ianswett
- Re: [quicwg/base-drafts] What to ack in an ACK fr… MikkelFJ
- Re: [quicwg/base-drafts] What to ack in an ACK fr… ianswett
- Re: [quicwg/base-drafts] What to ack in an ACK fr… ianswett