Index Journeys
RFC 322 UNKNOWN ARPANET · SOCKETS

Well-Known Sockets: Well known socket numbers

UCLA asks every host to report which sockets are already taken by standard services.

On rfc-editor.org ↗
PUBLISHED
March 1972
AUTHORS
V. Cerf, J. Postel
STREAM
Legacy
NETWORK LOGGER
Socket 1
PROPOSED CATALOG HOME
NIC
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   ]

AI ELI5

On this page
PROBLEMThe Network Measurement Group wanted a standard socket for a Process Discard service but did not know which sockets were already in use at each Host.
MECHANISMThe authors ask each Host Technical Liaison to send a note or phone call describing the function and socket numbers of its network service programs, and propose a published catalog kept at the NIC.
WHAT IT SETSThe RFC is a request for information; it notes only that socket 1 is the Network Logger, where ICP may be performed.

§1Why a Catalog Is Needed

The Network Measurement Group wants to establish a network standard socket number for a Process Discard service. Not all Hosts need to cooperate. To choose a number, the authors must know which sockets at each Host are already allocated to standard network functions.

They want to open a new service with its own door number, so they first need to know which door numbers are taken.

§2Socket 1 and the Request

At all Hosts that permit login for services, socket 1 is the Network Logger, on which the Initial Connection Protocol (ICP) may be performed.

The authors would like to catalog other sockets that are supposed to be well known. They ask each Host Technical Liaison for a note or phone call describing the function and socket numbers of the network service programs at that Host. The catalog would be published, and they recommend that it be maintained at the NIC.

Door number 1 is the front desk where you ask to be let in. Everyone is asked to send in a list of their other known doors.

§3What Comes Next

The RFC contains no protocol specification. It is a short call for information, with contact details for Vint Cerf and Jon Postel at UCLA, so that Technical Liaisons could respond.

It is only a letter asking for help, with the writers' phone numbers at the bottom.