Index Journeys
RFC 322 UNKNOWN ARPANET · SOCKETS

Well-Known Sockets: Well known socket numbers

A request for each host to report socket numbers used by its network services.

On rfc-editor.org ↗
PUBLISHED
March 1972
AUTHORS
V. Cerf, J. Postel
STREAM
Legacy
DOI
10.17487/RFC0322

RFC text

Original text · RFC Editor View on rfc-editor.org ↗ 
Network Working Group                                         V. Cerf
Request for Comments #322                                     J. Postel
NIC #9609                                                     UCLA-NMC
                                                              26 March 72

                       Well Known Socket Numbers

     The Network Measurement Group would like to establish a network
standard socket number for a Process Discard service (not all HOSTs need
cooperate.) To do this, it is necessary to know which sockets at each
HOST have already been allocated to standard network functions.

     At all HOSTs which permit login for services, socket 1 is the
Network Logger on which ICP may be performed.

     We would like to catalog other sockets which are supposed to be
well-known, so we would appreciate having a note or phone call from each
HOST Technical Liaison describing the function and socket numbers of
network service programs at each HOST.  The catalog will be published and
we would recommend that it be maintained at NIC.


                            Dr. Vint Cerf or Jon Postel
                            3804 Boelter Hall
                            UCLA Computer Science Department
                            Los Angeles, California 90024

                            (213) 825-4864   Vint

                            (213) 825-4733   Jon

                            (213) 825-2368   Secretary




       [ 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   ]

ISO Plain Language

On this page
PROBLEMThe Network Measurement Group wanted a standard socket for a Process Discard service but did not know which socket numbers were already allocated.
MECHANISMThe authors ask each Host Technical Liaison to provide the functions and socket numbers of network service programs at that host.
WHAT IT ASKSThe note says socket 1 is the Network Logger, where ICP may be performed, and proposes maintaining a published catalog at the NIC.

§1Finding an Available Socket

The Network Measurement Group wanted to establish a standard socket number for a Process Discard service. It did not require every host to cooperate, but the group needed to know which sockets already served standard network functions.

The group wanted a socket number for a new service. First it needed to find out which numbers were already in use.

§2The Request for Host Lists

RFC 322 states that socket 1 is the Network Logger at hosts that permit login for services, and that the Initial Connection Protocol may be performed there. The authors ask each Host Technical Liaison to report service functions and socket numbers.

They propose publishing the resulting catalog and recommend keeping it at the Network Information Center.

The note names socket 1 for the Network Logger and asks each host to identify its other service sockets. The proposed list would be published for the network community.

§3A Request, Not a Protocol

The RFC contains no specification for the Process Discard service and no completed catalog. It is a request for information from hosts, with contact details for the authors at UCLA.

This RFC asks hosts to send information. It does not define the new service or provide the catalog's final contents.