Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-08-17
- Expert(s)
-
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, and Michael Scharf SCTP: Michael Tuexen DCCP: Eddie Kohler and Yoshifumi Nishida
- Reference
- [RFC6335]
- Note
-
Service names and port numbers are used to distinguish between different services that run over transport protocols such as TCP, UDP, DCCP, and SCTP. Service names are assigned on a first-come, first-served process, as documented in [RFC6335]. Port numbers are assigned in various ways, based on three ranges: System Ports (0-1023), User Ports (1024-49151), and the Dynamic and/or Private Ports (49152-65535); the different uses of these ranges are described in [RFC6335]. According to Section 8.1.2 of [RFC6335], System Ports are assigned by the "IETF Review" or "IESG Approval" procedures described in [RFC8126]. User Ports are assigned by IANA using the "IETF Review" process, the "IESG Approval" process, or the "Expert Review" process, as per [RFC6335]. Dynamic Ports are not assigned. The registration procedures for service names and port numbers are described in [RFC6335]. Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration. ************************************************************************ * PLEASE NOTE THE FOLLOWING: * * * * ASSIGNMENT OF A PORT NUMBER DOES NOT IN ANY WAY IMPLY AN * * ENDORSEMENT OF AN APPLICATION OR PRODUCT, AND THE FACT THAT NETWORK * * TRAFFIC IS FLOWING TO OR FROM A REGISTERED PORT DOES NOT MEAN THAT * * IT IS "GOOD" TRAFFIC, NOR THAT IT NECESSARILY CORRESPONDS TO THE * * ASSIGNED SERVICE. FIREWALL AND SYSTEM ADMINISTRATORS SHOULD * * CHOOSE HOW TO CONFIGURE THEIR SYSTEMS BASED ON THEIR KNOWLEDGE OF * * THE TRAFFIC IN QUESTION, NOT WHETHER THERE IS A PORT NUMBER * * REGISTERED OR NOT. * ************************************************************************
- Request an Assignment
-
[https://www.iana.org/protocols/apply]
- Available Formats
-

CSV
XML
HTML
Plain text
| Service Name | Port Number | Transport Protocol | Description | Assignee | Contact | Registration Date | Modification Date | Reference | Service Code | Unauthorized Use Reported | Assignment Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|
| h323hostcall | 1720 | tcp | H.323 Call Control Signalling | [ITU-T] | [ITU-T_TSB] | 2013-01-31 | |||||
| h323hostcall | 1720 | udp | H.323 Call Control Signalling | [ITU-T] | [ITU-T_TSB] | 2013-01-31 | |||||
| h323hostcall | 1720 | sctp | H.323 Call Control | [ITU-T] | 2014-07-30 | ||||||
| wkars | 2720 | tcp | wkars | [Barry_Shelton] | [Barry_Shelton] | ||||||
| wkars | 2720 | udp | wkars | [Barry_Shelton] | [Barry_Shelton] | ||||||
| ufastro-instr | 3720 | tcp | UF Astro. Instr. Services | [David_B_Hon] | [David_B_Hon] | 2003-03 | |||||
| ufastro-instr | 3720 | udp | UF Astro. Instr. Services | [David_B_Hon] | [David_B_Hon] | 2003-03 | |||||
| ms-licensing | 5720 | tcp | MS-Licensing | [Thomas_Lindeman] | [Thomas_Lindeman] | 2002-11 | |||||
| ms-licensing | 5720 | udp | MS-Licensing | [Thomas_Lindeman] | [Thomas_Lindeman] | 2002-11 | |||||
| fodms | 7200 | tcp | FODMS FLIP | [David_Anthony] | [David_Anthony] | ||||||
| fodms | 7200 | udp | FODMS FLIP | [David_Anthony] | [David_Anthony] | ||||||
| dlip | 7201 | tcp | DLIP | [Albert_Manfredi] | [Albert_Manfredi] | ||||||
| dlip | 7201 | udp | DLIP | [Albert_Manfredi] | [Albert_Manfredi] | ||||||
| pon-ictp | 7202 | tcp | Inter-Channel Termination Protocol (ICTP) for multi-wavelength PON (Passive Optical Network) systems | [Broadband_Forum] | [Broadband_Forum] | 2017-02-22 | 2019-12-16 | [TR-352][Inter-Channel-Termination protocol (ICTP) is a peer-to-peer protocol with a binary message format that is used by a set of optical line terminal (OLT) channel terminations (CT) comprising a 40-Gigabit-capable next-generation passive optical network (NG-PON2) system to exchange channel profile configuration and status information and to coordinate the operation of tunable optical network units (ONUs) in a multi-wavelength channel environment.] | |||
| 7202 | udp | Reserved | |||||||||
| 7203-7214 | Unassigned | ||||||||||
| medimageportal | 7720 | tcp | MedImage Portal | [Robert_Helton] | [Robert_Helton] | 2003-10 | |||||
| medimageportal | 7720 | udp | MedImage Portal | [Robert_Helton] | [Robert_Helton] | 2003-10 | |||||
| h323callsigalt | 11720 | tcp | H.323 Call Control Signalling Alternate | [ITU-T] | [ITU-T_TSB] | 2013-01-31 | |||||
| h323callsigalt | 11720 | udp | H.323 Call Control Signalling Alternate | [ITU-T] | [ITU-T_TSB] | 2013-01-31 | |||||
| bprd | 13720 | tcp | BPRD Protocol (VERITAS NetBackup) | [Jeff_Holmbeck] | [Jeff_Holmbeck] | ||||||
| bprd | 13720 | udp | BPRD Protocol (VERITAS NetBackup) | [Jeff_Holmbeck] | [Jeff_Holmbeck] |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Albert_Manfredi] | Albert Manfredi | mailto:manfredi&engr05.comsys.rockwell.com | ||
| [Barry_Shelton] | Barry Shelton | mailto:bshelton&wirelessknowledge.com | ||
| [Broadband_Forum] | Broadband Forum | mailto:help&broadband-forum.org | 2020-03-17 | |
| [David_Anthony] | David Anthony | mailto:anthony&power.amasd.anatcp.rockwell.com | ||
| [David_B_Hon] | David B. Hon | mailto:hon&astro.ufl.edu | 2003-03 | |
| [ITU-T] | ITU-T | mailto:tsbsg16&itu.int | 2013-01-31 | |
| [ITU-T_TSB] | ITU-T TSB | ITU-T | mailto:tsbsg16&itu.int | 2013-01-31 |
| [Jeff_Holmbeck] | Jeff Holmbeck | mailto:Jeff.Holmbeck&veritas.com | ||
| [Robert_Helton] | Robert Helton | mailto:bob_helton&medimage.com | 2003-10 | |
| [Thomas_Lindeman] | Thomas Lindeman | mailto:tlindeµsoft.com | 2002-11 |