Internet Engineering Steering Group

Description

The Internet Engineering Steering Group (IESG) is the executive technical management body of the Internet Engineering Task Force (IETF). Within the context of 3GPP specifications, the IESG is referenced because 3GPP systems extensively incorporate IETF-developed protocols. The IESG does not define 3GPP-specific functionalities but is responsible for the approval and standardization process of IETF Request for Comments (RFCs), which become foundational to 3GPP architectures. For example, protocols such as the Session Initiation Protocol (SIP) for IMS multimedia telephony, the Diameter protocol for authentication and authorization, HTTP/2 for service-based interfaces in 5G core, and TCP/IP suites are all standardized through IETF processes overseen by the IESG.

The IESG's role in the IETF ecosystem is to provide technical oversight. It reviews and approves all IETF Internet-Drafts that are proposed to become Standards Track or Best Current Practice RFCs. This review ensures consistency with the IETF's architectural principles, technical quality, and that proper process has been followed. The IESG is composed of the Area Directors (ADs) who lead the various IETF technical areas (e.g., Transport, Routing, Security, Applications). When 3GPP decides to use an IETF protocol, it typically references a specific, stable RFC. The stability and authority of that RFC are a direct result of the IESG's approval. 3GPP may then profile the protocol—defining specific usage, extensions (via new AVPs or headers), and mandatory features—for its cellular context, documented in 3GPP specs like 29.835.

Therefore, the mention of IESG in 3GPP documents (e.g., in liaisons or normative references) acknowledges the governance source of key external standards. It highlights the collaborative relationship between the two standardization bodies. The IESG's management ensures that the IETF protocols 3GPP relies upon are robust, openly reviewed, and maintained, which in turn reduces risk and promotes global interoperability for 3GPP networks that use internet technology.

Purpose & Motivation

The IESG itself exists to provide leadership and ensure the technical coherence of the IETF's output, which is consumed by organizations worldwide, including 3GPP. Its purpose within the 3GPP context is indirect but vital: it provides the authoritative, stable foundation of internet protocols upon which 3GPP builds its service layers. 3GPP's motivation to reference IETF protocols, and by extension acknowledge the IESG, was driven by the desire to leverage well-established, ubiquitous, and non-proprietary technologies for data communication.

This approach solved several problems for 3GPP. First, it avoided reinventing the wheel for common functions like session signaling (SIP) or authentication (Diameter). Second, it ensured seamless interoperability between cellular networks and the broader internet. Adopting IETF standards facilitated convergence between telecom and IT worlds. The limitation of previous, purely telecom-specific protocols (e.g., SS7-based MAP) was their complexity and isolation from the internet ecosystem, making service innovation slower. By building on IETF work, 3GPP could focus its standardization efforts on the unique radio and mobility aspects while integrating best-of-breed solutions for IP-based service delivery.

The historical context is the shift from circuit-switched to all-IP networks initiated in 3GPP Rel-4/5. This required a new set of IP-based core network protocols. The IETF, with its open process and the IESG's stewardship, was the natural source. References to the IESG in 3GPP specs formalize this dependency and recognize the governance structure that guarantees the quality and openness of the underlying protocols.

Key Features

• Provides technical management and process oversight for the IETF standardization process.
• Composed of Area Directors who are responsible for specific technical domains.
• Approves all IETF Standards Track and BCP RFCs, ensuring quality and architectural consistency.
• Its output (RFCs) is normatively referenced by 3GPP for protocols like SIP, Diameter, and TLS.
• Represents the authoritative body for the internet standards used in 3GPP architectures.
• Facilitates liaison and collaboration between IETF and external SDOs like 3GPP.

Evolution Across Releases

Defining Specifications