33 ms·
Correction: While the socket is an implementation concept in some implementations, it generally is not. From RFC 793 (TCP): To allow for many processes within
by ambrop7 12y ago
Correction: While the socket is an implementation concept in some implementations, it generally is not. From RFC 793 (TCP):
To allow for many processes within a single Host to use TCP
communication facilities simultaneously, the TCP provides a set of
addresses or ports within each host. Concatenated with the network
and host addresses from the internet communication layer, this forms
a socket. A pair of sockets uniquely identifies each connection.
That is, a socket may be simultaneously used in multiple
connections.
But then, it is a TCP specific concept, and TLS is a better name because it can be used on top of other transport layers.
- tptacek 12y agoI knew someone was going to dispute that. :) I'd make two counterarguments about RFC 793: 1. It was written in 1981. You can find lots of other terms in early-80s RFCs that are no longer applicable to modern TCP/IP. 2. It was written in a time when Unix (and I guess VMS) implementation concerns infected all of standards work; if you follow the IETF, particularly DNS, there has been a long painful process of trying to disinfect standards of implementation entanglements. But we agree on TLS being the better name, which is probably all the matters to the thread.