We apologize for the delay in getting out these comments and we hope that you will respond more quickly with your reactions. Please direct your replies via the standard RFC mechanism. Two structures are presented in this RFC as shown below. Three variations are given for the way in which socket names are assigned, as examples of use of the first structure.
Users pick the arbitrary number arbitrarily and associate it with a process.
A logger chooses the arbitrary number dynamically and associates it with a process via a directory. The arbitrary number is assigned outside of a logger but may be issued by a logger to the remote party. The following discussion covers three different schemes of socket identifier assignment using a simple example. Under this scheme a user is able to use any 32-bit socket identifier he chooses. However, the possibility that some other user has accidentally picked this particular identifier is reasonably small, since there are about a billion different identifiers.