Re: [quicwg/base-drafts] What to ack in an ACK frame (#764)
ianswett <notifications@github.com> Mon, 02 October 2017 01:21 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 17471134BD7 for <quic-issues@ietfa.amsl.com>; Sun, 1 Oct 2017 18:21:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.398
X-Spam-Level:
X-Spam-Status: No, score=-8.398 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=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 XNEQWTkpCo94 for <quic-issues@ietfa.amsl.com>; Sun, 1 Oct 2017 18:21:25 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext5.iad.github.net [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC5CC134BD4 for <quic-issues@ietf.org>; Sun, 1 Oct 2017 18:21:25 -0700 (PDT)
Date: Sun, 01 Oct 2017 18:21:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1506907285; bh=Ya3GXpslVarNUOSPn/w77KxVGo0CE6xLzGevMjgvDx0=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wmZ76TwMmJSm0pfyl/yFndzurtFJ2zqn97so5s/YglW5o6FRc+81ILhXktwnMmnx9 Bod57PDHAxIxE9PYkDN5Oziap4RohKGiPhafvgrwYv/Ypgek7dx3ZElJaMoLpbDuZm zVI9b7wZ92/dXvhZEOEtnOzuBtURjW+8GtHTbkzU=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc82ce33a6d99ba966d4ed1d7ef24cedea4438ac592cf0000000115e9569592a169ce0f3e649b@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/333421216@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_59d19495128f7_29c33f9200e58f2c291f6"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/NkXzFeKs89waxTGHs4_2kkNsv7I>
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, 02 Oct 2017 01:21:27 -0000
We'll discuss this Wednesday, but the general rule is as you outlined in your comment: "Yes, it is clear that we should not include Ack blocks that have already been acked, and that we SHOULD include timestamps exactly once per packet. " Additionally, one should never retransmit the exact same ACK frame, and instead should always send the most up to date ACK information. Additionally, 'loss' of an ACK frame should not cause the sending of a new ack frame, just as it does not in TCP. Should this be called out explicitly in the transport draft? -- 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-333421216
- [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