[quicwg/base-drafts] missing description of what happens when receiving an ACK for an unsent package (#2298)

Marten Seemann <notifications@github.com> Sun, 06 January 2019 09:16 UTC

Date: Sun, 06 Jan 2019 01:16:38 -0800
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2e74c722bc0d98bd08f161dabe1b438aa8f0f80192cf000000011849897692a169ce179e2ba1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2298@github.com>
Subject: [quicwg/base-drafts] missing description of what happens when receiving an ACK for an unsent package (#2298)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c31c776406c0_18bc3f8a544d45b82524b6"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/HgyomPRYtVGYWa0QXaTCCElmO28>

I can't find text about this case anywhere.

A peer that receives an acknowledgement for a packet that it didn't send should be required to close the connection. I'm not sure which error code to use for that though, none of those currently defined really matches this case, so you'd have to use INTERNAL_ERROR. We might want to consider introducing a more specific error code.

-- 
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/2298

[quicwg/base-drafts] missing description of what … Marten Seemann
Re: [quicwg/base-drafts] missing description of w… Kazuho Oku
Re: [quicwg/base-drafts] missing description of w… MikkelFJ
Re: [quicwg/base-drafts] missing description of w… MikkelFJ
Re: [quicwg/base-drafts] missing description of w… MikkelFJ
Re: [quicwg/base-drafts] missing description of w… Martin Thomson