Hi, Gorry, On 4/4/2016 10:55 AM, [email protected] wrote: > 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.
These are different things, IMO. The TCP API needs a way to set any flags in the TCP header, either directly or indirectly. TCP does NOT require a way to set the MSS or segment size, IMO - that ought to be something it figures out from the interface parameters, IP settings, remote end, and path. It may be useful to set these things for instrumentation purposes, but not for regular operation. For MSS and segment size, the same ought to be true for UDP. For ECN, UDP ought to be ignorant - as should its API. The only question is whether the UDP API should have a "pass through" for signals from lower layers, whether IP, Ethernet, etc. IMO, those aren't part of the UDP API; they're part of the OS endpoint API to these other protocols. Joe > > 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
