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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| iafserver | 479 | tcp | iafserver | ||||||||
| iafserver | 479 | udp | iafserver | ||||||||
| dberegister | 1479 | tcp | dberegister | [Brian_Griswold] | [Brian_Griswold] | ||||||
| dberegister | 1479 | udp | dberegister | [Brian_Griswold] | [Brian_Griswold] | ||||||
| ssm-els | 2479 | tcp | SecurSight Event Logging Server (SSL) | [John_Linn] | [John_Linn] | ||||||
| ssm-els | 2479 | udp | SecurSight Event Logging Server (SSL) | [John_Linn] | [John_Linn] | ||||||
| twrpc | 3479 | tcp | 2Wire RPC | [Wire_IANA_Contact] | [Wire_IANA_Contact] | 2002-04 | |||||
| twrpc | 3479 | udp | 2Wire RPC | [Wire_IANA_Contact] | [Wire_IANA_Contact] | 2002-04 | |||||
| 4461-4479 | Unassigned | ||||||||||
| vxlan-gpe | 4790 | udp | Generic Protocol Extension for Virtual eXtensible Local Area Network (VXLAN) | [Lawrence_Kreeger] | [Lawrence_Kreeger] | 2014-08-26 | |||||
| 4790 | tcp | Reserved | |||||||||
| roce | 4791 | udp | IP Routable RocE | [InfiniBand_Trade_Association] | [Diego_Crupnicoff] | 2014-10-17 | |||||
| 4791 | tcp | Reserved | |||||||||
| unified-bus | 4792 | tcp | IP Routable Unified Bus | [Huawei] | [Wei_Pan] | 2022-07-08 | 2023-04-10 | ||||
| unified-bus | 4792 | udp | IP Routable Unified Bus | [Huawei] | [Wei_Pan] | 2022-07-08 | 2023-04-10 | ||||
| 4793 | tcp | Reserved | |||||||||
| uet | 4793 | udp | Ultra Ethernet Transport | [Ultra_Ethernet_Consortium] | [Vivek_Kashyap] | 2025-06-16 | |||||
| 4794 | tcp | Reserved | |||||||||
| veroce | 4794 | udp | veRoCE Transport Protocol | [ByteDance] | [Dai_Huichen] | 2026-03-06 | |||||
| 4795-4799 | Unassigned | ||||||||||
| 6472-6479 | Unassigned | ||||||||||
| 7479-7490 | Unassigned | ||||||||||
| 20223-20479 | Unassigned | ||||||||||
| 47810-47999 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Brian_Griswold] | Brian Griswold | mailto:brian&dancingbear.com | ||
| [ByteDance] | ByteDance | mailto:daihuichen&bytedance.com | 2026-03-06 | |
| [Dai_Huichen] | Dai Huichen | mailto:daihuichen&bytedance.com | 2026-03-06 | |
| [Diego_Crupnicoff] | Diego Crupnicoff (IBTA TWG Chair) | mailto:diego&mellanox.com | 2014-10-17 | |
| [Huawei] | Huawei | mailto:tarzan.pan&huawei.com | 2023-04-10 | |
| [InfiniBand_Trade_Association] | InfiniBand Trade Association (IBTA) | mailto:administration&infinibandta.org | 2014-10-17 | |
| [John_Linn] | John Linn | mailto:jlinn&securitydynamics.com | ||
| [Lawrence_Kreeger] | Lawrence Kreeger | mailto:kreeger&cisco.com | 2013-04-19 | |
| [Ultra_Ethernet_Consortium] | Ultra Ethernet Consortium | mailto:vivek.kashyap&intel.com | 2025-06-16 | |
| [Vivek_Kashyap] | Vivek Kashyap | mailto:vivek.kashyap&intel.com | 2025-06-16 | |
| [Wei_Pan] | Wei Pan | Huawei | mailto:tarzan.pan&huawei.com | 2023-04-10 |
| [Wire_IANA_Contact] | 2Wire IANA Contact | mailto:iana&2wire.com | 2002-04 |