Date: Fri, 07 Feb 2020 16:12:46 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJKZVLH4C7MRJYHCBEEN4JMXX5EVBNHHCBYLROM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3362/review/355506006@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3362@github.com>
References: <quicwg/base-drafts/pull/3362@github.com>
Subject: Re: [quicwg/base-drafts] Ack delays are adjusted by
 ack_delay_exponent (#3362)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5e3dfcfe15fa0_1a383fce81ecd96814083e";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/g_FD1Q9NJsvYLMNHSBeRDnrPnkg>


----==_mimepart_5e3dfcfe15fa0_1a383fce81ecd96814083e
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

ianswett commented on this pull request.



> @@ -315,14 +315,17 @@ samples, and rttvar is the variation in the RTT samples, estimated using a
 mean variation.
 
 The calculation of smoothed_rtt uses path latency after adjusting RTT samples
-for ACK delays.  For packets sent in the ApplicationData packet number space,
-a peer limits any delay in sending an acknowledgement for an ack-eliciting
-packet to no greater than the value it advertised in the max_ack_delay transport
-parameter.  Consequently, when a peer reports an Ack Delay that is greater than
-its max_ack_delay, the delay is attributed to reasons out of the peer's control,
-such as scheduler latency at the peer or loss of previous ACK frames.  Any
-delays beyond the peer's max_ack_delay are therefore considered effectively
-part of path delay and incorporated into the smoothed_rtt estimate.
+for ACK delays. ACK delays are communicated in the ack_delay field of the

Thanks, done.

-- 
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/3362#discussion_r376663900
----==_mimepart_5e3dfcfe15fa0_1a383fce81ecd96814083e
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p><b>@ianswett</b> commented on this pull request.</p>

<hr>

<p>In <a href="https://github.com/quicwg/base-drafts/pull/3362#discussion_r376663900">draft-ietf-quic-recovery.md</a>:</p>
<pre style='color:#555'>&gt; @@ -315,14 +315,17 @@ samples, and rttvar is the variation in the RTT samples, estimated using a
 mean variation.
 
 The calculation of smoothed_rtt uses path latency after adjusting RTT samples
-for ACK delays.  For packets sent in the ApplicationData packet number space,
-a peer limits any delay in sending an acknowledgement for an ack-eliciting
-packet to no greater than the value it advertised in the max_ack_delay transport
-parameter.  Consequently, when a peer reports an Ack Delay that is greater than
-its max_ack_delay, the delay is attributed to reasons out of the peer&#39;s control,
-such as scheduler latency at the peer or loss of previous ACK frames.  Any
-delays beyond the peer&#39;s max_ack_delay are therefore considered effectively
-part of path delay and incorporated into the smoothed_rtt estimate.
+for ACK delays. ACK delays are communicated in the ack_delay field of the
</pre>
<p>Thanks, done.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/pull/3362?email_source=notifications&amp;email_token=AFTOJKYZE7XMO56UJUGCALTRBX2H5A5CNFSM4KIOQTF2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCUYJOVQ#discussion_r376663900">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK745I2B3AKSKAQMYOTRBX2H5ANCNFSM4KIOQTFQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK3J7RWZTHKKAWFWY6LRBX2H5A5CNFSM4KIOQTF2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCUYJOVQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/pull/3362?email_source=notifications\u0026email_token=AFTOJKYZE7XMO56UJUGCALTRBX2H5A5CNFSM4KIOQTF2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCUYJOVQ#discussion_r376663900",
"url": "https://github.com/quicwg/base-drafts/pull/3362?email_source=notifications\u0026email_token=AFTOJKYZE7XMO56UJUGCALTRBX2H5A5CNFSM4KIOQTF2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCUYJOVQ#discussion_r376663900",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5e3dfcfe15fa0_1a383fce81ecd96814083e--