Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-07
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| iris-xpc | 713 | tcp | IRIS over XPC | ||||||||
| iris-xpc | 713 | udp | IRIS over XPC | ||||||||
| conferencetalk | 1713 | tcp | ConferenceTalk | [George_Kajos] | [George_Kajos] | ||||||
| conferencetalk | 1713 | udp | ConferenceTalk | [George_Kajos] | [George_Kajos] | ||||||
| raventbs | 2713 | tcp | Raven Trinity Broker Service | ||||||||
| raventbs | 2713 | udp | Raven Trinity Broker Service | ||||||||
| tftps | 3713 | tcp | TFTP over TLS | [Mark_mayernick] | [Mark_mayernick] | 2003-03 | |||||
| tftps | 3713 | udp | TFTP over TLS | [Mark_mayernick] | [Mark_mayernick] | 2003-03 | |||||
| proshareaudio | 5713 | tcp | proshare conf audio | [gunner] | [gunner] | ||||||
| proshareaudio | 5713 | udp | proshare conf audio | [gunner] | [gunner] | ||||||
| 6707-6713 | Unassigned | ||||||||||
| bfd-lag | 6784 | udp | Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces | [IESG] | [BFD_Chairs] | 2012-11-08 | 2014-01-09 | [RFC7130] | |||
| 7130-7160 | Unassigned | ||||||||||
| 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 |
|---|---|---|---|---|
| [BFD_Chairs] | IETF BFD Working Group Chairs | mailto:bfd-chairs&tools.ietf.org | 2014-01-09 | |
| [George_Kajos] | George Kajos | mailto:gkajos&mail1.videoserver.com | ||
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [Mark_mayernick] | Mark mayernick | mailto:Mark.Mayernick&thomson.net | 2003-03 | |
| [Patrick_Stein] | Patrick Stein | mailto:Patrick.Stein&jinx.eu | 2011-10-24 | |
| [gunner] | mailto:gunner&ibeam.intel.com |