Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-02
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
elvin-server 2916 tcp Elvin Server

IANA assigned this well-formed service name as a replacement for "elvin_server".
elvin_server 2916 tcp Elvin Server This entry is an alias to "elvin-server". This entry is now historic, not usable for use with many common service discovery mechanisms.
elvin-server 2916 udp Elvin Server

IANA assigned this well-formed service name as a replacement for "elvin_server".
elvin_server 2916 udp Elvin Server This entry is an alias to "elvin-server". This entry is now historic, not usable for use with many common service discovery mechanisms.
29119-29166 Unassigned
otmp 29167 tcp ObTools Message Protocol [Paul_Clark] [Paul_Clark] 2006-02
otmp 29167 udp ObTools Message Protocol [Paul_Clark] [Paul_Clark] 2006-02
29168 tcp Reserved
29168 udp Reserved
sbcap 29168 sctp SBcAP in 3GPP [_3GPP_Specifications] [_3GPP_Specifications] 2009-06-11
iuhsctpassoc 29169 sctp HNBAP and RUA Common Association [Dongwook_Kim] [Dongwook_Kim] 2009-09-08 2026-01-23

Contact Information

ID Name Organization Contact URI Last Updated
[Dongwook_Kim] Dongwook Kim 3GPP mailto:dongwook.kim&etsi.org 2026-01-23
[_3GPP_Specifications] Dongwook Kim 3GPP Specifications Manager mailto:dongwook.kim&etsi.org 2026-01-23
[Paul_Clark] Paul Clark mailto:paul&xmill.com 2006-02