Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-04-30
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
ahsp | 4333 | tcp | ArrowHead Service Protocol (AHSP) | [QuantuMatriX_Technologies] | [Matthew_Schultz] | 2014-04-10 | |||||
ahsp | 4333 | udp | ArrowHead Service Protocol (AHSP) | [QuantuMatriX_Technologies] | [Matthew_Schultz] | 2014-04-10 | |||||
ahsp | 4333 | sctp | ArrowHead Service Protocol (AHSP) | [QuantuMatriX_Technologies] | [Matthew_Schultz] | 2014-04-10 | |||||
matrix-vnet | 4360 | tcp | Matrix VNet Communication Protocol IANA assigned this well-formed service name as a replacement for "matrix_vnet". |
[Rehan_Mahmood] | [Rehan_Mahmood] | 2009-03-18 | |||||
matrix_vnet | 4360 | tcp | Matrix VNet Communication Protocol | [Rehan_Mahmood] | [Rehan_Mahmood] | 2009-03-18 | This entry is an alias to "matrix-vnet". This entry is now historic, not usable for use with many common service discovery mechanisms. | ||||
mcp | 4458 | tcp | Matrix Configuration Protocol | [Tim_DeBaillie] | [Tim_DeBaillie] | 2006-12 | |||||
mcp | 4458 | udp | Matrix Configuration Protocol | [Tim_DeBaillie] | [Tim_DeBaillie] | 2006-12 | |||||
mtl8000-matrix | 8115 | tcp | MTL8000 Matrix | [David_Pinch] | [David_Pinch] | 2002-04 | |||||
mtl8000-matrix | 8115 | udp | MTL8000 Matrix | [David_Pinch] | [David_Pinch] | 2002-04 | |||||
matrix-fed | 8448 | tcp | Matrix Federation Protocol | [The_Matrix.org_Foundation_C.I.C.] | [Travis_Ralston] | 2023-08-04 | |||||
matrix | MATRIX Remote AV Switching | [Ken_Jibiki] | [Ken_Jibiki] | Defined TXT keys: None | |||||||
mxs | MatrixStore | [Object_Matrix] | [Object_Matrix] | Defined TXT keys: None mxs.system.id=<system id> mxs.system.version=<system layer version> mxs.cluster.id=<cluster id the system belongs to> |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[David_Pinch] | David Pinch | mailto:dpinch&mtl-inst.com | 2002-04 | |
[Ken_Jibiki] | Ken Jibiki | mailto:ken&kenjij.com | ||
[Matthew_Schultz] | Matthew Schultz | QuantuMatriX Technologies | mailto:matt&qmxtech.com | 2014-04-10 |
[Object_Matrix] | Object Matrix | mailto:support&object-matrix.com | ||
[QuantuMatriX_Technologies] | QuantuMatriX Technologies | mailto:admin&qmxtech.com | 2014-04-10 | |
[Rehan_Mahmood] | Rehan Mahmood | mailto:rehan&matrixmultimedia.co.uk | 2009-03-18 | |
[The_Matrix.org_Foundation_C.I.C.] | The Matrix.org Foundation C.I.C. | mailto:matrix&matrix.org | 2023-08-04 | |
[Tim_DeBaillie] | Tim DeBaillie | mailto:debaillie&ciholas.com | 2006-12 | |
[Travis_Ralston] | Travis Ralston | The Matrix.org Foundation C.I.C. | mailto:travisr&matrix.org | 2023-08-04 |