Re: [quicwg/base-drafts] ACKs for receiver-only (#1232)
Nick Banks <notifications@github.com> Sun, 18 March 2018 23:00 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 968F212D869 for <quic-issues@ietfa.amsl.com>; Sun, 18 Mar 2018 16:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 9-Y9Gdvv2mvi for <quic-issues@ietfa.amsl.com>; Sun, 18 Mar 2018 16:00:10 -0700 (PDT)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 4BD3E12D810 for <quic-issues@ietf.org>; Sun, 18 Mar 2018 16:00:10 -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=M/v77DnEQjWh6TmRw7/B0SATz64=; b=WnHPZUWYAcUhX0S7 zOv9KPJ8lmFUE5MVfjPFKd0SCuzEba3jXs89oHYfZXOY8oHOaY53a9eVk+qeH49k ymWMOI2JmNDpSOiRN/Hn2PrDfyvTdpt5oBo7k2gXuKTiqgXJ/AHYLbEbV90McVE7 fSa9a7+gTeKdJZzlpHpz7YJFx7Q=
Received: by filter0215p1iad2.sendgrid.net with SMTP id filter0215p1iad2-4291-5AAEEF79-2 2018-03-18 23:00:09.140092404 +0000 UTC
Received: from smtp.github.com (out-2.smtp.github.com [192.30.252.193]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id eEaHJaXES6Wiypuu5Q8IBQ for <quic-issues@ietf.org>; Sun, 18 Mar 2018 23:00:09.099 +0000 (UTC)
Date: Sun, 18 Mar 2018 23:00:09 +0000
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab3683e34f6680c7d4f526f161cbd226ac665f34b192cf0000000116c6b17992a169ce12419296@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/374062655@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1232@github.com>
References: <quicwg/base-drafts/issues/1232@github.com>
Subject: Re: [quicwg/base-drafts] ACKs for receiver-only (#1232)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5aaeef7981d8_68703f9d3beaaf3483511"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3sqgMBdTfAN3Y3Dtx2aFb8qXGcv6sw1ixbvF tjd8BRFoaKzGrl4dRUASjrHffLNsbK+wafnkNml9f+ErRXIVS5mIcj1ovpA0esodkh0wWtRjywMGPB TdzKQlmIOY7vmOhzAPSrKQaEq7ea6+sUmPk/S0GDc5jE2zS6TaE80Irq7q0i/fxtEZCDb6I0lbieKg I=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/jhdVTL-APGb_cGC6KuhKErL8Ddc>
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 23:00:12 -0000
@ekr, I don't understand why you say this isn't true. The issue here is that if an endpoint sends nothing but ACKs, there is no guarantee its peer will acknowledge those packets. The peer may have other data to send back, and may choose to include ACK frames in those packets, if there is room, but if the peer has enough constant stream data to send back and (for some reason) prioritizes the STREAM frames higher than ACK frames, it might not end up acknowledging the endpoint's ACK frames in a timely manner. All that being said, personally I think ACK frames should have the highest priority when framing a packet to send out. So if you ever have something to send out (other than the ACKs) then the ACKs should end up getting sent too. But all this seems like an implementation issue to me. -- 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#issuecomment-374062655
- [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