Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2025-10-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 |
---|---|---|---|---|---|---|---|---|---|---|---|
msrps | tcp | MSRP protocol over TLS | 2014-04-25 | [RFC4976] | Defined TXT keys: | ||||||
nfs-domainroot | tcp | NFS service for the domain root, the root of an organization's published file namespace. | [IESG] | [IETF_Chair] | 2012-04-24 | [RFC6641] | Defined TXT keys: None | ||||
pkixrep | Public Key Infrastructure Repository Locator Service | [RFC4386] | |||||||||
pres | tcp | Presence | [RFC3861] | ||||||||
pres | udp | Presence | [RFC3861] | ||||||||
split-dns64 | tcp | DNS64 in split configuration | [Kasper_Dupont] | [Kasper_Dupont] | 2021-10-19 | Defined TXT keys: None | |||||
timezone | tcp | Time Zone Data Distribution Service - non-TLS | [IESG] | [IETF_Chair] | 2015-08-03 | [RFC7808] | This is an extension of the http service. Defined TXT keys: path=<context path> (as per Section 6 of [RFC6763]). | ||||
timezones | tcp | Time Zone Data Distribution Service - over TLS | [IESG] | [IETF_Chair] | 2015-08-03 | [RFC7808] | This is an extension of the https service. Defined TXT keys: path=<context path> (as per Section 6 of [RFC6763]). |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[IESG] | IESG | mailto:iesg&ietf.org | ||
[IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
[Kasper_Dupont] | Kasper Dupont | mailto:kasperd&xwhfx.16.oct.2021.kasperd.dk | 2021-10-19 |