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 |
---|---|---|---|---|---|---|---|---|---|---|---|
submission | 587 | tcp | Message Submission | 2011-11-17 | [RFC6409] | ||||||
submission | 587 | udp | Message Submission | 2011-11-17 | [RFC6409] | ||||||
pra-elmd | 1587 | tcp | pra_elmd IANA assigned this well-formed service name as a replacement for "pra_elmd". |
[Dennis_Mastin] | [Dennis_Mastin] | ||||||
pra_elmd | 1587 | tcp | pra_elmd | [Dennis_Mastin] | [Dennis_Mastin] | This entry is an alias to "pra-elmd". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||
pra-elmd | 1587 | udp | pra_elmd IANA assigned this well-formed service name as a replacement for "pra_elmd". |
[Dennis_Mastin] | [Dennis_Mastin] | ||||||
pra_elmd | 1587 | udp | pra_elmd | [Dennis_Mastin] | [Dennis_Mastin] | This entry is an alias to "pra-elmd". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||
masc | 2587 | tcp | MASC | [Pavlin_Ivanov_Radosl] | [Pavlin_Ivanov_Radosl] | ||||||
masc | 2587 | udp | MASC | [Pavlin_Ivanov_Radosl] | [Pavlin_Ivanov_Radosl] | ||||||
p2pgroup | 3587 | tcp | Peer to Peer Grouping | [Igor_Kostic] | [Igor_Kostic] | 2002-08 | |||||
p2pgroup | 3587 | udp | Peer to Peer Grouping | [Igor_Kostic] | [Igor_Kostic] | 2002-08 | |||||
5587-5596 | Unassigned | ||||||||||
6584-6587 | Unassigned | ||||||||||
7576-7587 | Unassigned |
Contact Information
ID | Name | Contact URI | Last Updated |
---|---|---|---|
[Dennis_Mastin] | Dennis Mastin | mailto:dennis&tasmania.platte.com | |
[Igor_Kostic] | Igor Kostic | mailto:igorkoµsoft.com | 2002-08 |
[Pavlin_Ivanov_Radosl] | Pavlin Ivanov Radoslavov | mailto:pavlin&catarina.usc.edu |