[quicwg/base-drafts] ACKs for receiver-only (#1232)
ekr <notifications@github.com> Sun, 18 March 2018 21:55 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 3F30112AF83 for <quic-issues@ietfa.amsl.com>; Sun, 18 Mar 2018 14:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.606
X-Spam-Level:
X-Spam-Status: No, score=-0.606 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 pNHnvZzBPJYk for <quic-issues@ietfa.amsl.com>; Sun, 18 Mar 2018 14:55:24 -0700 (PDT)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (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 4296E1205F0 for <quic-issues@ietf.org>; Sun, 18 Mar 2018 14:55:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=GBD5rBkcB7bO14syOOxNTMTXwAQ=; b=cVbdlFDzC/2Fu+pw 7TH9mMp0LdvOqVFXBK5+0tLmX2iibWMJpIe8Kr3SLqdEIXN+cMlxZtEWHI7nzQPv AgXo3e/LZ+E7dz1eMZ9arVz1E5i/NwN7LeaEAPNeAC3obRe+dNPGzfLloaNajyy6 DEUNh4jYdNu54xKLRhMC6haReeU=
Received: by filter0525p1iad2.sendgrid.net with SMTP id filter0525p1iad2-26439-5AAEE049-23 2018-03-18 21:55:21.947061545 +0000 UTC
Received: from smtp.github.com (out-2.smtp.github.com [192.30.252.193]) by ismtpd0009p1iad1.sendgrid.net (SG) with ESMTP id wt1zx9sKS86SWt84CTmAiA for <quic-issues@ietf.org>; Sun, 18 Mar 2018 21:55:21.886 +0000 (UTC)
Date: Sun, 18 Mar 2018 21:55:22 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba5c05aa4ff57817450beed5098fdee1c153df3d992cf0000000116c6a24992a169ce12419296@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1232@github.com>
Subject: [quicwg/base-drafts] ACKs for receiver-only (#1232)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5aaee049c0bf8_2bde3fa2e74b0f2c1497a2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak115FtUjxUg80WYtgi//MxhYYFDJ+/YOUF6+1 FjA0RA54ZjE6nHwUy7VU6utvuarorogkFCKjOFtDagLmTAqRxZnFTMn4Z5OA0RwDp7Aojn4duh6cUB IhuAHGuGgG/N1AJOamwJMCWRCKKgXyu7J03OgacVnq/m2Bmf1r/ul5Hhig==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/kbtJ0ahwm_4_4_xxayITOKI7rrE>
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: Sun, 18 Mar 2018 21:55:27 -0000
"A receiver that is only sending ACK frames will not receive acknowledgments for its packets. Sending an occasional MAX_DATA or MAX_STREAM_DATA frame as data is received will ensure that acknowledgements are generated by a peer. Otherwise, an endpoint MAY send a PING frame once per RTT to solicit an acknowledgment." But this isn't true if the counterparty piggybacks ACKs in its packets that contain STREAM data (which is at least what I do!), and why I filed #1231. Is this really the behavior we want? -- 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/1232
- [quicwg/base-drafts] ACKs for receiver-only (#123… ekr
- Re: [quicwg/base-drafts] ACKs for receiver-only (… Nick Banks
- Re: [quicwg/base-drafts] ACKs for receiver-only (… ekr
- Re: [quicwg/base-drafts] ACKs for receiver-only (… Martin Thomson
- Re: [quicwg/base-drafts] ACKs for receiver-only (… ekr
- Re: [quicwg/base-drafts] ACKs for receiver-only (… Martin Thomson
- Re: [quicwg/base-drafts] ACKs for receiver-only (… Martin Thomson