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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| olsr | 698 | tcp | OLSR | [Thomas_Clausen] | [Thomas_Clausen] | ||||||
| olsr | 698 | udp | OLSR | [Thomas_Clausen] | [Thomas_Clausen] | ||||||
| rsvp-encap-1 | 1698 | tcp | RSVP-ENCAPSULATION-1 | ||||||||
| rsvp-encap-1 | 1698 | udp | RSVP-ENCAPSULATION-1 | ||||||||
| mck-ivpip | 2698 | tcp | MCK-IVPIP | [Robert_Vincent] | [Robert_Vincent] | ||||||
| mck-ivpip | 2698 | udp | MCK-IVPIP | [Robert_Vincent] | [Robert_Vincent] | ||||||
| sagectlpanel | 3698 | tcp | SAGECTLPANEL | [Mark_Gamble] | [Mark_Gamble] | 2003-02 | |||||
| sagectlpanel | 3698 | udp | SAGECTLPANEL | [Mark_Gamble] | [Mark_Gamble] | 2003-02 | |||||
| 6698 | Unassigned | ||||||||||
| 6980 | tcp | Reserved | |||||||||
| qolyester | 6980 | udp | QoS-extended OLSR protocol | [Green_Communications_SAS] | [Ignacy_Gawedzki] | 2022-05-24 | |||||
| 6981-6996 | Unassigned | ||||||||||
| 7698-7699 | Unassigned | ||||||||||
| 8689-8698 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Green_Communications_SAS] | Green Communications SAS | mailto:contact&green-communications.fr | 2022-05-24 | |
| [Ignacy_Gawedzki] | Ignacy Gawedzki | Green Communications SAS | mailto:ignacy.gawedzki&green-communications.fr | 2022-05-24 |
| [Mark_Gamble] | Mark Gamble | mailto:mark.gamble&sage.com | 2003-02 | |
| [Robert_Vincent] | Robert Vincent | mailto:bert&mck.com | ||
| [Thomas_Clausen] | Thomas Clausen | mailto:thomas.clausen&polytechnique.edu | 2023-02-28 |