Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-11-27
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
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 | ||||
usp-ctr-stomp | tcp | USP discovery | [Broadband_Forum] | [Broadband_Forum] | 2017-01-12 | [http://www.broadband-forum.org/assignments] | Defined TXT keys: see www.broadband-forum.org/assignments | ||||
usp-ctr-ws | tcp | USP discovery | [Broadband_Forum] | [Broadband_Forum] | 2017-09-28 | [http://www.broadband-forum.org/assignments] | Defined TXT keys: see www.broadband-forum.org/assignments | ||||
vapix-http | tcp | Indicator for VAPIX support over HTTP | [Axis_Communications] | [Christian_Storm] | 2023-04-18 | Defined TXT keys: https://help.axis.com/en-us/axis-os#axis-bonjour-implementation | |||||
vapix-https | tcp | Indicator for VAPIX support over HTTPS | [Axis_Communications] | [Christian_Storm] | 2023-04-18 | Defined TXT keys: https://help.axis.com/en-us/axis-os#axis-bonjour-implementation | |||||
wdp | tcp | Windows Device Portal | [Microsoft_Corporation_5] | [Hirsch_Singhal] | 2016-03-03 | Defined TXT keys: D (device type), S (https port), A (architecture), T (tags) | |||||
web-xi | tcp | HTTP-based protocol for DAQ devices | [Spectris_plc] | [Carsten_Hansen] | 2019-02-13 | Defined TXT keys: name, version | |||||
wot | tcp | W3C WoT Thing Description or Directory | [W3C_Web_of_Things_Working_Group] | [Kazuyuki_Ashimura] | 2022-11-22 | 2022-12-15 |
Defined TXT keys: td: Absolute pathname of the Thing Description of the Thing or Thing Description of the Thing Description Directory. type: Type of the Thing Description, i.e. "Thing" or "Directory". If omitted, the type is assumed to be Thing. scheme: Scheme part of URL. One of the following values can be specified, with the standard registered URI interpretations [RFC7595]: http (HTTP over TCP),https (HTTP over TLS/TCP), coap+tcp (CoAP over TCP), or coaps+tcp (CoAP over TLS/TCP). If omitted, the scheme is assumed to be http. |
||||
wpl-ers-http | tcp | World Programming repository server | [World_Programming_Limited] | [Thomas_Quarendon] | 2017-03-17 | Defined TXT keys: None | |||||
xul-http | XUL (XML User Interface Language) transported over HTTP | [Eran_Gampel] | [Eran_Gampel] | Defined TXT keys: u=<username> p=<password> path=<path to document> (Same as for _http._tcp) | |||||||
zigbee-bridge | tcp | ZigBee Bridge device | [ZigBee_Alliances_Network_Device_working_group] | [Leslie_Mulder] | 2013-05-28 | Defined TXT keys: see: http://www.zigbee.org/Standards/ZigBeeNetworkDevices | |||||
zigbee-bridge | udp | ZigBee Bridge device | [ZigBee_Alliances_Network_Device_working_group] | [Leslie_Mulder] | 2013-05-28 | Defined TXT keys: see: http://www.zigbee.org/Standards/ZigBeeNetworkDevices | |||||
zigbee-gateway | tcp | ZigBee IP Gateway | [ZigBee_Alliances_Network_Device_working_group] | [Leslie_Mulder] | 2013-05-28 | Defined TXT keys: see: http://www.zigbee.org/Standards/ZigBeeNetworkDevices | |||||
zigbee-gateway | udp | ZigBee IP Gateway | [ZigBee_Alliances_Network_Device_working_group] | [Leslie_Mulder] | 2013-05-28 | Defined TXT keys: see: http://www.zigbee.org/Standards/ZigBeeNetworkDevices |