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 |
---|---|---|---|---|---|---|---|---|---|---|---|
ldap | 389 | tcp | Lightweight Directory Access Protocol | [Tim_Howes] | [Tim_Howes] | ||||||
ldap | 389 | udp | Lightweight Directory Access Protocol | [Tim_Howes] | [Tim_Howes] | ||||||
ldaps | 636 | tcp | ldap protocol over TLS/SSL (was sldap) | [Pat_Richard] | [Pat_Richard] | ||||||
ldaps | 636 | udp | ldap protocol over TLS/SSL (was sldap) | [Pat_Richard] | [Pat_Richard] | ||||||
www-ldap-gw | 1760 | tcp | www-ldap-gw | [Nick_Emery] | [Nick_Emery] | ||||||
www-ldap-gw | 1760 | udp | www-ldap-gw | [Nick_Emery] | [Nick_Emery] | ||||||
msft-gc-ssl | 3269 | tcp | Microsoft Global Catalog with LDAP/SSL | [Asaf_Kashi] | [Asaf_Kashi] | ||||||
msft-gc-ssl | 3269 | udp | Microsoft Global Catalog with LDAP/SSL | [Asaf_Kashi] | [Asaf_Kashi] | ||||||
ldap-admin | 3407 | tcp | LDAP admin server port | [Stephen_Tsun_2] | [Stephen_Tsun_2] | 2002-02 | |||||
ldap-admin | 3407 | udp | LDAP admin server port | [Stephen_Tsun_2] | [Stephen_Tsun_2] | 2002-02 | |||||
bmc-ctd-ldap | 6301 | tcp | BMC CONTROL-D LDAP SERVER IANA assigned this well-formed service name as a replacement for "bmc_ctd_ldap". |
[Portnoy_Boxman_2] | [Portnoy_Boxman_2] | 2006-09 | |||||
bmc_ctd_ldap | 6301 | tcp | BMC CONTROL-D LDAP SERVER | [Portnoy_Boxman_2] | [Portnoy_Boxman_2] | 2006-09 | This entry is an alias to "bmc-ctd-ldap". This entry is now historic, not usable for use with many common service discovery mechanisms. | ||||
bmc-ctd-ldap | 6301 | udp | BMC CONTROL-D LDAP SERVER IANA assigned this well-formed service name as a replacement for "bmc_ctd_ldap". |
[Portnoy_Boxman_2] | [Portnoy_Boxman_2] | 2006-09 | |||||
bmc_ctd_ldap | 6301 | udp | BMC CONTROL-D LDAP SERVER | [Portnoy_Boxman_2] | [Portnoy_Boxman_2] | 2006-09 | This entry is an alias to "bmc-ctd-ldap". This entry is now historic, not usable for use with many common service discovery mechanisms. | ||||
pgpkey-ldap | PGP Keyserver using LDAP | [Jeroen_Massar_3] | [Jeroen_Massar_3] | Defined TXT keys: None |
Contact Information
ID | Name | Contact URI | Last Updated |
---|---|---|---|
[Asaf_Kashi] | Asaf Kashi | mailto:asafkµsoft.com | |
[Jeroen_Massar_3] | Jeroen Massar | mailto:jeroen&unfix.org | |
[Nick_Emery] | Nick Emery | mailto:Nick.Emery&altavista.digital.com | |
[Pat_Richard] | Pat Richard | mailto:patr&xcert.com | |
[Portnoy_Boxman_2] | Portnoy Boxman | mailto:Portnoy_Boxman&bmc.com | 2006-09 |
[Stephen_Tsun_2] | Stephen Tsun | mailto:stsun&calient.net | 2002-02 |
[Tim_Howes] | Tim Howes | mailto:Tim.Howes&terminator.cc.umich.edu |