| Number | Files | Title | Authors | Date | More Info | Status |
|---|---|---|---|---|---|---|
| RFC 6335,BCP 165 | 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 | UpdatesRFC 2780,RFC 2782,RFC 3828,RFC 4340,RFC 4960,RFC 5595,Errata | Best Current Practice | |
| RFC 7605,BCP 165 | Recommendations on Using Assigned Transport Port Numbers | J. Touch | August 2015 | Errata | Best Current Practice |
This document defines the procedures that the Internet AssignedNumbers Authority (IANA) uses when handling assignment and otherrequests related to the Service Name and Transport Protocol PortNumber registry. It also discusses the rationale and principlesbehind these procedures and how they facilitate the long-termsustainability of the registry.
This document updates IANA's procedures by obsoleting the previousUDP and TCP port assignment procedures defined in Sections 8 and 9.1of the IANA Allocation Guidelines, and it updates the IANA servicename and port assignment procedures for UDP-Lite, the DatagramCongestion Control Protocol (DCCP), and the Stream ControlTransmission Protocol (SCTP). It also updates the DNS SRVspecification to clarify what a service name is and how it isregistered. This memo documents an Internet Best Current Practice.
This document provides recommendations to designers of application andservice protocols on how to use the transport protocol port numberspace and when to request a port assignment from IANA. It provides designerguidance to requesters or users of port numbers on how to interact with IANAusing the processes defined in RFC 6335; thus, this document complements (butdoes not update) that document.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.