Return to Answer

1. TCP-IP Illustrated Volume 1 The Protocols, W. Richard Stevens, 1994 Addison Wesley

2. RFC793, Information Sciences Institute, University of Southern California for DARPA

3. RFC147, The Definition of a Socket, Joel M. Winett, Lincoln Laboratory

1. TCP-IP Illustrated Volume 1 The Protocols, W. Richard Stevens, 1994 Addison Wesley

2. RFC793, Information Sciences Institute, University of Southern California for DARPA

3. RFC147, The Definition of a Socket, Joel M. Winett, Lincoln Laboratory

1. TCP-IP Illustrated Volume 1 The Protocols, W. Richard Stevens, 1994 Addison Wesley

2. RFC793, Information Sciences Institute, University of Southern California for DARPA

3. RFC147, The Definition of a Socket, Joel M. Winett, Lincoln Laboratory

1. TCP-IP Illustrated Volume 1 The Protocols, W. Richard Stevens, 1994 Addison Wesley

2. RFC793, Information Sciences Institute, University of Southern California for DARPA

3. RFC147, The Definition of a Socket, Joel M. Winett, Lincoln Laboratory

@plugwash makes a salient observation.

The fundamental problem is that the TCP RFC definition of socket is in conflict with the defintion of socket used by all major operating systems and libraries.

By definition the RFC is correct. When a library misuses terminology, this does not supersede the RFC. Instead, it imposes a burden of responsibility on users of that library to understand both interpretations and to be careful with words and context. Where RFCs do not agree, the most recent and most directly applicable RFC takes precedence.