RFC 7605: Recommendations on Using Assigned Transport Port Numbers
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7605
- Published
- August 2015
- Authors
- J. Touch
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- wit
- Pages
- 24
- Also known as
- BCP165
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6633Deprecation of ICMP Source Quench MessagesCurrent
May 2012
- RFC 3257Stream Control Transmission Protocol Applicability StatementCurrent
April 2002
- RFC 8899Packetization Layer Path MTU Discovery for Datagram TransportsCurrent
September 2020
- RFC 8087The Benefits of Using Explicit Congestion Notification (ECN)Current
March 2017
- RFC 6773DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT TraversalCurrent
November 2012
- RFC 1835Architecture of the WHOIS++ serviceCurrent
August 1995
- RFC 1834Whois and Network Information Lookup Service, Whois++Current
August 1995
- RFC 7560Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) FeedbackCurrent
August 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?