On Wed, Jul 5, 2023, at 08:15, Matt Joras wrote: > I'm not sure I understand the concern here
My concern is that a sender can send some amount of data, then decide to reliably deliver only a prefix of that data. This allows that to happen with no signals to a receiving application that might indicate something different than a complete delivery of the stream. But the receiving application has somewhere between the cutoff point and the complete stream on hand. The receiving application will be ignorant of these two offsets. All of this happens when the stack is upgraded, not due to a deliberate choice on the part of the application. Hence, my choice of the word "truncation". Hence, my preference for applications to opt in to this by allocating an error code for the purpose (or status code, if you will).
