Re: [quicwg/base-drafts] ACK of non-existent packet is illegal (#2302)

[Marten Seemann <[e-mail]>]

marten-seemann commented on this pull request.



>  acknowledgment of its ACK frames, with the knowledge this could cause the sender
 to unnecessarily retransmit some data.  Standard QUIC {{QUIC-RECOVERY}}
 algorithms declare packets lost after sufficiently newer packets are
 acknowledged.  Therefore, the receiver SHOULD repeatedly acknowledge newly
 received packets in preference to packets received in the past.
 
+An endpoint SHOULD treat receipt of an acknowledgment for a packet it did not
+send as a connection error of type PROTOCOL_VIOLATION, if it is able to detect

We had PROTOCOL_VIOLATIONs come up in interop testing a couple of times. The problem is, it tells you **exactly nothing** about what's going wrong.

gQUIC was (relatively) easy to debug, partly because it has a very long list of error codes. At some point (and I don't remember when and why), we decided to shrink that list to just around 10 error codes. Now we don't even have a single error code left for loss-recovery related errors - it's all just a PROTOCOL_VIOLATION.

-- 
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/2302#discussion_r245850590