On 10/3/2017 1:22 PM, Toerless Eckert wrote: > APIs suffer the neverending debate of "not an IETF job, go to POSIX". A protocol without an API is dead code. > IMHO, IETF should define APIs, We already have - see TCP and UDP, for example. > eg: let TAPS really do the work thats > now declared out of scope. And then go to POSIX with the results. There are differences between the API defined in a protocol and the way it is implemented in an OS. Both IETF (protocol) and POSIX (OS) have a role in developing aspects of that interface, but IMO it cannot be the "turf" of just one of those organizations. Joe