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
1 2
Service Name | Port Number | Transport Protocol | Description | Assignee | Contact | Registration Date | Modification Date | Reference | Service Code | Unauthorized Use Reported | Assignment Notes |
---|---|---|---|---|---|---|---|---|---|---|---|
guid | Special service type for resolving by GUID (Globally Unique Identifier) | Defined TXT keys: Varies; Depends on type of service being offered/resolved Although DNS-SD does not recommend or advocate using GUIDs as the primary name of an offered service why not?, it does support use of GUIDs as service names where developers want to use them that way. Typically users do not browse for GUIDs. They are not user-friendly and not very informative. Typically, the service is advertised as usual, using a user-friendly name. One of the TXT record attributes is a GUID for the service instance. Once the user has browsed and chosen the desired service instance via its user-friendly name, the service is resolved, the TXT record is retrieved, and the GUID is stored. A given network service instance is therefore being advertised two ways, for example: <User-Friendly-Name>._ptp._tcp.local <GUID>._guid._tcp.local On subsequent accesses to the service, the GUID-based name is resolved, and that particular service instance is discovered, even if the user has subsequently changed the user-friendly name to something else. Note: Although each different logical service type needs to have its own different DNS-SD service type, all GUID-based names use the same pseudo-type: "_guid._tcp". There is no possibility of name conflict because (by definition) GUIDs are globally unique. | |||||||||
hue | tcp | Philips hue protocol | [Signify] | [Walter_Slegers] | 2017-11-01 | 2019-08-09 | Defined TXT keys: bridgeid, modelid | ||||
jnx-kcsync | tcp | jollys keychain cloud sync protocol | [Patrick_Stein] | [Patrick_Stein] | 2011-10-24 | Defined TXT keys: hash=<40hex characters> salt=<40hex characters> uuid=<40hex characters> Example: hash=5e7580598c0d7064d4fc79faaeb42585e1a675f8 salt=f0164cb3a0c3d7efe75abea8fda86d2d56c8dda9 uuid=db61dc092922252e45bbb264f59147138c7fd5fa | |||||
macfoh-data | udp | MacFOH realtime data | [Shaun_Wexler] | [Shaun_Wexler] | Defined TXT keys: None | ||||||
socketcloud | Socketcloud distributed application framework | [Robert_Goodyear] | [Robert_Goodyear] | Defined TXT keys: system, service, process, context, direction, status, progress, health, directive, flags | |||||||
thing | tcp | Internet of things service discovery | [Aaltronav] | [ICT_Manager] | 2019-10-02 | Defined TXT keys: version, url, location, privacy, support, vendor, about | |||||
thing | udp | Internet of things service discovery | [Aaltronav] | [ICT_Manager] | 2019-10-02 | Defined TXT keys: version, url, location, privacy, support, vendor, about | |||||
voalte2 | tcp | Server location via DNS-SD | [Voalte_Inc] | [John_Simpson] | 2019-01-22 | Defined TXT keys: txtvers, name, (others not publicly documented) | |||||
voalte3 | tcp | Server location via DNS-SD | [Voalte_Inc] | [John_Simpson] | 2019-01-22 | Defined TXT keys: txtvers, name, (others not publicly documented) |
1 2
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[Aaltronav] | Aaltronav | mailto:hostmaster&aaltronav.eu | 2019-10-02 | |
[ICT_Manager] | ICT Manager | Aaltronav | mailto:hostmaster&aaltronav.eu | 2019-10-02 |
[John_Simpson] | John Simpson | Voalte, Inc. | mailto:jms1&voalte.com | 2019-01-22 |
[Patrick_Stein] | Patrick Stein | mailto:Patrick.Stein&jinx.eu | 2011-10-24 | |
[Robert_Goodyear] | Robert Goodyear | mailto:robg&brand-up.com | ||
[Shaun_Wexler] | Shaun Wexler | mailto:dev&macfoh.com | ||
[Signify] | Signify | mailto:leon.bouwmeester&signify.com | 2019-08-09 | |
[Voalte_Inc] | Voalte, Inc. | mailto:engops&voalte.com | 2019-01-22 | |
[Walter_Slegers] | Walter Slegers | mailto:walter.slegers&signify.com | 2019-08-09 |