[Text version]

This RFC is obsoleted by: RFC 750 , RFC 755 , RFC 758 , RFC 762 , RFC 770 , RFC 776 , RFC 790 , RFC 820 , RFC 870 , RFC 900 , RFC 923 , RFC 943 , RFC 960 , RFC 990 , RFC 997 , RFC 1010 , RFC 1020 , RFC 1060 , RFC 1062 , RFC 1117 , RFC 1166 , RFC 1340 , RFC 1700

Network Working Group Request for Comments : 349 NIC : 10428

Jon Postel Computer Science UCLA-NMC 30 May 72

                    Proposed Standard Socket Numbers

I propose that there be a czar (me ?) who hands out official socket
numbers for use by standard protocols.  This czar should also keep track
of and publish a list of those socket numbers where host specific
services can be obtained.  I further suggest that the initial allocation
be as follows:
        Sockets         Assignment
        0-63            Network wide standard functions
        64-127          Host specific functions
        128-239         Reserved for future use
        240-255         Any experimental function

and within the network wide standard functions the following particular
assignment be made:
        Socket          Assignment
           1            Telnet
           3            File Transfer
           5            Remote Job Entry
           7            Echo
           9            Discard

these socket numbers (decimal) are to be used for the socket called "L" in the official Initial Connection protocol (ICP) as specified in NIC 7104 the "Current Network Protocols" notebook.

       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by BBN Corp. under the   ]
       [ direction of Alex McKenzie.                   12/96   ]