Date: Sun, 26 Jul 2020 18:52:10 -0700
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK4BLJGER7NDBRNBMF55FIKEVEVBNHHCPIHZLY@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/664077868@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_5f1e334aa5c75_67863f8e100cd96419196e";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/XObZUBPHp4iqPV78LnXClQwt9Qc>


----==_mimepart_5f1e334aa5c75_67863f8e100cd96419196e
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

@tatsuhiro-t Thank you for pointing that out. I missed that.

I tend to think that we should adopt #3957. As stated in my original comment, handling of late acks is the prerequisite of many of the normative requirements that exist in the recovery draft. Therefore, it is better to have a normative requirement for handling of late acks.

-- 
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-664077868
----==_mimepart_5f1e334aa5c75_67863f8e100cd96419196e
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p></p>
<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/tatsuhiro-t/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/tatsuhiro-t">@tatsuhiro-t</a> Thank you for pointing that out. I missed that.</p>
<p>I tend to think that we should adopt <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="664883229" data-permission-text="Title is private" data-url="https://github.com/quicwg/base-drafts/issues/3957" data-hovercard-type="pull_request" data-hovercard-url="/quicwg/base-drafts/pull/3957/hovercard" href="https://github.com/quicwg/base-drafts/pull/3957">#3957</a>. As stated in my original comment, handling of late acks is the prerequisite of many of the normative requirements that exist in the recovery draft. Therefore, it is better to have a normative requirement for handling of late acks.</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-664077868">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK5ATXVKB2RHPKHXVTTR5TMUVANCNFSM4PGIWQVQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK2LI5SUK5K7BHTXNMDR5TMUVA5CNFSM4PGIWQV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE6KQMLA.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-664077868",
"url": "https://github.com/quicwg/base-drafts/issues/3956#issuecomment-664077868",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5f1e334aa5c75_67863f8e100cd96419196e--