Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-08-29
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
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] | ||||||
isdc | 1636 | tcp | ISP shared public data control | ||||||||
isdc | 1636 | udp | ISP shared public data control | ||||||||
solve | 2636 | tcp | Solve | [Peter_Morrison] | [Peter_Morrison] | ||||||
solve | 2636 | udp | Solve | [Peter_Morrison] | [Peter_Morrison] | ||||||
servistaitsm | 3636 | tcp | SerVistaITSM | [Ralph_Campbell] | [Ralph_Campbell] | 2002-11 | |||||
servistaitsm | 3636 | udp | SerVistaITSM | [Ralph_Campbell] | [Ralph_Campbell] | 2002-11 | |||||
sfm-db-server | 5636 | tcp | SFMdb - SFM DB server | [De_Chih_Chien] | [De_Chih_Chien] | 2008-10-06 | |||||
5636 | udp | Reserved | |||||||||
metaedit-mu | 6360 | tcp | MetaEdit+ Multi-User | [Steven_Kelly] | [Steven_Kelly] | 2007-11-12 | |||||
metaedit-mu | 6360 | udp | MetaEdit+ Multi-User | [Steven_Kelly] | [Steven_Kelly] | 2007-11-12 | |||||
6361-6362 | Unassigned | ||||||||||
ndn | 6363 | udp | Named Data Networking | [Regents_of_the_University_of_California] | [Jeff_Burke] | 2013-10-30 | |||||
6363 | tcp | Reserved | |||||||||
6364-6369 | Unassigned | ||||||||||
6636 | tcp | Reserved | |||||||||
mpls-udp-dtls | 6636 | udp | Encapsulate MPLS packets in UDP tunnels with DTLS. | [IESG] | [IETF_Chair] | 2015-02-10 | [RFC7510] | ||||
netserialext1 | 16360 | tcp | Network Serial Extension Ports One | [Michael_J_Hoy] | [Michael_J_Hoy] | ||||||
netserialext1 | 16360 | udp | Network Serial Extension Ports One | [Michael_J_Hoy] | [Michael_J_Hoy] | ||||||
netserialext2 | 16361 | tcp | Network Serial Extension Ports Two | [Michael_J_Hoy] | [Michael_J_Hoy] | ||||||
netserialext2 | 16361 | udp | Network Serial Extension Ports Two | [Michael_J_Hoy] | [Michael_J_Hoy] | ||||||
16362-16366 | Unassigned | ||||||||||
netserialext3 | 16367 | tcp | Network Serial Extension Ports Three | [Michael_J_Hoy] | [Michael_J_Hoy] | ||||||
netserialext3 | 16367 | udp | Network Serial Extension Ports Three | [Michael_J_Hoy] | [Michael_J_Hoy] | ||||||
netserialext4 | 16368 | tcp | Network Serial Extension Ports Four | [Michael_J_Hoy] | [Michael_J_Hoy] | ||||||
netserialext4 | 16368 | udp | Network Serial Extension Ports Four | [Michael_J_Hoy] | [Michael_J_Hoy] | ||||||
16369-16383 | Unassigned | ||||||||||
18636-18667 | Unassigned | ||||||||||
DMExpress | 32636 | tcp | DMExpress | [Arnie_Farrelly] | [Arnie_Farrelly] | ||||||
DMExpress | 32636 | udp | DMExpress | [Arnie_Farrelly] | [Arnie_Farrelly] |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[Arnie_Farrelly] | Arnie Farrelly | mailto:afarrelly&syncsort.com | ||
[De_Chih_Chien] | De-Chih Chien | mailto:de-chih_chien&symantec.com | 2008-10-06 | |
[IESG] | IESG | mailto:iesg&ietf.org | ||
[IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
[Jeff_Burke] | Jeff Burke | Regents of the University of California | mailto:jburke&remap.ucla.edu | 2013-10-30 |
[Michael_J_Hoy] | Michael J Hoy | mailto:mhoy&canberra-abq.com | ||
[Pat_Richard] | Pat Richard | mailto:patr&xcert.com | ||
[Peter_Morrison] | Peter Morrison | mailto:peter_morrison&sydney.sterling.com | ||
[Ralph_Campbell] | Ralph Campbell | mailto:ralph.campbell&xasystems.com | 2002-11 | |
[Regents_of_the_University_of_California] | Regents of the University of California | mailto:jburke&remap.ucla.edu | 2013-10-30 | |
[Steven_Kelly] | Steven Kelly | mailto:stevek&metacase.com | 2007-11-12 |