Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-08-17
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| silc | 706 | tcp | SILC | [Pekka_Riikonen] | [Pekka_Riikonen] | ||||||
| silc | 706 | udp | SILC | [Pekka_Riikonen] | [Pekka_Riikonen] | ||||||
| jetform | 1706 | tcp | jetform | [gdeinsta] | [gdeinsta] | ||||||
| jetform | 1706 | udp | jetform | [gdeinsta] | [gdeinsta] | ||||||
| ncdmirroring | 2706 | tcp | NCD Mirroring | [Tim_Stevenson] | [Tim_Stevenson] | ||||||
| ncdmirroring | 2706 | udp | NCD Mirroring | [Tim_Stevenson] | [Tim_Stevenson] | ||||||
| rt-event | 3706 | tcp | Real-Time Event Port | ||||||||
| rt-event | 3706 | udp | Real-Time Event Port | ||||||||
| 5706-5712 | Unassigned | ||||||||||
| 6706 | udp | Reserved | |||||||||
| 6706 | tcp | Reserved | |||||||||
| frc-lp | 6706 | sctp | ForCES LP (Low priority) channel | [RFC5811] | |||||||
| 7041-7069 | Unassigned | ||||||||||
| 7702-7706 | Unassigned | ||||||||||
| aero | 8060 | udp | Asymmetric Extended Route Optimization (AERO) | [IESG] | [IETF_Chair] | [RFC6706] | |||||
| 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 |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Patrick_Stein] | Patrick Stein | mailto:Patrick.Stein&jinx.eu | 2011-10-24 | |
| [Pekka_Riikonen] | Pekka Riikonen | mailto:priikone&poseidon.pspt.fi | ||
| [Tim_Stevenson] | Tim Stevenson | mailto:tes&ncd.com | ||
| [gdeinsta] | gdeinsta | mailto:gdeinsta&jetform.com |