Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-30
- 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
- [RFC 6335]
- 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 [RFC 6335]. 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 [RFC 6335]. According to Section 8.1.2 of [RFC 6335], System Ports are assigned by the "IETF Review" or "IESG Approval" procedures described in [RFC 8126]. User Ports are assigned by IANA using the "IETF Review" process, the "IESG Approval" process, or the "Expert Review" process, as per [RFC 6335]. Dynamic Ports are not assigned. The registration procedures for service names and port numbers are described in [RFC 6335]. 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
TXT
| Service Name | Port Number | Transport Protocol | Description | Assignee | Contact | Registration Date | Modification Date | Reference | Service Code | Unauthorized Use Reported | Assignment Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|
| crinis-hb | 3818 | tcp | Crinis Heartbeat | [Eric_McMurry] | [Eric_McMurry] | 2004-04 | |||||
| crinis-hb | 3818 | udp | Crinis Heartbeat | [Eric_McMurry] | [Eric_McMurry] | 2004-04 | |||||
| dsmcc-config | 13818 | tcp | DSMCC Config | [Tim_Addington] | [Tim_Addington] | [ISO/IEC 13818-6 MPEG-2 DSM-CC] | |||||
| dsmcc-config | 13818 | udp | DSMCC Config | [Tim_Addington] | [Tim_Addington] | [ISO/IEC 13818-6 MPEG-2 DSM-CC] | |||||
| dsmcc-session | 13819 | tcp | DSMCC Session Messages | [Tim_Addington] | [Tim_Addington] | [ISO/IEC 13818-6 MPEG-2 DSM-CC] | |||||
| dsmcc-session | 13819 | udp | DSMCC Session Messages | [Tim_Addington] | [Tim_Addington] | [ISO/IEC 13818-6 MPEG-2 DSM-CC] | |||||
| dsmcc-passthru | 13820 | tcp | DSMCC Pass-Thru Messages | [Tim_Addington] | [Tim_Addington] | [ISO/IEC 13818-6 MPEG-2 DSM-CC] | |||||
| dsmcc-passthru | 13820 | udp | DSMCC Pass-Thru Messages | [Tim_Addington] | [Tim_Addington] | [ISO/IEC 13818-6 MPEG-2 DSM-CC] | |||||
| dsmcc-download | 13821 | tcp | DSMCC Download Protocol | [Tim_Addington] | [Tim_Addington] | [ISO/IEC 13818-6 MPEG-2 DSM-CC] | |||||
| dsmcc-download | 13821 | udp | DSMCC Download Protocol | [Tim_Addington] | [Tim_Addington] | [ISO/IEC 13818-6 MPEG-2 DSM-CC] | |||||
| dsmcc-ccp | 13822 | tcp | DSMCC Channel Change Protocol | [Tim_Addington] | [Tim_Addington] | [ISO/IEC 13818-6 MPEG-2 DSM-CC] | |||||
| dsmcc-ccp | 13822 | udp | DSMCC Channel Change Protocol | [Tim_Addington] | [Tim_Addington] | [ISO/IEC 13818-6 MPEG-2 DSM-CC] |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Eric_McMurry] | Eric McMurry | mailto:emcmurry&crinisnetworks.com | 2004-04 |
| [Tim_Addington] | Tim Addington | mailto:Tim.Addington&sciatl.com |