Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-02
- Expert(s)
-
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ha-cluster | 694 | tcp | ha-cluster | [Alan_Robertson] | [Alan_Robertson] | ||||||
| ha-cluster | 694 | udp | ha-cluster | [Alan_Robertson] | [Alan_Robertson] | ||||||
| rrimwm | 1694 | tcp | rrimwm | ||||||||
| rrimwm | 1694 | udp | rrimwm | ||||||||
| pwrsevent | 2694 | tcp | pwrsevent | [Yoshinobu_Nakamura] | [Yoshinobu_Nakamura] | ||||||
| pwrsevent | 2694 | udp | pwrsevent | [Yoshinobu_Nakamura] | [Yoshinobu_Nakamura] | ||||||
| 3694 | Unassigned | 2007-04-05 | |||||||||
| 5694-5695 | Unassigned | ||||||||||
| reload-config | 6084 | tcp | Peer to Peer Infrastructure Configuration | [IESG] | [IETF_Chair] | 2009-01-29 | 2013-03-26 | [RFC6940] | |||
| 6937-6945 | Unassigned | ||||||||||
| bioserver | 6946 | tcp | Biometrics Server | [ISHII_AKIO] | [ISHII_AKIO] | 2006-01 | |||||
| bioserver | 6946 | udp | Biometrics Server | [ISHII_AKIO] | [ISHII_AKIO] | 2006-01 | |||||
| 6947-6950 | Unassigned | ||||||||||
| client-wakeup | 9694 | tcp | T-Mobile Client Wakeup Message | [Michael_Schonborn] | [Michael_Schonborn] | 2009-09-11 | |||||
| client-wakeup | 9694 | udp | T-Mobile Client Wakeup Message | [Michael_Schonborn] | [Michael_Schonborn] | 2009-09-11 | |||||
| 16901-16949 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Alan_Robertson] | Alan Robertson | mailto:alanr&unix.sh | ||
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [ISHII_AKIO] | ISHII AKIO | mailto:ishii.akio&jp.fujitsu.com | 2006-01 | |
| [Michael_Schonborn] | Michael Schönborn | T-Mobile International AG | mailto:michael.schoenborn&t-mobile.net | 2009-09-11 |
| [Yoshinobu_Nakamura] | Yoshinobu Nakamura | mailto:nakamura&np.lps.cs.fujitsu.co.jp |