I agree with your last statement. We must find a way to distinguish between the features that an application may require and network functionalities that derive from those features.
Marie-Jose Montpetit, Ph.D. [email protected] @SocialTVMIT > On Jun 1, 2015, at 11:22 PM, Joe Touch <[email protected]> wrote: > > > > On 6/1/2015 1:34 PM, Michael Welzl wrote: > .... >>> Segmentation is HOW TCP gives you a reliable byte-sequence service over >>> a packet service. >>> >>> It is absolutely NOT something provided to the user or under user >>> control. Users can set MTU values on *some systems*, but that's not part >>> of the TCP API (to the application) nor does MTU necessarily correspond >>> to actual data boundaries (TCP is allowed to do a lot of things). >> >> Yes, I didn't mean that segmentation is under user control. Let me rephrase >> my above sentence: >> >>>> It gives you, via its non-configurable static behavior: >>>> segmentation, congestion control, .... AND it lets you control some >>>> things: PUSH and an URGENT pointer and ... > > But it doesn't "give" you segmentation. It uses segmentation to provide > a reliable byte stream over a packetized service. If we wanted, we could > arguably export a TCP service over a circuit that did NOT need to rely > on segmentation. > > This discussion really needs to distinguish between WHAT TCP exports and > HOW TCP makes that happen - the latter may or may not ever be visible to > the user. > > Joe > > _______________________________________________ > Taps mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/taps
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
