home *** CD-ROM | disk | FTP | other *** search
/ The Hacker's Encyclopedia 1998 / hackers_encyclopedia.iso / rfc / 1 / rfc0175.txt < prev    next >
Encoding:
Text File  |  2003-06-11  |  2.2 KB  |  60 lines
  1.  
  2.  
  3.  
  4.  
  5.  
  6.  
  7. Network Working Group                        11 June 1971
  8. Request for Comments: 175                    E. Harslem - Rand
  9. NIC 7074                                     J. Heafner - Rand
  10.  
  11.              Comments on "Socket Conventions Reconsidered"
  12.              ---------------------------------------------
  13.  
  14.         We agree with the conclusions reached by Abhay, Bob, and Joel in
  15.    RFC #167, "Socket Conventions Reconsidered," (see RFC #129, scheme #4)
  16.    -- especially the necessity for a major NCP overhaul.
  17.  
  18.         Our main departure in thinking from RFC #167 concerns the socket
  19.    length. (See RFC #164, page 21.)  Since there is an apparently serious
  20.    TIP storage consideration, Rand- assigned sockets will have the
  21.    high-order 16 bits zero.
  22.  
  23.         For the particular programs (current and pending) that Rand must
  24.    access, repeatability of socket name (RFC #167, page 3) is not
  25.    necessary for the user process and also not necessary for the server
  26.    process except for initial contact (ICP) sockets.
  27.  
  28.    Our current use of socket names is diagrammed below.
  29.  
  30.     O           15 16             23 24          30 31
  31.     ---------------------------------------------------
  32.    |              |                 |              |   |
  33.     ---------------------------------------------------
  34.      ^              ^                 ^              ^
  35.      |_ zero        |                 |              |_ gender
  36.                     |                 |
  37.                     |                 |_ zero for initial
  38.                     |                    contact, otherwise
  39.                     |                    dynamically assigned
  40.                     |                    by 3rd level user
  41.                     |                    program
  42.                     |_ administratively assigned (fixed
  43.                        and associated with programs)
  44.  
  45.    (NOTE: This scheme corresponds exactly with both UCSB and UCLA/CCN
  46.    conventions).
  47.  
  48.        [ This RFC was put into machine readable form for entry ]
  49.        [ into the online RFC archives by BBN Corp. under the   ]
  50.        [ direction of Alex McKenzie.                   12/96   ]
  51.  
  52.  
  53.  
  54.  
  55.  
  56.  
  57.  
  58.                                                                 [Page 1]
  59.  
  60.