Network Working Group J. Reynolds Request for Comments: 1700 J. Postel STD: 2 ISI Obsoletes RFCs: 1340, 1060, 1010, 990, 960, October 1994 943, 923, 900, 870, 820, 790, 776, 770, 762, 758,755, 750, 739, 604, 503, 433, 349 Obsoletes IENs: 127, 117, 93 Category: Standards Track
ASSIGNED NUMBERS
Status of this Memo
This memo is a status report on the parameters (i.e., numbers and keyWords) used in PRotocols in the Internet community. Distribution of this memo is unlimited.
OVERVIEW
This RFCis a snapshot of the ongoing process of the assignment of protocol parameters for the Internet protocol suite. To make the current information readily available the assignments are kept up-to- date in a set of online text files. This RFChas been assembled by catinating these files together with a minimum of formatting "glue". The authors appologize for the somewhat rougher formatting and style than is typical of most RFCs.
We eXPect that various readers will notice specific items that should be corrected. Please send any specific corrections via email to <iana@isi.edu>.
INTRODUCTION
The files in this Directory document the currently assigned values for several series of numbers used in network protocol implementations.
FTP://ftp.isi.edu/in-notes/iana/assignments
The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols. The IANA is chartered by the Internet Society (ISOC) and the Federal Network Council (FNC) to act as the clearinghouse to assign and coordinate the use of numerous Internet protocol parameters.
The Internet protocol suite, as defined by the Internet Engineering Task Force (IETF) and its steering group (the IESG), contains numerous parameters, such as internet addresses, domain names, autonomous system numbers (used in some routing protocols), protocol numbers, port numbers, management information base object identifiers, including private enterprise numbers, and many others.
The common use of the Internet protocols by the Internet community requires that the particular values used in these parameter fields be assigned uniquely. It is the task of the IANA to make those unique assignments as requested and to maintain a registry of the currently assigned values.
Requests for parameter assignments (protocols, ports, etc.) should be
sent to <iana@isi.edu>.
Requests for SNMP network management private enterprise number assignments should be sent to <iana-mib@isi.edu>.
The IANA is located at and Operated by the Information Sciences Institute (ISI) of the University of Southern California (USC).
If you are developing a protocol or application that will require the use of a link, socket, port, protocol, etc., please contact the IANA to receive a number assignment.
Joyce K. Reynolds Internet Assigned Numbers Authority USC - Information Sciences Institute 4676 Admiralty Way Marina del Rey, California 90292-6695
Most of the protocols are documented in the RFCseries of notes. Some of the items listed are undocumented. Further information on protocols can be found in the memo, "Internet Official Protocol Standards" (STD 1).
Data Notations
The convention in the documentation of Internet Protocols is to express numbers in decimal and to picture data in "big-endian" order [COHEN]. That is, fields are described left to right, with the most significant octet on the left and the least significant octet on the right.
The order of transmission of the header and data described in this document is resolved to the octet level. Whenever a diagram shows a group of octets, the order of transmission of those octets is the normal order in which they are read in English. For example, in the following diagram the octets are transmitted in the order they are numbered.
Whenever an octet represents a numeric quantity the left most bit in the diagram is the high order or most significant bit. That is, the bit labeled 0 is the most significant bit. For example, the following diagram represents the value 170 (decimal).
Similarly, whenever a multi-octet field represents a numeric quantity the left most bit of the whole field is the most significant bit. When
a multi-octet quantity is transmitted the most significant octet is transmitted first.
Special Addresses
There are five classes of ip addresses: Class A through Class E. Of these, Classes A, B, and C are used for unicast addresses, Class D is used for multicast addresses, and Class E addresses are reserved for future use.
With the advent of classless addressing [CIDR1, CIDR2], the
network-number part of an address may be of any length, and the whole notion of address classes becomes less important.
There are certain special cases for IP addresses. These special cases can be concisely summarized using the earlier notation for an IP address:
if we also use the notation "-1" to mean the field contains all 1 bits. Some common special cases are as follows:
(a) {0, 0}
This host on this network. Can only be used as a source address (see note later).
(b) {0, <Host-number>}
Specified host on this network. Can only be used as a source address.
(c) { -1, -1}
Limited broadcast. Can only be used as a destination address, and a datagram with this address must never be forwarded outside the (sub-)net of the source.
(d) {<Network-number>, -1}
Directed broadcast to specified network. Can only be used as a destination address.
(e) {<Network-number>, <Subnet-number>, -1}
Directed broadcast to specified subnet. Can only be used as a destination address.
(f) {<Network-number>, -1, -1}
Directed broadcast to all subnets of specified subnetted network. Can only be used as a destination address.
(g) {127, <any>}
Internal host loopback address. Should never appear outside a host.
REFERENCES
[COHEN] Cohen, D., "On Holy Wars and a Plea for Peace", IEEE Computer Magazine, October 1981.
[CIDR1] Fuller, V., T. Li, J. Yu, and K. Varadhan, "Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy", RFC1519, September 1993.
[CIDR2] Rekhter, Y., and T. Li, "An Architecture for IP Address Allocation with CIDR", RFC1518, September 1993.
In the Internet Protocol (IP) [RFC791] there is a field to identify the version of the internetwork general protocol. This field is 4 bits in size.
Assigned Internet Version Numbers
Decimal Keyword Version References ------- ------- ------- ---------- 0 Reserved [JBP] 1-3 Unassigned [JBP] 4 IP Internet Protocol [RFC791,JBP] 5 ST ST Datagram Mode [RFC1190,JWF] 6 SIP Simple Internet Protocol [RH6] 7 TP/IX TP/IX: The Next Internet [RXU] 8 PIP The P Internet Protocol [PXF] 9 TUBA TUBA [RXC] 10-14 Unassigned [JBP] 15 Reserved [JBP]
REFERENCES
[RFC791] Postel, J., ed., "Internet Protocol - DARPA Internet Program Protocol Specification", STD 5, RFC791, USC/Information Sciences Institute, September 1981.
[RFC1190] Topolcic, C., Editor, "Experimental Internet Stream Protocol, Version 2 (ST-II)", RFC1190, CIP Working Group,
[CFTP] Forsdick, H., "CFTP", Network Message, Bolt Beranek and Newman, January 1982.
[CISCO] Cisco Systems, "Gateway Server Reference Manual", Manual Revision B, January 10, 1988.
[DDN] Feinler, E., Editor, "DDN Protocol Handbook", Network Information Center, SRI International, December 1985.
[DGP] M/A-COM Government Systems, "Dissimilar Gateway Protocol Specification, Draft Version", Contract no. CS901145, November 16, 1987.
[ETHERNET] "The Ethernet, A Local Area Network: Data Link Layer and Physical Layer Specification", AA-K759B-TK, Digital Equipment Corporation, Maynard, MA. Also as: "The Ethernet - A Local Area Network", Version 1.0, Digital Equipment Corporation, Intel Corporation, Xerox Corporation, September 1980. And: "The Ethernet, A Local Area Network: Data Link Layer and Physical Layer Specifications", Digital, Intel and Xerox, November 1982. And: XEROX, "The Ethernet, A Local Area Network: Data Link Layer and Physical Layer Specification", X3T51/80-50, Xerox Corporation, Stamford, CT., October 1980.
[IEN90] Cohen, D. and J. Postel, "Multiplexing Protocol", IEN 90,
USC/Information Sciences Institute, May 1979.
[IEN119] Forgie, J., "ST - A Proposed Internet Stream Protocol", IEN 119, MIT Lincoln Laboratory, September 1979.
[IEN158] Haverty, J., "XNET Formats for Internet Protocol Version 4", IEN 158, October 1980.
[MFENET] Shuttleworth, B., "A Documentary of MFENet, a National Computer Network", UCRL-52317, Lawrence Livermore Labs, Livermore, California, June 1977.
[PUP] Boggs, D., J. Shoch, E. Taft, and R. Metcalfe, "PUP: An Internetwork Architecture", XEROX Palo Alto Research Center, CSL-79-10, July 1979; also in IEEE Transactions on Communication, Volume COM-28, Number 4, April 1980.
[SPRITE] Welch, B., "The Sprite Remote Procedure Call System", Technical Report, UCB/Computer Science Dept., 86/302, University of California at Berkeley, June 1986.
[RFC741] Cohen, D., "Specifications for the Network Voice Protocol", RFC741, ISI/RR 7539, USC/Information Sciences Institute, March 1976.
[RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC768, USC/Information Sciences Institute, August 1980.
[RFC791] Postel, J., "Internet Protocol - DARPA Internet Program Protocol Specification", STD 5, RFC791, DARPA, September 1981.
[RFC792] Postel, J., "Internet Control Message Protocol - DARPA Internet Program Protocol Specification", STD 5, RFC792, USC/Information Sciences Institute, September 1981.
[RFC793] Postel, J., "Transmission Control Protocol - DARPA Internet Program Protocol Specification", STD 7, RFC793, USC/Information Sciences Institute, September 1981.
[RFC823] Hinden, R., and A. Sheltzer, "The DARPA Internet Gateway", RFC823, BBN, September 1982.
[RFC869] Hinden, R., "A Host Monitoring Protocol", RFC869, Bolt Beranek and Newman, December 1983.
[RFC888] Seamonson, L., and E. Rosen, "STUB" Exterior Gateway Protocol", RFC888, BBN Communications Corporation, January 1984.
[RFC905] International Standards Organization, "ISO Transport Protocol Specification - ISO DP 8073", RFC905, April 1984.
[RFC908] Velten, D., R. Hinden, and J. Sax, "Reliable Data Protocol", RFC908, BBN Communications Corporation, July 1984.
The Well Known Ports are controlled and assigned by the IANA and on most systems can only be used by system (or root) processes or by programs executed by privileged users.
Ports are used in the TCP [RFC793] to name the ends of logical connections which carry long term conversations. For the purpose of providing services to unknown callers, a service contact port is defined. This list specifies the port used by the server process as its contact port. The contact port is sometimes called the "well-known port".
To the extent possible, these same port assignments are used with the UDP [RFC768].
The assigned ports use a small portion of the possible port numbers. For many years the assigned ports were in the range 0-255. Recently, the range for assigned ports managed by the IANA has been expanded to the range 0-1023.
Port Assignments:
Keyword Decimal Description References ------- ------- ----------- ---------- 0/tcp Reserved 0/udp Reserved # Jon Postel <postel@isi.edu> tcpmux 1/tcp TCP Port Service Multiplexer tcpmux 1/udp TCP Port Service Multiplexer # Mark Lottor <MKL@nisc.sri.com> compressnet 2/tcp Management Utility compressnet 2/udp Management Utility compressnet 3/tcp Compression Process compressnet 3/udp Compression Process # Bernie Volz <VOLZ@PROCESS.COM> # 4/tcp Unassigned # 4/udp Unassigned rje 5/tcp Remote Job Entry rje 5/udp Remote Job Entry # Jon Postel <postel@isi.edu> # 6/tcp Unassigned # 6/udp Unassigned echo 7/tcp Echo echo 7/udp Echo # Jon Postel <postel@isi.edu> # 8/tcp Unassigned
# 15/udp Unassigned # 16/tcp Unassigned # 16/udp Unassigned qotd 17/tcp Quote of the Day qotd 17/udp Quote of the Day # Jon Postel <postel@isi.edu> msp 18/tcp Message Send Protocol msp 18/udp Message Send Protocol # Rina Nethaniel <---none---> chargen 19/tcp Character Generator chargen 19/udp Character Generator ftp-data 20/tcp File Transfer [Default Data] ftp-data 20/udp File Transfer [Default Data] ftp 21/tcp File Transfer [Control] ftp 21/udp File Transfer [Control] # Jon Postel <postel@isi.edu> # 22/tcp Unassigned # 22/udp Unassigned telnet 23/tcp Telnet telnet 23/udp Telnet # Jon Postel <postel@isi.edu> 24/tcp any private mail system 24/udp any private mail system # Rick Adam <rick@UUNET.UU.NET> smtp 25/tcp Simple Mail Transfer smtp 25/udp Simple Mail Transfer # Jon Postel <postel@isi.edu> # 26/tcp Unassigned # 26/udp Unassigned nsw-fe 27/tcp NSW User System FE nsw-fe 27/udp NSW User System FE
# Robert Thomas <BThomas@F.BBN.COM> # 28/tcp Unassigned # 28/udp Unassigned msg-icp 29/tcp MSG ICP msg-icp 29/udp MSG ICP # Robert Thomas <BThomas@F.BBN.COM> # 30/tcp Unassigned # 30/udp Unassigned msg-auth 31/tcp MSG Authentication msg-auth 31/udp MSG Authentication # Robert Thomas <BThomas@F.BBN.COM> # 32/tcp Unassigned # 32/udp Unassigned dsp 33/tcp Display Support Protocol dsp 33/udp Display Support Protocol # Ed Cain <cain@edn-unix.dca.mil> # 34/tcp Unassigned # 34/udp Unassigned 35/tcp any private printer server 35/udp any private printer server # Jon Postel <postel@isi.edu> # 36/tcp Unassigned # 36/udp Unassigned time 37/tcp Time time 37/udp Time # Jon Postel <postel@isi.edu> rap 38/tcp Route access Protocol rap 38/udp Route Access Protocol # Robert Ullmann <ariel@world.std.com> rlp 39/tcp Resource Location Protocol rlp 39/udp Resource Location Protocol # Mike Accetta <MIKE.ACCETTA@CMU-CS-A.EDU> # 40/tcp Unassigned # 40/udp Unassigned graphics 41/tcp Graphics graphics 41/udp Graphics nameserver 42/tcp Host Name Server nameserver 42/udp Host Name Server nicname 43/tcp Who Is nicname 43/udp Who Is mpm-flags 44/tcp MPM FLAGS Protocol mpm-flags 44/udp MPM FLAGS Protocol mpm 45/tcp Message Processing Module [recv] mpm 45/udp Message Processing Module [recv] mpm-snd 46/tcp MPM [default send] mpm-snd 46/udp MPM [default send] # Jon Postel <postel@isi.edu> ni-ftp 47/tcp NI FTP
ni-ftp 47/udp NI FTP # Steve Kille <S.Kille@isode.com>
auditd 48/tcp Digital Audit Daemon auditd 48/udp Digital Audit Daemon # Larry Scott <scott@zk3.dec.com> login 49/tcp Login Host Protocol login 49/udp Login Host Protocol # Pieter Ditmars <pditmars@BBN.COM> re-mail-ck 50/tcp Remote Mail Checking Protocol re-mail-ck 50/udp Remote Mail Checking Protocol # Steve Dorner <s-dorner@UIUC.EDU> la-maint 51/tcp IMP Logical Address Maintenance la-maint 51/udp IMP Logical Address Maintenance # Andy Malis <malis_a@timeplex.com> xns-time 52/tcp XNS Time Protocol xns-time 52/udp XNS Time Protocol # Susie Armstrong <Armstrong.wbst128@XEROX> domain 53/tcp Domain Name Server domain 53/udp Domain Name Server # Paul Mockapetris <PVM@ISI.EDU> xns-ch 54/tcp XNS Clearinghouse xns-ch 54/udp XNS Clearinghouse # Susie Armstrong <Armstrong.wbst128@XEROX> isi-gl 55/tcp ISI Graphics Language isi-gl 55/udp ISI Graphics Language xns-auth 56/tcp XNS Authentication xns-auth 56/udp XNS Authentication # Susie Armstrong <Armstrong.wbst128@XEROX> 57/tcp any private terminal access 57/udp any private terminal access # Jon Postel <postel@isi.edu> xns-mail 58/tcp XNS Mail xns-mail 58/udp XNS Mail # Susie Armstrong <Armstrong.wbst128@XEROX> 59/tcp any private file service 59/udp any private file service # Jon Postel <postel@isi.edu> 60/tcp Unassigned 60/udp Unassigned ni-mail 61/tcp NI MAIL ni-mail 61/udp NI MAIL # Steve Kille <S.Kille@isode.com> acas 62/tcp ACA Services acas 62/udp ACA Services # E. Wald <ewald@via.enet.dec.com> # 63/tcp Unassigned # 63/udp Unassigned covia 64/tcp Communications Integrator (CI)
covia 64/udp Communications Integrator (CI) # "Tundra" Tim Daneliuk # <tundraix!tundra@clout.chi.il.us> tacacs-ds 65/tcp TACACS-Database Service tacacs-ds 65/udp TACACS-Database Service # Kathy Huber <khuber@bbn.com> sql*net 66/tcp Oracle SQL*NET sql*net 66/udp Oracle SQL*NET # Jack Haverty <jhaverty@ORACLE.COM> bootps 67/tcp Bootstrap Protocol Server bootps 67/udp Bootstrap Protocol Server bootpc 68/tcp Bootstrap Protocol Client bootpc 68/udp Bootstrap Protocol Client # Bill Croft <Croft@SUMEX-AIM.STANFORD.EDU> tftp 69/tcp Trivial File Transfer tftp 69/udp Trivial File Transfer # David Clark <ddc@LCS.MIT.EDU> gopher 70/tcp Gopher gopher 70/udp Gopher # Mark McCahill <mpm@boombox.micro.umn.edu> netrjs-1 71/tcp Remote Job Service netrjs-1 71/udp Remote Job Service netrjs-2 72/tcp Remote Job Service netrjs-2 72/udp Remote Job Service netrjs-3 73/tcp Remote Job Service netrjs-3 73/udp Remote Job Service netrjs-4 74/tcp Remote Job Service netrjs-4 74/udp Remote Job Service # Bob Braden <Braden@ISI.EDU>
75/tcp any private dial out service 75/udp any private dial out service # Jon Postel <postel@isi.edu> deos 76/tcp Distributed External Object Store deos 76/udp Distributed External Object Store # Robert Ullmann <ariel@world.std.com> 77/tcp any private RJE service 77/udp any private RJE service # Jon Postel <postel@isi.edu> vettcp 78/tcp vettcp vettcp 78/udp vettcp # Christopher Leong <leong@kolmod.mlo.dec.com> finger 79/tcp Finger finger 79/udp Finger # David Zimmerman <dpz@RUTGERS.EDU> www-http 80/tcp World Wide Web HTTP www-http 80/udp World Wide Web HTTP # Tim Berners-Lee <timbl@nxoc01.cern.ch> hosts2-ns 81/tcp HOSTS2 Name Server
hosts2-ns 81/udp HOSTS2 Name Server # Earl Killian <EAK@MORDOR.S1.GOV> xfer 82/tcp XFER Utility xfer 82/udp XFER Utility # Thomas M. Smith <tmsmith@esc.syr.ge.com> mit-ml-dev 83/tcp MIT ML Device mit-ml-dev 83/udp MIT ML Device # David Reed <--none---> ctf 84/tcp Common Trace Facility ctf 84/udp Common Trace Facility # Hugh Thomas <thomas@oils.enet.dec.com> mit-ml-dev 85/tcp MIT ML Device mit-ml-dev 85/udp MIT ML Device # David Reed <--none---> mfcobol 86/tcp Micro Focus Cobol mfcobol 86/udp Micro Focus Cobol # Simon Edwards <--none---> 87/tcp any private terminal link 87/udp any private terminal link # Jon Postel <postel@isi.edu> kerberos 88/tcp Kerberos kerberos 88/udp Kerberos # B. Clifford Neuman <bcn@isi.edu> su-mit-tg 89/tcp SU/MIT Telnet Gateway su-mit-tg 89/udp SU/MIT Telnet Gateway # Mark Crispin <MRC@PANDA.COM> dnsix 90/tcp DNSIX Securit Attribute Token Map dnsix 90/udp DNSIX Securit Attribute Token Map # Charles Watt <watt@sware.com> mit-dov 91/tcp MIT Dover Spooler mit-dov 91/udp MIT Dover Spooler # Eliot Moss <EBM@XX.LCS.MIT.EDU> npp 92/tcp Network Printing Protocol npp 92/udp Network Printing Protocol # Louis Mamakos <louie@sayshell.umd.edu> dcp 93/tcp Device Control Protocol dcp 93/udp Device Control Protocol # Daniel Tappan <Tappan@BBN.COM> objcall 94/tcp Tivoli Object Dispatcher objcall 94/udp Tivoli Object Dispatcher # Tom Bereiter <--none---> supdup 95/tcp SUPDUP supdup 95/udp SUPDUP # Mark Crispin <MRC@PANDA.COM> dixie 96/tcp DIXIE Protocol Specification dixie 96/udp DIXIE Protocol Specification # Tim Howes <Tim.Howes@terminator.cc.umich.edu> swift-rvf 97/tcp Swift Remote Vitural File Protocol
swift-rvf 97/udp Swift Remote Vitural File Protocol # Maurice R. Turcotte # <mailrus!uflorida!rm1!dnmrt%rmatl@uunet.UU.NET> tacnews 98/tcp TAC News tacnews 98/udp TAC News # Jon Postel <postel@isi.edu> metagram 99/tcp Metagram Relay
metagram 99/udp Metagram Relay # Geoff Goodfellow <Geoff@FERNWOOD.MPK.CA.U> newacct 100/tcp [unauthorized use] hostname 101/tcp NIC Host Name Server hostname 101/udp NIC Host Name Server # Jon Postel <postel@isi.edu> iso-tsap 102/tcp ISO-TSAP iso-tsap 102/udp ISO-TSAP # Marshall Rose <mrose@dbc.mtview.ca.us> gppitnp 103/tcp Genesis Point-to-Point Trans Net gppitnp 103/udp Genesis Point-to-Point Trans Net acr-nema 104/tcp ACR-NEMA Digital Imag. & Comm. 300 acr-nema 104/udp ACR-NEMA Digital Imag. & Comm. 300 # Patrick McNamee <--none---> csnet-ns 105/tcp Mailbox Name Nameserver csnet-ns 105/udp Mailbox Name Nameserver # Marvin Solomon <solomon@CS.WISC.EDU> 3com-tsmux 106/tcp 3COM-TSMUX 3com-tsmux 106/udp 3COM-TSMUX # Jeremy Siegel <jzs@NSD.3Com.COM> rtelnet 107/tcp Remote Telnet Service rtelnet 107/udp Remote Telnet Service # Jon Postel <postel@isi.edu> snagas 108/tcp SNA Gateway Access Server snagas 108/udp SNA Gateway Access Server # Kevin Murphy <murphy@sevens.lkg.dec.com> pop2 109/tcp Post Office Protocol - Version 2 pop2 109/udp Post Office Protocol - Version 2 # Joyce K. Reynolds <jkrey@isi.edu> pop3 110/tcp Post Office Protocol - Version 3 pop3 110/udp Post Office Protocol - Version 3 # Marshall Rose <mrose@dbc.mtview.ca.us> sunrpc 111/tcp SUN Remote Procedure Call sunrpc 111/udp SUN Remote Procedure Call # Chuck McManis <cmcmanis@sun.com> mcidas 112/tcp McIDAS Data Transmission Protocol mcidas 112/udp McIDAS Data Transmission Protocol # Glenn Davis <davis@unidata.ucar.edu> auth 113/tcp Authentication Service auth 113/udp Authentication Service # Mike St. Johns <stjohns@arpa.mil>
audionews 114/tcp Audio News Multicast audionews 114/udp Audio News Multicast # Martin Forssen <maf@dtek.chalmers.se> sftp 115/tcp Simple File Transfer Protocol sftp 115/udp Simple File Transfer Protocol # Mark Lottor <MKL@nisc.sri.com> ansanotify 116/tcp ANSA REX Notify ansanotify 116/udp ANSA REX Notify # Nicola J. Howarth <njh@ansa.co.uk> uucp-path 117/tcp UUCP Path Service uucp-path 117/udp UUCP Path Service sqlserv 118/tcp SQL Services sqlserv 118/udp SQL Services # Larry Barnes <barnes@broke.enet.dec.com> nntp 119/tcp Network News Transfer Protocol nntp 119/udp Network News Transfer Protocol # Phil Lapsley <phil@UCBARPA.BERKELEY.EDU> cfdptkt 120/tcp CFDPTKT cfdptkt 120/udp CFDPTKT # John Ioannidis <ji@close.cs.columbia.ed> erpc 121/tcp Encore Expedited Remote Pro.Call erpc 121/udp Encore Expedited Remote Pro.Call # Jack O'Neil <---none--->
smakynet 122/tcp SMAKYNET smakynet 122/udp SMAKYNET # Mike O'Dowd <odowd@ltisun8.epfl.ch> ntp 123/tcp Network Time Protocol ntp 123/udp Network Time Protocol # Dave Mills <Mills@HUEY.UDEL.EDU> ansatrader 124/tcp ANSA REX Trader ansatrader 124/udp ANSA REX Trader # Nicola J. Howarth <njh@ansa.co.uk> locus-map 125/tcp Locus PC-Interface Net Map Ser locus-map 125/udp Locus PC-Interface Net Map Ser # Eric Peterson <lcc.eric@SEAS.UCLA.EDU> unitary 126/tcp Unisys Unitary Login unitary 126/udp Unisys Unitary Login # <feil@kronos.nisd.cam.unisys.com> locus-con 127/tcp Locus PC-Interface Conn Server locus-con 127/udp Locus PC-Interface Conn Server # Eric Peterson <lcc.eric@SEAS.UCLA.EDU> gss-xlicen 128/tcp GSS X License Verification gss-xlicen 128/udp GSS X License Verification # John Light <johnl@gssc.gss.com> pwdgen 129/tcp Password Generator Protocol pwdgen 129/udp Password Generator Protocol # Frank J. Wacho <WANCHO@WSMR-SIMTEL20.ARMY.MIL> cisco-fna 130/tcp cisco FNATIVE
cisco-fna 130/udp cisco FNATIVE cisco-tna 131/tcp cisco TNATIVE cisco-tna 131/udp cisco TNATIVE cisco-sys 132/tcp cisco SYSMAINT cisco-sys 132/udp cisco SYSMAINT statsrv 133/tcp Statistics Service statsrv 133/udp Statistics Service # Dave Mills <Mills@HUEY.UDEL.EDU> ingres-net 134/tcp INGRES-NET Service ingres-net 134/udp INGRES-NET Service # Mike Berrow <---none---> loc-srv 135/tcp Location Service loc-srv 135/udp Location Service # Joe Pato <apollo!pato@EDDIE.MIT.EDU> profile 136/tcp PROFILE Naming System profile 136/udp PROFILE Naming System # Larry Peterson <llp@ARIZONA.EDU> netbios-ns 137/tcp NETBIOS Name Service netbios-ns 137/udp NETBIOS Name Service netbios-dgm 138/tcp NETBIOS Datagram Service netbios-dgm 138/udp NETBIOS Datagram Service netbios-ssn 139/tcp NETBIOS session Service netbios-ssn 139/udp NETBIOS Session Service # Jon Postel <postel@isi.edu> emfis-data 140/tcp EMFIS Data Service emfis-data 140/udp EMFIS Data Service emfis-cntl 141/tcp EMFIS Control Service emfis-cntl 141/udp EMFIS Control Service # Gerd Beling <GBELING@ISI.EDU> bl-idm 142/tcp Britton-Lee IDM bl-idm 142/udp Britton-Lee IDM # Susie Snitzer <---none---> imap2 143/tcp Interim Mail Access Protocol v2 imap2 143/udp Interim Mail Access Protocol v2 # Mark Crispin <MRC@PANDA.COM> news 144/tcp NewS news 144/udp NewS # James Gosling <JAG@SUN.COM> uaac 145/tcp UAAC Protocol uaac 145/udp UAAC Protocol # David A. Gomberg <gomberg@GATEWAY.MITRE.ORG> iso-tp0 146/tcp ISO-IP0 iso-tp0 146/udp ISO-IP0 iso-ip 147/tcp ISO-IP iso-ip 147/udp ISO-IP # Marshall Rose <mrose@dbc.mtview.ca.us>
# Bill Davidson <billd@equalizer.cray.com> https 443/tcp https MCom https 443/udp https MCom # Kipp E.B. Hickman <kipp@mcom.com> snpp 444/tcp Simple Network Paging Protocol snpp 444/udp Simple Network Paging Protocol # [RFC1568] microsoft-ds 445/tcp Microsoft-DS microsoft-ds 445/udp Microsoft-DS # Arnold Miller <arnoldm@microsoft.com> ddm-rdb 446/tcp DDM-RDB ddm-rdb 446/udp DDM-RDB ddm-dfm 447/tcp DDM-RFM ddm-dfm 447/udp DDM-RFM ddm-byte 448/tcp DDM-BYTE ddm-byte 448/udp DDM-BYTE # Jan David Fisher <jdfisher@VNET.IBM.COM> as-servermap 449/tcp AS Server Mapper as-servermap 449/udp AS Server Mapper # Barbara Foss <BGFOSS@rchvmv.vnet.ibm.com> tserver 450/tcp TServer tserver 450/udp TServer # Harvey S. Schultz <hss@mtgzfs3.mt.att.com> # 451-511 Unassigned exec 512/tcp remote process execution; # authentication performed using # passwords and UNIX loppgin names biff 512/udp used by mail system to notify users # of new mail received; currently # receives messages only from # processes on the same machine login 513/tcp remote login a la telnet; # automatic authentication performed # based on priviledged port numbers # and distributed data bases which # identify "authentication domains" who 513/udp maintains data bases showing who's # logged in to machines on a local # net and the load average of the # machine cmd 514/tcp like exec, but automatic # authentication is performed as for # login server
syslog 514/udp printer 515/tcp spooler printer 515/udp spooler # 516/tcp Unassigned # 516/udp Unassigned talk 517/tcp like tenex link, but across # machine - unfortunately, doesn't # use link protocol (this is actually # just a rendezvous port from which a # tcp connection is established) talk 517/udp like tenex link, but across # machine - unfortunately, doesn't # use link protocol (this is actually # just a rendezvous port from which a tcp connection is established) ntalk 518/tcp ntalk 518/udp utime 519/tcp unixtime utime 519/udp unixtime efs 520/tcp extended file name server router 520/udp local routing process (on site); # uses variant of Xerox NS routing # information protocol # 521-524 Unassigned timed 525/tcp timeserver timed 525/udp timeserver tempo 526/tcp newdate tempo 526/udp newdate # 527-529 Unassigned courier 530/tcp rpc courier 530/udp rpc conference 531/tcp chat conference 531/udp chat netnews 532/tcp readnews netnews 532/udp readnews netwall 533/tcp for emergency broadcasts netwall 533/udp for emergency broadcasts # 534-538 Unassigned apertus-ldp 539/tcp Apertus Technologies Load Determination apertus-ldp 539/udp Apertus Technologies Load Determination uucp 540/tcp uucpd uucp 540/udp uucpd uucp-rlogin 541/tcp uucp-rlogin Stuart Lynne
The Registered Ports are not controlled by the IANA and on most systems can be used by ordinary user processes or programs executed by ordinary users.
Ports are used in the TCP [RFC793] to name the ends of logical connections which carry long term conversations. For the purpose of providing services to unknown callers, a service contact port is defined. This list specifies the port used by the server process as its contact port. While the IANA can not control uses of these ports it does register or list uses of these ports as a convienence to the community.
To the extent possible, these same port assignments are used with the UDP [RFC768].
The Registered Ports are in the range 1024-65535.
Port Assignments:
Keyword Decimal Description References ------- ------- ----------- ---------- 1024/tcp Reserved 1024/udp Reserved # IANA <iana@isi.edu> blackjack 1025/tcp network blackjack blackjack 1025/udp network blackjack iad1 1030/tcp BBN IAD iad1 1030/udp BBN IAD iad2 1031/tcp BBN IAD iad2 1031/udp BBN IAD iad3 1032/tcp BBN IAD iad3 1032/udp BBN IAD # Andy Malis <malis_a@timeplex.com> instl_boots 1067/tcp Installation Bootstrap Proto. Serv. instl_boots 1067/udp Installation Bootstrap Proto. Serv. instl_bootc 1068/tcp Installation Bootstrap Proto. Cli.
instl_bootc 1068/udp Installation Bootstrap Proto. Cli. # David Arko <<darko@hpfcrn.fc.hp.com>
socks 1080/tcp Socks socks 1080/udp Socks # Ying-Da Lee <ylee@syl.dl.nec.com ansoft-lm-1 1083/tcp Anasoft License Manager ansoft-lm-1 1083/udp Anasoft License Manager ansoft-lm-2 1084/tcp Anasoft License Manager ansoft-lm-2 1084/udp Anasoft License Manager nfa 1155/tcp Network File Access nfa 1155/udp Network File Access # James Powell <james@mailhost.unidata.com> nerv 1222/tcp SNI R&D network nerv 1222/udp SNI R&D network # Martin Freiss <freiss.pad@sni.de> hermes 1248/tcp hermes 1248/udp alta-ana-lm 1346/tcp Alta Analytics License Manager alta-ana-lm 1346/udp Alta Analytics License Manager bbn-mmc 1347/tcp multi media conferencing bbn-mmc 1347/udp multi media conferencing bbn-mmx 1348/tcp multi media conferencing bbn-mmx 1348/udp multi media conferencing sbook 1349/tcp Registration Network Protocol sbook 1349/udp Registration Network Protocol editbench 1350/tcp Registration Network Protocol editbench 1350/udp Registration Network Protocol # Simson L. Garfinkel <simsong@next.cambridge.ma.us> equationbuilder 1351/tcp Digital Tool Works (MIT) equationbuilder 1351/udp Digital Tool Works (MIT) # Terrence J. Talbot <lexcube!tjt@bu.edu> lotusnote 1352/tcp Lotus Note lotusnote 1352/udp Lotus Note # Greg Pflaum <iris.com!Greg_Pflaum@uunet.uu.net> relief 1353/tcp Relief Consulting relief 1353/udp Relief Consulting # John Feiler <relief!jjfeiler@uu2.psi.com> rightbrain 1354/tcp RightBrain Software rightbrain 1354/udp RightBrain Software # Glenn Reid <glann@rightbrain.com> intuitive edge 1355/tcp Intuitive Edge intuitive edge 1355/udp Intuitive Edge # Montgomery Zukowski # <monty@nextnorth.acs.ohio-state.edu> cuillamartin 1356/tcp CuillaMartin Company cuillamartin 1356/udp CuillaMartin Company pegboard 1357/tcp Electronic PegBoard pegboard 1357/udp Electronic PegBoard
