ietf-wg-mops / draft-ietf-mops-streaming-opcons

drafts for the mops IETF working group
Other
5 stars 4 forks source link

Comparison between UDP and TCP isn't quite right - should be between applications over UDP and over TCP #134

Closed SpencerDawkins closed 2 years ago

SpencerDawkins commented 2 years ago

From @tfpauly

SpencerDawkins commented 2 years ago

@tfpauly - I need to look at this more closely. I understand your point about UDP, but (because UDP is not a real transport layer, while TCP and QUIC are), I suspect (without looking closely yet) I'm going to be making sure that I explain this more clearly, without trying to explain the behavior(s) of applications running over TCP and QUIC.

As an aside, I'm trying to make this clearer in drafts I'm targeting forwards Media Over QUIC/MOQ, so I actually DO believe you ...

Please await results.

GrumpyOldTroll commented 2 years ago

A +1 from @michael-scharf 's review (https://mailarchive.ietf.org/arch/msg/mops/eGGPYW2vytPsLwRBlJ38MezPFh0/):

Section 6. Evolution of Transport Protocols and Transport Protocol Behaviors

I really wonder whether UDP vs. TCP vs. QUIC is actually the relevant distinction. What may actually matter are the transport services provided by the protocol stack (e.g., RFC 8095). I fully agree to a related comment in the INTDIR review.

SpencerDawkins commented 2 years ago

After looking at this issue. I agree with both @tfpauly and @michael-scharf that the emphasis should be on the interaction between (see new section describing this) media transport protocols and the transport services provided by underlying transport protocols.

I'm moving the formerly-UDP section below the formerly-TCP section, because it's easier to describe what UDP is NOT doing after describing what TCP IS doing. I'm also moving one paragraph into the formerly-TCP section from Section 6, because it is specific to ABR strategies that assume a reliable transport.

More news to come, when I create a PR for this issue ...

SpencerDawkins commented 2 years ago

We think #169 is now mergrable.