On 6/16/2017 11:23 AM, Tommy Pauly wrote: > - I’d love to see the terminology be less sockets-specific, especially > considering the work for Post-Sockets APIs. A set of intents should be able > to be applied to individual messages being sent or on a higher-level > protocol, ideally, not just on the level of a transport connection as > represented by a socket.
I sincerely hope this and other TAPS documents are more specific about what is meant by a "socket". An Internet socket is an IP address paired with a transport protocol port (RFC793), such that a socket pair defines a connection (TCP, SCTP, DCCP) or association (UDP). A Unix socket is a OS mechanism that allows user-space applications to access transport-layer connections or associations. The two are otherwise not related; there are many Unix socket parameters focusing on the OS user-space to kernel-space interface, interprocess communication management, etc, and have no relation to Internet socket pairs. Unix sockets do not represent transport connections; they are interfaces that include access to the transport API. Joe _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
