Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-11-19
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
socks | 1080 | tcp | Socks | [Ying_Da_Lee] | [Ying_Da_Lee] | ||||||
socks | 1080 | udp | Socks | [Ying_Da_Lee] | [Ying_Da_Lee] | ||||||
gap | 10800 | tcp | Gestor de Acaparamiento para Pocket PCs | [Juan_Carlos_Olivares] | [Juan_Carlos_Olivares] | 2006-03 | |||||
gap | 10800 | udp | Gestor de Acaparamiento para Pocket PCs | [Juan_Carlos_Olivares] | [Juan_Carlos_Olivares] | 2006-03 | |||||
10801-10804 | Unassigned | ||||||||||
lpdg | 10805 | tcp | LUCIA Pareja Data Group | [Alvaro_P_Dominguez] | [Alvaro_P_Dominguez] | 2006-02 | |||||
lpdg | 10805 | udp | LUCIA Pareja Data Group | [Alvaro_P_Dominguez] | [Alvaro_P_Dominguez] | 2006-02 | |||||
10806-10808 | Unassigned | ||||||||||
nbd | 10809 | tcp | Network Block Device | [Wouter_Verhelst] | [Wouter_Verhelst] | 2010-08-02 | 2024-04-30 | [https://github.com/NetworkBlockDevice/nbd/blob/master/doc/proto.md] | |||
10809 | udp | Reserved |
Contact Information
ID | Name | Contact URI | Last Updated |
---|---|---|---|
[Alvaro_P_Dominguez] | Alvaro P. Dominguez | mailto:alpado&gmail.com | 2006-02 |
[Juan_Carlos_Olivares] | Juan Carlos Olivares Rojas | mailto:jcolivares04c&cenidet.edu.mx | 2006-03 |
[Wouter_Verhelst] | Wouter Verhelst | mailto:w&uter.be | 2010-08-02 |
[Ying_Da_Lee] | Ying-Da Lee | mailto:ylee&syl.dl.nec.com |