I was thinking in terms of what we were trying to achieve within TAPS, and from that perspective things like: ECN-marks, Maximum datagram/segment size, etc. I do not think through the TCP API (for instance), since these concern the path and are only needed by CC or PMTUD algorithms within TCP.
These same values do need to be accessed (visible) over the current UDP API so that apps can implement mechanisms that use these. Gorry > On 4/3/2016 4:54 AM, [email protected] wrote: >> When someone talks about using TCP or SCTP then they are typically using >> an API to the transport that hides a lot of details. > > I'm not sure I agree with this. > > IMO, TCP defines an API that is intended to provide a service capability > that it renders on top of less-capable underlying services. > > UDP does this much less so, so that might be a simpler place to start, > but only because the level of service is simpler - not because of > "hiding a lot of details". > > Joe > > _______________________________________________ > Taps mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/taps > _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
