> On Jul 23, 2019, at 8:19 AM, Theresa Enghardt <ther...@inet.tu-berlin.de> 
> wrote:
> 
> Another important difference between TCP and UDP are Message Boundaries.
> So in some cases, TCP + Framer may be equivalent to UDP.

FWIW, they might provide *similar* capabilities, even only those that the app 
is concerned about, but there are a LOT of other differences that can’t be 
glossed over. In some cases, it is TCP that is lacking (as above); in others, 
UDP).

It’s only important whether the user does or doesn’t care about those 
properties. When they match what they care about, they can be considered 
equivalent.

I.e., there’s not likely going to be a strict and absolute equivalence between 
transports.

Equivalence is TO THE USER, relative to their constraints.

Joe

_______________________________________________
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

Reply via email to