Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-11-22
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
mqtt | 1883 | tcp | Message Queuing Telemetry Transport Protocol | [OASIS] | [Robin_Cover] | 2015-02-10 | |||||
mqtt | 1883 | udp | Message Queuing Telemetry Transport Protocol | [OASIS] | [Robin_Cover] | 2015-02-10 | |||||
secure-mqtt | 8883 | tcp | Secure MQTT | [OASIS] | [Robin_Cover] | 2008-02-27 | 2015-03-06 | ||||
secure-mqtt | 8883 | udp | Secure MQTT | [OASIS] | [Robin_Cover] | 2008-02-27 | 2015-03-06 | ||||
mqtt | IBM MQ Telemetry Transport Broker | [AndySC] | [AndySC] | Defined TXT keys: topics=<open topic to subscribe to for information>, eg topic=/info | |||||||
usp-agt-mqtt | tcp | USP discovery | [Broadband_Forum] | [Broadband_Forum] | 2020-03-17 | [http://www.broadband-forum.org/assignments] | Defined TXT keys: see www.broadband-forum.org/assignments | ||||
usp-ctr-mqtt | tcp | USP discovery | [Broadband_Forum] | [Broadband_Forum] | 2020-03-17 | [http://www.broadband-forum.org/assignments] | Defined TXT keys: see www.broadband-forum.org/assignments |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[AndySC] | AndySC | mailto:AndySC&uk.ibm.com | ||
[Broadband_Forum] | Broadband Forum | mailto:help&broadband-forum.org | 2020-03-17 | |
[OASIS] | OASIS | mailto:robin&oasis-open.org | 2015-02-10 | |
[Robin_Cover] | Robin Cover | OASIS KMIP Technical Committee | mailto:robin&oasis-open.org | 2011-07-25 |