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
iris-xpcs 714 tcp IRIS over XPCS [RFC4992]
iris-xpcs 714 udp IRIS over XPCS [RFC4992]
iscsi 860 tcp iSCSI [IESG] [IETF_Chair] 2013-08-27 [RFC7143]
iscsi 860 udp iSCSI [IESG] [IETF_Chair] 2013-08-27 [RFC7143]
sesi-lm 1714 tcp sesi-lm
sesi-lm 1714 udp sesi-lm
raventdm 2714 tcp Raven Trinity Data Mover [Daniel_Sorlov] [Daniel_Sorlov]
raventdm 2714 udp Raven Trinity Data Mover [Daniel_Sorlov] [Daniel_Sorlov]
iscsi-target 3260 tcp iSCSI port [IESG] [IETF_Chair] 2013-08-27 [RFC7143]
iscsi-target 3260 udp iSCSI port [IESG] [IETF_Chair] 2013-08-27 [RFC7143]
delos-dms 3714 tcp DELOS Direct Messaging [Ekkehard_Morgenstern] [Ekkehard_Morgenstern] 2003-03
delos-dms 3714 udp DELOS Direct Messaging [Ekkehard_Morgenstern] [Ekkehard_Morgenstern] 2003-03
prosharevideo 5714 tcp proshare conf video [gunner] [gunner]
prosharevideo 5714 udp proshare conf video [gunner] [gunner]
ibprotocol 6714 tcp Internet Backplane Protocol [Alessandro_Bassi] [Alessandro_Bassi]
ibprotocol 6714 udp Internet Backplane Protocol [Alessandro_Bassi] [Alessandro_Bassi]

Contact Information

ID Name Organization Contact URI Last Updated
[Alessandro_Bassi] Alessandro Bassi mailto:abassi&cs.utk.edu
[Daniel_Sorlov] Daniel Sorlov mailto:Daniel&sorlov.com
[Ekkehard_Morgenstern] Ekkehard Morgenstern mailto:ekkehard&ekkehardmorgenstern.de 2003-03
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[gunner] mailto:gunner&ibeam.intel.com