Date: Sun, 26 Jul 2020 21:11:18 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJKYYJ5XRKC3WUEJ5GGN5FI2ONEVBNHHCPIHZLY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3956/664108552@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3956@github.com>
References: <quicwg/base-drafts/issues/3956@github.com>
Subject: Re: [quicwg/base-drafts] Suggest endpoints may recognize acks after
 loss is declared (#3956)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5f1e53e6354a7_3c133f89b2acd96c735743";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/yN44hZRztAMKcngdzuFZDA1lipo>


----==_mimepart_5f1e53e6354a7_3c133f89b2acd96c735743
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

FWIW, our implementation, as of a little while ago, tracks for `>` the current PTO.  If everything is working nicely, that limits our commitment.  As we are sending probes, the time lengthens so that we send a probe before discarding state.  If it takes two probes to get an ACK, we won't recognize that, but we will always catch an ACK for the last set of probes.  And the state commitment is minimal unless we're forced to probe.

-- 
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/3956#issuecomment-664108552
----==_mimepart_5f1e53e6354a7_3c133f89b2acd96c735743
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p></p>
<p>FWIW, our implementation, as of a little while ago, tracks for <code>&gt;</code> the current PTO.  If everything is working nicely, that limits our commitment.  As we are sending probes, the time lengthens so that we send a probe before discarding state.  If it takes two probes to get an ACK, we won't recognize that, but we will always catch an ACK for the last set of probes.  And the state commitment is minimal unless we're forced to probe.</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/3956#issuecomment-664108552">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK5YUKOLBJN56RM5QO3R5T46NANCNFSM4PGIWQVQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJKZ5V3KGNOEPWPQEDBTR5T46NA5CNFSM4PGIWQV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE6KX4CA.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/3956#issuecomment-664108552",
"url": "https://github.com/quicwg/base-drafts/issues/3956#issuecomment-664108552",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5f1e53e6354a7_3c133f89b2acd96c735743--