Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!umd5!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!ea.ecn.purdue.edu!davy
From: davy@ea.ecn.purdue.edu (Dave Curry)
Newsgroups: comp.unix.questions
Subject: Re: inet port numbers
Message-ID: <1374@ea.ecn.purdue.edu>
Date: 25 Dec 87 01:29:50 GMT
References: <1480@saturn.ucsc.edu>
Reply-To: davy@ea.ecn.purdue.edu.UUCP (Dave Curry)
Organization: Purdue University Engineering Computer Network
Lines: 21
Keywords: registry

In article <1480@saturn.ucsc.edu> koreth@ssyx.ucsc.edu (Steven Grimm) writes:
>With all the interest in interprocess communication nowadays, there are bound
>to be some port number clashes between peoples' programs.  What does everyone
>think of starting up a registry for port numbers?  

Swell idea.  So swell, in fact, that the Network Information Center
already does it.  They publish the numbers every so often (6 months?)
as a Request for Comments; the most recent is RFC1010, I believe.  You
can get this by using anonymous FTP to SRI-NIC.ARPA, and grabbing the
file RFC:RFC1010.TXT.

The folks who answer mail to NIC@SRI-NIC.ARPA could probably tell you
all about just exactly what numbers they register, etc.  I believe
there are restrictions on some things (like, they only register ports
below 1024 or something).

For those of you who haven't dealt with them, the folks at the address
NIC@SRI-NIC.ARPA are always very helpful with general questions about
the Internet, and you'd be surprised how much of the stuff you'd think
they *should* keep track of they already *do* keep track of...)

--Dave