Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry
RFC 6335
Document | Type |
RFC - Best Current Practice
(August 2011; Errata)
Also known as BCP 165
|
|
---|---|---|---|
Authors | Michelle Cotton , Lars Eggert , Joseph Touch , Magnus Westerlund , Stuart Cheshire | ||
Last updated | 2020-01-21 | ||
Replaces | draft-cotton-tsvwg-iana-ports | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized with errata bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6335 (Best Current Practice) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | David Harrington | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) M. Cotton Request for Comments: 6335 ICANN BCP: 165 L. Eggert Updates: 2780, 2782, 3828, 4340, 4960, 5595 Nokia Category: Best Current Practice J. Touch ISSN: 2070-1721 USC/ISI M. Westerlund Ericsson S. Cheshire Apple August 2011 Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry Abstract 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. Status of This Memo This memo documents an Internet Best Current Practice. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6335. Cotton, et al. Best Current Practice [Page 1] RFC 6335 Service Name and Port Number Procedures August 2011 Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Cotton, et al. Best Current Practice [Page 2] RFC 6335 Service Name and Port Number Procedures August 2011 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Conventions Used in This Document . . . . . . . . . . . . . . 8 5. Service Names . . . . . . . . . . . . . . . . . . . . . . . . 8 5.1. Service Name Syntax . . . . . . . . . . . . . . . . . . . 9 5.2. Service Name Usage in DNS SRV Records . . . . . . . . . . 10 6. Port Number Ranges . . . . . . . . . . . . . . . . . . . . . . 11 6.1. Service Names and Port Numbers for Experimentation . . . . 12 7. Principles for Service Name and Transport Protocol Port Number Registry Management . . . . . . . . . . . . . . . . . . 12 7.1. Past Principles . . . . . . . . . . . . . . . . . . . . . 13Show full document text