Date: Tue, 11 Feb 2020 21:06:13 -0800
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK2MCPIOTNXQXFAFFEN4KC5ELEVBNHHCDF6P4Q@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3451/585031589@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3451@github.com>
References: <quicwg/base-drafts/issues/3451@github.com>
Subject: Re: [quicwg/base-drafts] Should we allow ACK-only packets to be
 declared lost? (#3451)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5e4387c5f01d5_9be3f87924cd96c32065d";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Sp3SsRtHnoZCBLomZVA3ydYMzl0>


----==_mimepart_5e4387c5f01d5_9be3f87924cd96c32065d
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I don't follow that argument.

There's a simpler one: if sending packets causes congestion such that loss (or ECN-CE marking) occurs, then ignoring that signal means that you will likely create more congestion.

I don't see how the relationship to inbound packets is relevant here.  There are many ways in which the rate of outbound packets might be determined by inbound packets.  Servers answers requests, after all.  And if ACK-only packets are the dominant use of a link, then deliberately ignoring signals from them likely only drives send rates up to unsustainable levels; and that's on top of not counting those packets toward limits (something that is necessary).

-- 
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/3451#issuecomment-585031589
----==_mimepart_5e4387c5f01d5_9be3f87924cd96c32065d
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>I don't follow that argument.</p>
<p>There's a simpler one: if sending packets causes congestion such that loss (or ECN-CE marking) occurs, then ignoring that signal means that you will likely create more congestion.</p>
<p>I don't see how the relationship to inbound packets is relevant here.  There are many ways in which the rate of outbound packets might be determined by inbound packets.  Servers answers requests, after all.  And if ACK-only packets are the dominant use of a link, then deliberately ignoring signals from them likely only drives send rates up to unsustainable levels; and that's on top of not counting those packets toward limits (something that is necessary).</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/issues/3451?email_source=notifications&amp;email_token=AFTOJK5N6MNLNSPF7VZQHQDRCN7ULA5CNFSM4KTMUMD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELPN7JI#issuecomment-585031589">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK7REDF7DT2HP3FQ7Y3RCN7ULANCNFSM4KTMUMDQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK4BRA2VWJWM657I2XLRCN7ULA5CNFSM4KTMUMD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELPN7JI.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/issues/3451?email_source=notifications\u0026email_token=AFTOJK5N6MNLNSPF7VZQHQDRCN7ULA5CNFSM4KTMUMD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELPN7JI#issuecomment-585031589",
"url": "https://github.com/quicwg/base-drafts/issues/3451?email_source=notifications\u0026email_token=AFTOJK5N6MNLNSPF7VZQHQDRCN7ULA5CNFSM4KTMUMD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELPN7JI#issuecomment-585031589",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5e4387c5f01d5_9be3f87924cd96c32065d--