> On 1. jun. 2015, at 23.17, Joe Touch <[email protected]> wrote: > > > > On 6/1/2015 12:23 PM, Michael Welzl wrote: >> I'll try addressing another detail, maybe that helps get us aligned: >> >> >>> On 1. jun. 2015, at 21.38, Mirja Kühlewind >>> <[email protected]> wrote: >>> >>> Hi Joe >>>> >>>> My concern is that there is no clear relation between 3.1.2 and 3.1.3. >>> >>> Yes, that’s actually true. Initially there was no section 3.1.2 as this doc >>> is not on interfaces. However it seems to be incomplete without mentioning >>> interfaces at all. If we keep this section, you are right, the relation >>> should be there. >> >> The document is about services. These are provided via interfaces - so the >> document should very much be about interfaces. >> 3.1.3 describes TCP, it lists all the things you get with TCP - nothing that >> the application can configure, but what you get with it anyway. >> >> The complete service provided by TCP consists of everything TCP is AND the >> what the application can configure about it. > > Yes. > >> It gives you segmentation, congestion control, .... AND it lets you use PUSH >> and an URGENT pointer and ... > > 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 ... Cheers, Michael _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
