Cite this BCP: TXTBCP 165 contains the following RFCs:
|RFC 6335, BCP 165||ASCII, PDF||Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry||M. Cotton, L. Eggert, J. Touch, M. Westerlund, S. Cheshire||August 2011||Updates RFC 2780, RFC 2782, RFC 3828, RFC 4340, RFC 4960, RFC 5595, Errata||Best Current Practice|
|RFC 7605, BCP 165||ASCII, PDF||Recommendations on Using Assigned Transport Port Numbers||J. Touch||August 2015||Errata||Best Current Practice|
Abstract of RFC 6335
This document defines the procedures that the Internet Assigned Numbers Authority (IANA) uses when handling assignment and other requests related to the Service Name and Transport Protocol Port Number registry. It also discusses the rationale and principles behind these procedures and how they facilitate the long-term sustainability of the registry. This document updates IANA's procedures by obsoleting the previous UDP and TCP port assignment procedures defined in Sections 8 and 9.1 of the IANA Allocation Guidelines, and it updates the IANA service name and port assignment procedures for UDP-Lite, the Datagram Congestion Control Protocol (DCCP), and the Stream Control Transmission Protocol (SCTP). It also updates the DNS SRV specification to clarify what a service name is and how it is registered. This memo documents an Internet Best Current Practice.
Abstract of RFC 7605
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.