Recommendations on Using Assigned Transport Port Numbers
Metadata
- Publisher
- IETF
- Doc Type
- Best Practice
- Pages
- 24
- Abstract
- This document provides recommendations to designers of application and service protocols on how to use the transport protocol port number space and when to request a port assignment from IANA. It provides designer guidance to requesters or users of port numbers on how to interact with IANA using the processes defined in RFC 6335; thus, this document complements (but does not update) that document.
- Publication Date
- 2015-08-01
- Status Note
- Best Current Practice
- DOI
10.17487/RFC7605- Link
- https://doi.org/10.17487/RFC7605
- Author(s)
- Dr. Joseph D. Touch
- Keyword(s)
- TCP, UDP, SCTP, DCCP, IANA
Latest version of IETF RFC 7605
Document Versions — IETF RFC 7605
-
▶ IETF RFC 7605 (2015-08-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2780 [Active*]
- IETF RFC 3692 [Active*]
- IETF RFC 4727 [Active*]
- IETF RFC 5246 [Superseded*]
- IETF RFC 5405 [Superseded*]
- IETF RFC 5925 [Active*]
- IETF RFC 6335 [Active*]
- IETF RFC 6347 [Superseded*]
Bibliographic Reference(s)
- ISI.IEN112 — 46 EXTERNAL
- RFC33 — RFC33 EXTERNAL
- RFC37 — RFC37 EXTERNAL
- RFC38 — RFC38 EXTERNAL
- RFC48 — RFC48 EXTERNAL
- IETF RFC 61 [Superseded*]
- RFC76 — RFC76 EXTERNAL
- IETF RFC 333 [Active*]
- IETF RFC 739 [Superseded*]
- IETF RFC 758 [Superseded*]
- IETF RFC 768 [Active*]
- IETF RFC 793 [Superseded*]
- IETF RFC 820 [Superseded*]
- IETF RFC 900 [Superseded*]
- IETF RFC 959 [Active*]
- IETF RFC 1122 [Active*]
- IETF RFC 1340 [Superseded*]
- IETF RFC 1700 [Superseded*]
- IETF RFC 1812 [Active*]
- IETF RFC 1833 [Active*]
- IETF RFC 2595 [Active*]
- IETF RFC 2644 [Active*]
- IETF RFC 2817 [Active*]
- IETF RFC 3232 [Active*]
- IETF RFC 3261 [Active*]
- IETF RFC 4301 [Active, Amended*]
- IETF RFC 4340 [Active*]
- IETF RFC 4960 [Superseded*]
- IETF RFC 5226 [Superseded*]
- IETF RFC 5245 [Superseded*]
- IETF RFC 5389 [Superseded*]
- IETF RFC 5766 [Superseded*]
- IETF RFC 6066 [Active*]
- IETF RFC 6762 [Active*]
- IETF RFC 6763 [Active*]
- IETF RFC 7120 [Active*]
- IETF RFC 7230 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7605.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7605, Recommendations on Using Assigned Transport Port Numbers. Available at https://doi.org/10.17487/RFC7605
Snippet:
IETF RFC 7605, Recommendations on Using Assigned Transport Port Numbers. Available at https://doi.org/10.17487/RFC7605
HTML (ISO 690 compliant)
Preview:
IETF RFC 7605, Recommendations on Using Assigned Transport Port Numbers. Available at https://doi.org/10.17487/RFC7605
Snippet:
<span class="citation"><cite>IETF RFC 7605</cite>, Recommendations on Using Assigned Transport Port Numbers. Available at <a href="https://doi.org/10.17487/RFC7605" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7605</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7605, Recommendations on Using Assigned Transport Port Numbers
doi: 10.17487/RFC7605
url: https://doi.org/10.17487/RFC7605
doi: 10.17487/RFC7605
url: https://doi.org/10.17487/RFC7605
Snippet:
<li> <cite id="bib-rfc7605">IETF RFC 7605</cite>, Recommendations on Using Assigned Transport Port Numbers <span class="doi">10.17487/RFC7605</span> </li>
Referenced By
- IETF RFC 8085 [Active*]
- IETF RFC 9205 [Active*]