Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-10-15
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
rtip | 771 | tcp | |||||||||
rtip | 771 | udp | |||||||||
vaultbase | 1771 | tcp | vaultbase | [Jose_A_Sesin] | [Jose_A_Sesin] | ||||||
vaultbase | 1771 | udp | vaultbase | [Jose_A_Sesin] | [Jose_A_Sesin] | ||||||
vergencecm | 2771 | tcp | Vergence CM | [Mark_Morwood] | [Mark_Morwood] | ||||||
vergencecm | 2771 | udp | Vergence CM | [Mark_Morwood] | [Mark_Morwood] | ||||||
paging-port | 3771 | tcp | RTP Paging Port | [Patrick_Ferriter] | [Patrick_Ferriter] | 2003-06 | |||||
paging-port | 3771 | udp | RTP Paging Port | [Patrick_Ferriter] | [Patrick_Ferriter] | 2003-06 | |||||
netagent | 5771 | tcp | NetAgent | [Bradley_Birnbaum] | [Bradley_Birnbaum] | ||||||
netagent | 5771 | udp | NetAgent | [Bradley_Birnbaum] | [Bradley_Birnbaum] | ||||||
plysrv-https | 6771 | tcp | PolyServe https | [Mike_Spitzer] | [Mike_Spitzer] | 2005-08 | |||||
plysrv-https | 6771 | udp | PolyServe https | [Mike_Spitzer] | [Mike_Spitzer] | 2005-08 | |||||
7709-7719 | Unassigned | ||||||||||
8771-8777 | Unassigned | ||||||||||
filenet-rmi | 32771 | tcp | FileNET RMI | [Chris_Adkins] | [Chris_Adkins] | ||||||
filenet-rmi | 32771 | udp | FileNet RMI | [Chris_Adkins] | [Chris_Adkins] |
Contact Information
ID | Name | Contact URI | Last Updated |
---|---|---|---|
[Bradley_Birnbaum] | Bradley Birnbaum | mailto:bradley.birnbaum&eshare.com | |
[Chris_Adkins] | Chris Adkins | mailto:cadkins&filenet.com | 2006-10 |
[Jose_A_Sesin] | Jose A. Sesin | mailto:sesin&vaultbase.com | |
[Mark_Morwood] | Mark Morwood | mailto:markm&sentillion.com | |
[Mike_Spitzer] | Mike Spitzer | mailto:mjs&polyserve.com | 2005-08 |
[Patrick_Ferriter] | Patrick Ferriter | mailto:Patrick.Ferriter&zultys.com | 2003-06 |