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 |
---|---|---|---|---|---|---|---|---|---|---|---|
z-wave | 4123 | tcp | Z-Wave Protocol | [Sigma_Designs_Inc_2] | [Anders_Brandt][Mary_Miller] | 2007-02 | 2012-11-08 | ||||
z-wave | 4123 | udp | Z-Wave Protocol | [Sigma_Designs_Inc_2] | [Anders_Brandt][Mary_Miller] | 2007-02 | 2012-11-08 | ||||
z-wave-s | 41230 | tcp | Z-Wave Protocol over SSL/TLS | [Sigma_Designs_3] | [Anders_Brandt_4] | 2015-06-26 | |||||
z-wave-s | 41230 | udp | Z-Wave Protocol over DTLS | [Sigma_Designs_3] | [Anders_Brandt_4] | 2015-06-26 | |||||
41231-41793 | Unassigned | ||||||||||
z-wave-tunnel | 44123 | tcp | Z-Wave Secure Tunnel | [Sigma_Designs_Inc] | [Anders_Brandt_3] | 2012-10-12 | 2015-06-26 | ||||
44123 | udp | Reserved |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[Anders_Brandt] | Anders Brandt | Sigma Designs, Inc. | mailto:Anders_Brandt&sigmadesigns.com | 2012-11-08 |
[Anders_Brandt_3] | Anders Brandt | Sigma Designs | mailto:anders_brandt&sigmadesigns.com | 2012-10-12 |
[Anders_Brandt_4] | Anders Brandt | Sigma Designs | mailto:anders_brandt&sigmadesigns.com | 2015-06-26 |
[Mary_Miller] | Mary Miller | Sigma Designs, Inc. | mailto:Mary_Miller&sigmadesigns.com | 2012-11-08 |
[Sigma_Designs_Inc] | Sigma Designs, Inc. | mailto:anders_brandt&sigmadesigns.com | 2011-10-03 | |
[Sigma_Designs_Inc_2] | Sigma Designs, Inc. | mailto:pr&sdesigns.com | 2012-11-08 | |
[Sigma_Designs_3] | Sigma Designs | mailto:anders_brandt&sigmadesigns.com | 2015-06-26 |