Return-Path: 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 2DF45130E44 for ; Tue, 2 Oct 2018 08:53:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.456 X-Spam-Level: X-Spam-Status: No, score=-8.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 BG-LeogsvpyV for ; Tue, 2 Oct 2018 08:53:13 -0700 (PDT) Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 606FF130E16 for ; Tue, 2 Oct 2018 08:53:13 -0700 (PDT) Date: Tue, 02 Oct 2018 08:53:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538495592; bh=nVPrkNlXtITcOs7ZLnlVtakwDVFVKJmzge8t9isJNrk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Jkyy37wG6fS29mEXTD9epUdiwvwaoMWa9dWYrtYExjytK7kscG8Dn3vGIXHBBIb1O j9StyBxqi3qW2s8Aj2YLSeQXibyuY/QbmaSb2p24sNPd0MezigRhHiLe7qI4JEikMs v8Fn/oiyWJLFFN6DExfOzKdmvoHpgkZfBBNLqm2U= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Ack Delay and TLP (#1796) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5bb3946820497_48253fc2668d45c44705c"; 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 Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.29 List-Id: Notification list for GitHub issues related to the QUIC WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2018 15:53:15 -0000 ----==_mimepart_5bb3946820497_48253fc2668d45c44705c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit janaiyengar commented on this pull request. > @@ -446,16 +433,16 @@ flight, since this packet adds network load without establishing packet loss. ## Generating Acknowledgements QUIC SHOULD delay sending acknowledgements in response to packets, but MUST NOT -excessively delay acknowledgements of packets containing frames other than ACK -or ACN_ECN. Specifically, implementations MUST attempt to enforce a maximum -ack delay to avoid causing the peer spurious timeouts. The RECOMMENDED maximum -ack delay in QUIC is 25ms. - -An acknowledgement MAY be sent for every second full-sized packet, as TCP does -{{?RFC5681}}, or may be sent less frequently, as long as the delay does not -exceed the maximum ack delay. QUIC recovery algorithms do not assume the peer -generates an acknowledgement immediately when receiving a second full-sized -packet. +excessively delay acknowledgements of packets containing frames other than ACK. +Specifically, implementations MUST attempt to enforce a maximum +ack delay to avoid causing the peer spurious timeouts. The maximum ack delay +is communicated in the `max_ack_delay` transport parameter and the default s/default/RECOMMENDED -- 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/pull/1796#pullrequestreview-160794798 ----==_mimepart_5bb3946820497_48253fc2668d45c44705c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar commented on this pull request.

In draft-ietf-quic-recovery.md:

> @@ -446,16 +433,16 @@ flight, since this packet adds network load without establishing packet loss.
 ## Generating Acknowledgements
 
 QUIC SHOULD delay sending acknowledgements in response to packets, but MUST NOT
-excessively delay acknowledgements of packets containing frames other than ACK
-or ACN_ECN.  Specifically, implementations MUST attempt to enforce a maximum
-ack delay to avoid causing the peer spurious timeouts.  The RECOMMENDED maximum
-ack delay in QUIC is 25ms.
-
-An acknowledgement MAY be sent for every second full-sized packet, as TCP does
-{{?RFC5681}}, or may be sent less frequently, as long as the delay does not
-exceed the maximum ack delay.  QUIC recovery algorithms do not assume the peer
-generates an acknowledgement immediately when receiving a second full-sized
-packet.
+excessively delay acknowledgements of packets containing frames other than ACK.
+Specifically, implementations MUST attempt to enforce a maximum
+ack delay to avoid causing the peer spurious timeouts.  The maximum ack delay
+is communicated in the `max_ack_delay` transport parameter and the default

s/default/RECOMMENDED

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5bb3946820497_48253fc2668d45c44705c--