News for hackers. Stuff that matters.
Re:Lying to TCP makes it a best-effort streaming protocol by mordero on Friday February 02, 2018 @01:28PM (#16292861)
I don't think that is quite true. I believe with UDP there is no promise of packets being received in order. I think this article is saying that you still get the benefits of processing the packets in the order received, but you don't have to worry about the latency of waiting for the re-transmission of any packets.
Re:Lying to TCP makes it a best-effort streaming protocol by vvanders on Friday February 02, 2018 @01:36PM (#16292948)
It's so trivial to add ordering to UDP, it's really the right protocol to use here.

Subverting TCP leads to all sorts of problems around congestion(which you can no longer filter on because which TCP streams are being non-compliant?) that it just should not be done.

Re:Lying to TCP makes it a best-effort streaming protocol by JoeAltmaier on Friday February 02, 2018 @05:46PM (#16294848)
TCP layer also gives you pacing, congestion control and flow control. Which UDP, you'd have to do yourself?
Re:Lying to TCP makes it a best-effort streaming protocol by JoeAltmaier on Friday February 02, 2018 @05:59PM (#16294943)
And its not totally trivial to reorder UDP. Say you receive packets 1,2,3,5. How long to you wait for '4'? Maybe it was dropped; maybe its coming.

Then you get 6,7. Is 4 still out there? You've got 3 packets in your pocket, waiting for 4. That adds up too.

TCP gives you some idea of what packets you SHOULD have received, so you can respond better. UDP doesn't have any windowing etc so you have no idea.

Re:Lying to TCP makes it a best-effort streaming protocol by vvanders on Friday February 02, 2018 @06:12PM (#16295016)
I guess I don't really see the big issue with that. It's not like windowing and congestion control is some kind of black magic. It's spelled out pretty cleanly in the TCP RFC and pretty straight-forward to reimplement.

Generally if you're hitting cases where TCP is causing you grief and you need to reach for UDP you've already got enough context to understand your congestion problems/etc.

We've been doing this in game-dev for decades, ditto the voip space so it's not like you don't have a wealth of knowledge to draw from if you're really stumped.

Re:Lying to TCP makes it a best-effort streaming protocol by JoeAltmaier on Friday February 02, 2018 @07:51PM (#16295448)
If you just use TCP again you haven't done anything. The whole point is to avoid latency.

Most folks use some UDP-based protocol package instead of reinventing the wheel. Its not rocket science, but it isn't trivial. Defining your own packets to do all the flow stuff is just work, like any other programming task.

Re:Lying to TCP makes it a best-effort streaming protocol by vvanders on Friday February 02, 2018 @08:34PM (#16295613)
I don't think I was suggesting using TCP, I was suggesting implementing the features you like from TCP into your stack if you really need them. You can do congestion control without retry, etc.

I've built variations of UDP based protocols 4 or 5 different times over my career. I'm literally in the middle of this right now with the radio framing protocol I've been developing. I really think you're making it out to be much harder than it is.

Re:Lying to TCP makes it a best-effort streaming protocol by tonyg on Saturday February 03, 2018 @04:52AM (#16296955)
I was delighted when DCCP appeared: https://en.wikipedia.org/wiki/Datagram_Congestion_Control_Pr...

It focuses narrowly on a congestion control protocol, and is intended to be combined which whichever datagram-based protocol you have lying around that might be suffering from congestion issues.

Re:Lying to TCP makes it a best-effort streaming protocol by ramenmeal on Friday February 02, 2018 @06:39PM (#16295136)
Isn't the pacing and congestion control based on ACK's though? And this is suggesting to ACK everything. I feel like I'm missing something.
Re:Lying to TCP makes it a best-effort streaming protocol by marcosdumay on Friday February 02, 2018 @08:32PM (#16295602)
> It's so trivial to add ordering to UDP

Specially when compared with creating and using a user space IP protocol like was done here, or adding a new one into the kernel.

Re:Lying to TCP makes it a best-effort streaming protocol by ramzyo on Friday February 02, 2018 @05:40PM (#16294796)
I'm not sure I understand the distinction. How could TCP guarantee that packets will be received in order without re-transmissions? Re-transmission is a mechanism for making this a guarantee. If the receiver just ACKs everything it gets, then isn't that effectively making no guarantees about the order?
Re:Lying to TCP makes it a best-effort streaming protocol by JoeAltmaier on Friday February 02, 2018 @05:45PM (#16294841)
TCP layer of your IP stack does re-ordering and presents them to the client in order. UDP layer doesn't. So by acking every packet, TCP layer will still present what it DOES receive in order.
Re:Lying to TCP makes it a best-effort streaming protocol by ramzyo on Friday February 02, 2018 @08:52PM (#16295676)
Right, but UDP also presents what it receives in order - so what's the advantage of forcing TCP to behave this way? I struggle to think of a practical use case where either a) UDP or another protocol wouldn't be selected [e.g. in a VoIP system] in the design phase b) using TCP in this non-standards compliant way would be nothing more than a short-term bandaid because of other constraints (e.g. can't change Layer 4 to something non-TCP).
Re:Lying to TCP makes it a best-effort streaming protocol by JoeAltmaier on Saturday February 03, 2018 @08:35AM (#16297552)
Absolutely not. UDP delivers packets as received.

Don't underestimate how often packets are received out of order. There's even a consumer DSL modem that swaps every odd UDP packet with every even one - I had to compensate for this in a VOIP product. Using TCP in this bastardized way would cure that. That said, I tend to agree its a poor idea to use TCP in this way. The famous book on IP used to list 8 protocol possibilities (only 2 commonly survive today, UDP and TCP) of which streaming and packet reordering was a valid combination (without acking/retransmitting). Don't know what it was called, but that's what being attempted here.

Re:Lying to TCP makes it a best-effort streaming protocol by ramzyo on Saturday February 03, 2018 @12:33PM (#16298520)
I think we’re operating on different definitions of in-order and as received. TCP delivers packets in order, but perhaps not as received, if it had to request retransmission of a dropped packet. UDP delivers packets in order that they were received. Doing what the article suggests would make TCP also deliver packets in the order that they were received. No?
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)