Description
The Internet Assigned Numbers Authority (IANA) is a function, historically performed by ICANN, that coordinates key technical elements of the global Internet to ensure its stable and secure operation. Its core responsibilities include the allocation of IP address blocks to Regional Internet Registries (RIRs), the administration of the AS Number space, and the management of the DNS root zone. Crucially for protocol development, IANA maintains registries of "protocol parameters" – the code points, numbers, and identifiers used in Internet protocols (e.g., IP protocol numbers, TCP/UDP port numbers, enterprise numbers for SNMP and RADIUS).
In the context of 3GPP standards, IANA's role is referential. 3GPP technical specifications (TSs) do not define new global protocol numbers arbitrarily. Instead, when a 3GPP-defined protocol needs a unique identifier for use on IP networks (e.g., a new GTP extension, a DIAMETER application, or a protocol type in a packet header), the specification mandates that the value must be assigned by IANA. For example, TS 29.060 (GTP) specifies that GTPv1-C message types must be registered with IANA, and TS 29.272 (E-UTRAN DIAMETER interfaces) defines DIAMETER Application-Ids that require IANA assignment. This ensures global interoperability and prevents conflicts with other standards bodies.
The process involves 3GPP submitting a request to IANA via an IETF RFC or through direct liaison, following IETF guidelines (RFC 5226). Once assigned, these numbers are published in IANA's online registries. 3GPP equipment and network nodes (e.g., PGWs, MMEs, PCRFs) are then implemented using these globally unique, IANA-assigned values. This dependency highlights the deep integration of 3GPP architectures with the broader Internet protocol ecosystem, ensuring that 5G and LTE networks can seamlessly exchange data and signaling with servers and networks on the public Internet.
Purpose & Motivation
IANA exists to provide a central, neutral coordination point for the technical parameters that underpin the global Internet's interoperability. Without such a central authority, different vendors, operators, and standards bodies might independently assign the same number for different purposes, leading to protocol conflicts, packet misrouting, and service failures. The creation of IANA (originally managed by Jon Postel) was motivated by the need for order in the early, rapidly expanding ARPANET and Internet, ensuring that fundamental resources like IP addresses and protocol numbers were allocated in a fair and consistent manner.
For 3GPP, referencing IANA solves the problem of how to integrate mobile-specific protocols into the global Internet infrastructure. 3GPP networks are not isolated; they connect to the Internet and interwork with IETF-defined protocols daily. By using IANA-assigned numbers, 3GPP ensures that its protocols (e.g., GTP, DIAMETER, PFCP) are uniquely identifiable on IP networks worldwide. This approach addresses the limitations of proprietary or organization-specific number spaces, which would cause interoperability nightmares in multi-vendor, multi-operator environments. The historical context is the convergence of telecommunications and Internet technologies, where 3GPP adopted IP as its core transport, necessitating adherence to the Internet's established coordination mechanisms.
Key Features
- Global allocation of IP address spaces to RIRs
- Management of the DNS root zone and .int domain
- Maintenance of protocol parameter registries (numbers, codes)
- Assignment of Autonomous System (AS) Numbers
- Coordination of TCP/UDP port numbers and IP protocol numbers
- Registration of enterprise numbers for vendor-specific MIBs/attributes
Evolution Across Releases
First referenced in 3GPP specifications as the authority for protocol number assignments, particularly as 3GPP began specifying IP-based interfaces and protocols. This established the principle that 3GPP would use the Internet's standard numbering spaces rather than creating its own conflicting ones.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.140 | 3GPP TS 23.140 |
| TS 23.816 | 3GPP TS 23.816 |
| TS 24.302 | 3GPP TS 24.302 |
| TS 24.484 | 3GPP TS 24.484 |
| TS 26.142 | 3GPP TS 26.142 |
| TS 26.143 | 3GPP TS 26.143 |
| TS 26.346 | 3GPP TS 26.346 |
| TS 26.804 | 3GPP TS 26.804 |
| TS 26.841 | 3GPP TS 26.841 |
| TS 29.060 | 3GPP TS 29.060 |
| TS 29.173 | 3GPP TS 29.173 |
| TS 29.229 | 3GPP TS 29.229 |
| TS 29.230 | 3GPP TS 29.230 |
| TS 29.329 | 3GPP TS 29.329 |
| TS 29.336 | 3GPP TS 29.336 |
| TS 29.337 | 3GPP TS 29.337 |
| TS 29.338 | 3GPP TS 29.338 |
| TS 29.414 | 3GPP TS 29.414 |
| TS 29.835 | 3GPP TS 29.835 |
| TS 31.113 | 3GPP TR 31.113 |
| TS 32.272 | 3GPP TR 32.272 |
| TS 36.422 | 3GPP TR 36.422 |
| TS 36.462 | 3GPP TR 36.462 |
| TS 37.472 | 3GPP TR 37.472 |
| TS 37.482 | 3GPP TR 37.482 |
| TS 38.412 | 3GPP TR 38.412 |
| TS 38.422 | 3GPP TR 38.422 |
| TS 38.462 | 3GPP TR 38.462 |
| TS 38.472 | 3GPP TR 38.472 |
| TS 38.825 | 3GPP TR 38.825 |