Reviewer: Yaron Sheffer Review result: Not Ready The whole notion of TAPS is new to me, so I may be missing the point here. This document defines a minimal set of network APIs that should be available to applications, in order to allow multiple different transport protocols to be used as interchangeable plug-ins with minimal or no change to applications. However the document does not cover security, and instead refers readers to a security protocol survey (draft-ietf-taps-transport-security). There's a disconnect here: in many cases we want applications to be aware of security features. For example, a typical TCP-using application should choose whether to enable TLS encryption of the connection (or as a receiver, whether to require encryption), and if TLS is selected, should at the very least receive access to the authenticated address of the connection's peer. In other words, a meaningful minimal set of APIs cannot be defined without considering the effects and requirements of security protocols. Put differently, the application normally treats the transport protocol and the security protocol layered on it as one protocol. Hence the old name of TLS: Secure Socket Layer. The application sees a single socket, not one socket for transport and another for security. This has been the case for TCP for the last 20-odd years, and is unlikely to change any time soon. I have not surveyed the protocols discussed in this draft, and I don't know whether a viable transport-level security protocol exists for each of them. If this is not the case, then I guess the industry is not yet ready for the kind of solution proposed here.
