Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2022-11-22
Expert(s)
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, 
Jana Iyengar, 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
dei-icda 618 tcp DEI-ICDA [David_Turner] [David_Turner]
dei-icda 618 udp DEI-ICDA [David_Turner] [David_Turner]
dssiapi 1265 tcp DSSIAPI [Jim_Turner] [Jim_Turner]
dssiapi 1265 udp DSSIAPI [Jim_Turner] [Jim_Turner]
rtsclient 2501 tcp Resource Tracking system client [Aubrey_Turner] [Aubrey_Turner]
rtsclient 2501 udp Resource Tracking system client [Aubrey_Turner] [Aubrey_Turner]
turn 3478 tcp TURN over TCP 2019-08-02 [RFC8656]
turn 3478 udp TURN over UDP 2019-08-02 [RFC8656]
turns 5349 tcp TURN over TLS 2019-08-02 [RFC8656]
turns 5349 udp TURN over DTLS [IESG] [IETF_Chair] 2019-08-02 [RFC7350] This service name was initially created by [RFC8656].

Contact Information

ID Name Organization Contact URI Last Updated
[Aubrey_Turner] Aubrey Turner mailto:S95525ta%25etsuacad.bitnet@ETSUADMN.ETSU.EDU
[David_Turner] David Turner mailto:digital&quetico.tbaytel.net
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Jim_Turner] Jim Turner mailto:Jim.Turner&asg.com