RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry

This document defines the procedures that the Internet Assigned Numbers Authority (IANA) uses when handling assignment and other requests related to the…

Read RFC 6335 on the RFC Editor

Outgoing relationships (25 related RFCs)

Updates, Normative reference — RFC 4960: Stream Control Transmission Protocol
Updates, Normative reference — RFC 2782: A DNS RR for specifying the location of services (DNS SRV)
Updates, Normative reference — RFC 4340: Datagram Congestion Control Protocol (DCCP)
Updates, Normative reference — RFC 3828: The Lightweight User Datagram Protocol (UDP-Lite)
Updates, Normative reference — RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
Updates, Normative reference — RFC 5595: The Datagram Congestion Control Protocol (DCCP) Service Codes
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 5234: Augmented BNF for Syntax Specifications: ABNF
Normative reference — RFC 793: Transmission Control Protocol
Normative reference — RFC 768: User Datagram Protocol
Normative reference — RFC 4727: Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP Headers
Normative reference — RFC 4020: Early IANA Allocation of Standards Track Code Points
Informative reference — RFC 5389: Session Traversal Utilities for NAT (STUN)
Informative reference — RFC 1700: Assigned Numbers
Informative reference — RFC 959: File Transfer Protocol
Informative reference — RFC 5766: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
Informative reference — RFC 3692: Assigning Experimental and Testing Numbers Considered Useful
Informative reference — RFC 3232: Assigned Numbers: RFC 1700 is Replaced by an On-line Database
Informative reference — RFC 4844: The RFC Series and RFC Editor
Informative reference — RFC 4342: Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 3: TCP-Friendly Rate Control (TFRC)
Informative reference — RFC 1340: Assigned Numbers
Informative reference — RFC 1078: TCP port service Multiplexer (TCPMUX)
Informative reference — RFC 2957: The application/whoispp-query Content-Type
Informative reference — RFC 5237: IANA Allocation Guidelines for the Protocol Field

Incoming relationships (35 related RFCs)

Normatively referenced by — RFC 7858: Specification for DNS over Transport Layer Security (TLS)
Normatively referenced by — RFC 6763: DNS-Based Service Discovery
Normatively referenced by — RFC 9260: Stream Control Transmission Protocol
Normatively referenced by — RFC 7414: A Roadmap for Transmission Control Protocol (TCP) Specification Documents
Normatively referenced by — RFC 7595: Guidelines and Registration Procedures for URI Schemes
Normatively referenced by — RFC 8762: Simple Two-Way Active Measurement Protocol
Normatively referenced by — RFC 7589: Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication
Normatively referenced by — RFC 8915: Network Time Security for the Network Time Protocol
Normatively referenced by — RFC 7350: Datagram Transport Layer Security (DTLS) as Transport for Session Traversal Utilities for NAT (STUN)
Normatively referenced by — RFC 8765: DNS Push Notifications
Normatively referenced by — RFC 7605: Recommendations on Using Assigned Transport Port Numbers
Normatively referenced by — RFC 8071: NETCONF Call Home and RESTCONF Call Home
Normatively referenced by — RFC 7808: Time Zone Data Distribution Service
Normatively referenced by — RFC 6641: Using DNS SRV to Specify a Global File Namespace with NFS Version 4
Normatively referenced by — RFC 6764: Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV)
Normatively referenced by — RFC 8267: Network File System (NFS) Upper-Layer Binding to RPC-over-RDMA Version 1
Normatively referenced by — RFC 7553: The Uniform Resource Identifier (URI) DNS Resource Record
Normatively referenced by — RFC 9900: Updates to NETCONF Transport Port Numbers
Informatively referenced by — RFC 7252: The Constrained Application Protocol (CoAP)
Informatively referenced by — RFC 8085: UDP Usage Guidelines
Informatively referenced by — RFC 6733: Diameter Base Protocol
Informatively referenced by — RFC 9499: DNS Terminology
Informatively referenced by — RFC 7597: Mapping of Address and Port with Encapsulation (MAP-E)
Informatively referenced by — RFC 8094: DNS over Datagram Transport Layer Security (DTLS)
Informatively referenced by — RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
Informatively referenced by — RFC 6943: Issues in Identifier Comparison for Security Purposes
Informatively referenced by — RFC 6951: UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets for End-Host to End-Host Communication
Informatively referenced by — RFC 7585: Dynamic Peer Discovery for RADIUS/TLS and RADIUS/DTLS Based on the Network Access Identifier (NAI)
Informatively referenced by — RFC 8994: An Autonomic Control Plane (ACP)
Informatively referenced by — RFC 7422: Deterministic Address Mapping to Reduce Logging in Carrier-Grade NAT Deployments
Informatively referenced by — RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access
Informatively referenced by — RFC 9109: Network Time Protocol Version 4: Port Randomization
Informatively referenced by — RFC 7711: PKIX over Secure HTTP (POSH)
Informatively referenced by — RFC 7618: Dynamic Allocation of Shared IPv4 Addresses
Informatively referenced by — RFC 9665: Service Registration Protocol for DNS-Based Service Discovery