News for hackers. Stuff that matters.
Re:Lying to TCP makes it a best-effort streaming protocol by JoeAltmaier on Saturday February 03, 2018 @12:44PM (#16298574)
TCP won't nack a packet when one is perceived as 'missed' (but really out-of-order); that's clear from the premise (ack everything).

But reordering also happens simply by examining received packets in a burst, and putting them right.

So its six of one and a half-dozen of the other I guess. Sorry for coming off so abrupt.

Re:Lying to TCP makes it a best-effort streaming protocol by ramzyo on Saturday February 03, 2018 @01:34PM (#16298818)
No problem, thanks for clarifying! So basically the benefit to the TCP NACK approach is that the TCP layer will also do a sort on the packets received?
Re:Lying to TCP makes it a best-effort streaming protocol by JoeAltmaier on Sunday February 04, 2018 @10:27AM (#16303077)
Yeah, which is imperfect but there you are. It means sometimes out-of-order packets will be reordered, and sometimes dropped (since TCP acked it, the (existing) TCP code will discard the out-of-order packet as 'duplicate'. Which turns out works pretty well in practice, since out-of-order are almost always in a burst (no delay inter-packet)