CARVIEW |
Select Language
HTTP/1.1 200 OK
Date: Mon, 14 Jul 2025 14:23:23 GMT
Server: Apache
X-Content-Type-Options: nosniff
Vary: Accept-Encoding,Cookie
Expires: Mon, 14 Jul 2025 14:23:23 GMT
Cache-Control: public, max-age=3600
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
Referrer-Policy: same-origin
Cross-Origin-Opener-Policy: same-origin
Content-Type: text/html; charset=utf-8
Set-Cookie: csrftoken=e23q3y0izQA3FIjYV3rhVNECYyl4w4kM; expires=Mon, 13 Jul 2026 14:23:23 GMT; Max-Age=31449600; Path=/; SameSite=Lax; Secure
Content-Encoding: gzip
Content-Security-Policy: upgrade-insecure-requests; default-src 'self' https://*.iana.org; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.google.com https://cse.google.com https://clients1.google.com; style-src 'self' 'unsafe-inline' https://www.google.com; child-src 'self' https://www.youtube.com https://clients1.google.com https://cse.google.com https://www.google.com/; img-src 'self' https://data.iana.org https://www.iana.org https://www.google.com https://www.googleapis.com https://clients1.google.com https://*.gstatic.com;
Content-Length: 4374
Strict-Transport-Security: max-age=48211200; preload
Application for Service Names and User Port Numbers
Application for Service Names and User Port Numbers
This form is used to register user port numbers and service names in the IANA Service Name and Transport Protocol Port Number Registry.
For detailed instructions on how to fill out the elements of this form, please read the procedures document (RFC 6335).
Please read the following before submitting your request:
- Registration is open to any party that meets the eligibility requirements described in RFC 6335, section 8.1.2, and RFC 7605. This includes review under the "Expert Review" procedure documented in RFC 8126.
- User port numbers range between 1024 and 49151. If you wish to register a system port — those numbered 1023 or less — it must be done through the standardisation process of the IETF. Dynamic port numbers (ranging from 49152-65535) are not assigned.
- 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 an assigned port does not mean that it is "good" traffic nor that the traffic 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, and any other relevant criteria.
- A particular application or service should require at most one assigned user port number. For applications or services that offer multiple functions it is usually possible to utilize one port as a multiplexer or rendezvous service.
- To add an additional transport protocol (TCP, UDP, SCTP or DCCP) to an existing assignment, a new template is required. The new request requires Expert Review.
- In the Service Name and Description, avoid terms and acronyms referring to "service" and "protocol", as these are implied for all assignments. Please also avoid version-specific information, as new assignments are expected to be version-independent.
- The entire process may take up to 1-2 months; given these are permanent changes to a limited global resource, applicants should plan accordingly. The process could take less time if the request is fully formed and all criteria are met.
- Unassigned service names and port numbers should not be used prior to assignment. IANA will assign the service name and optionally a port number after your application has been approved.