Description
Request For Comments (RFC) is a formal document series authored and published by the Internet Engineering Task Force (IETF). Within the 3GPP ecosystem, RFCs are critically important because many core protocols and architectural principles used in mobile networks are derived from or specified by IETF standards. An RFC can represent several stages of standardization: Internet Standard, Proposed Standard, Best Current Practice (BCP), Informational, or Experimental. The process begins with an Internet-Draft, which, after review and consensus within the relevant IETF working group, may be published as an RFC. Once published, an RFC is assigned a sequential number and remains static; revisions are issued as new RFCs, potentially obsoleting previous ones.
The content of an RFC can range from detailed protocol specifications (e.g., RFC 3261 for SIP, RFC 6733 for Diameter) to architectural overviews, policy documents, and historical notes. Protocol specifications define message formats, state machines, error handling, and security considerations. For 3GPP, these protocols are often incorporated by reference. For instance, the IP Multimedia Subsystem (IMS) relies heavily on SIP (RFC 3261) for session control, Diameter (RFC 6733) for authentication and authorization, and RTP (RFC 3550) for media transport. The 3GPP specifications define how these generic Internet protocols are profiled, extended, or constrained for use in a mobile environment, such as adding specific header fields or defining new Diameter applications.
From an architectural perspective, the use of IETF RFCs allows 3GPP to leverage well-tested, open standards, promoting interoperability between mobile networks and the broader Internet. It enables a clear separation between the radio-specific layers (defined by 3GPP) and the core service layers that use IP technology. Engineers working on 3GPP core network elements must have a deep understanding of the relevant RFCs to implement nodes like the P-CSCF, HSS, or PCRF correctly. The RFC publication process, with its emphasis on open review and rough consensus, contributes to the robustness and security of the protocols upon which modern telecommunications depend.
Purpose & Motivation
The RFC process was created to facilitate the open development and documentation of the protocols and procedures that make the Internet work. Its purpose is to provide a stable, referenceable record of technical specifications and ideas. For 3GPP, adopting IETF RFCs solves several key problems. First, it avoids reinventing the wheel; instead of creating proprietary protocols for IP-based services, 3GPP can integrate mature, widely implemented standards. This accelerates development and ensures global interoperability. Second, it aligns mobile networks with the Internet paradigm, which was a fundamental design goal for 3G and beyond, moving away from circuit-switched telephony towards an all-IP core.
Historically, early cellular standards (like GSM) used telecom-specific signaling protocols (e.g., MAP, CAP). The shift to 3G (UMTS) and especially 4G (LTE) involved a conscious decision to base the core network on IP. This required protocols for session management, mobility, and security that were scalable and widely understood. The IETF's work on SIP, Diameter, and IPsec provided ready-made solutions. The RFC mechanism, with its rigorous peer review, provided the necessary technical depth and stability for large-scale commercial deployment.
Furthermore, the RFC series includes Best Current Practice documents that guide operational and security practices, which are vital for running reliable networks. By referencing RFCs, 3GPP specifications can remain focused on the radio access and mobile-specific adaptations, while delegating the detailed IP protocol mechanics to the IETF. This separation of concerns is a key factor in the success and flexibility of modern mobile network architectures.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (32 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the RFC function was enhanced to handle specific procedural scenarios for managing floor control, including the handling of multiple floor requests from the same user when queuing and the processing of floor requests received by a former floor arbitrator from the user who was granted the floor. Additionally, the release incorporated the published RFC 8583, which standardized the Diameter Load control mechanism, and introduced procedures related to a Requested Node AMF.
- Handling mulitple Floor Requests from same user when queuing TS 24.380CR0191
- Handling Floor Requests received by former floor arbitrator from floor granted user TS 24.380CR0190
- draft-ietf-dime-load published as RFC 8583 TS 29.229CR0293
- Requested Node AMF TS 29.329CR0249
- draft-ietf-dime-load published as RFC 8583 TS 29.329CR0251
In Release 16, the RFC function was enhanced with specific procedures for handling unacknowledged group call requests in MCPTT, providing a list of non-responding members. The release also introduced refined state management to handle a 'Floor taken' message while in a 'Pending request' state and clarified the handling of transmission end requests while awaiting prior responses.
- List of MCPTT group members who did not acknowledge the group call request TS 24.483CR0065
- List of MCPTT group members who did not acknowledge the group call request TS 24.484CR0134
- Handle Floor taken message in 'Pending request' state of floor participant state m/c TS 24.380CR0240
- Removing Transmission cancel request and Transmission cancel response TS 24.581CR0062
- EN on Floor Request multi talker TS 24.380CR0222
- SSRC handling for implicit floor request case TS 24.380CR0242
+ 2 more changes
In Release 17, the RFC function was enhanced with new procedures for managing the floor request queue, including the ability for an authorized user to cancel a queued request and to clear the entire queue. The release also updated IETF references for ICE and RFC 7616, and provided a terminology fix for the authorization semantics of "Allow-request-affiliated-groups." These updates refined the control mechanisms available to the service requester within the service relationship.
- Cancel queued floor request and notify to users TS 24.380CR0275
- An authorized user clearing the entire floor request queue TS 24.380CR0304
- Update of IETF references for ICE TS 29.232CR0662
- Update of IETF references for ICE TS 29.332CR0202
- Floor request queue terminology TS 24.380CR0305
- Allow-request-affiliated-groups authorization semantics fix TS 24.484CR0203
+ 2 more changes
In Release 18, the RFC function was enhanced by adding the user ID parameter to Floor Request and Transmission Request messages from the NCF to the CF, as specified for MCPTT and MCVideo services. The release also provided clarifications on handling the release of queued floor request re-transmissions and on the applicability of IETF RFC 8101 namespaces. Furthermore, corrections were made to procedural message names and usage guidance for RTP SSRC during call setup with implicit transmission requests.
- MCPTT Adding user ID in Floor Request message from NCF to CF TS 24.380CR0348
- MCVideo Adding user ID in Transmission Request message from NCF to CF TS 24.581CR0112
- Correction of Queued Floor Request message name TS 24.380CR0325
- Plugtest issue 10.1.4 of Nov 2022: Handling of release queued floor request re-transmission TS 24.380CR0330
- Clarification on applicability of the namespaces IETF RFC 8101 TS 24.484CR0237
- RTP SSRC of audio and video media streams usage in during call setup using implicit transmission request - med plane TS 24.581CR0110
+ 1 more changes
In Release 19, the RFC function was updated to include procedures for terminating a local BDC establishment even when the incoming INVITE request's SDP lacks a BDC media component. It also introduced new configuration parameters for authorizing emergency remote floor requests, both for management objects and general network configuration. Furthermore, the release updated the normative IETF reference governing the process for signing and verifying third-party user identity information.
- Terminating local BDC establishment without BDC media component in SDP of incoming INVITE request TS 23.228CR1416
- Emergency remote floor request authorization MO configuration TS 24.483CR0190
- Emergency remote floor request authorization configuration TS 24.484CR0287
- Update the IETF reference to the process of signing and verifying third party user identity information TS 23.228CR1652
Explore further
Broader topics and technologies where RFC plays a role.
Defining Specifications
3GPP specifications that define or reference RFC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TR 22.945 v1300 | Fax Services Guidance for GSM/UMTS | Rel-4 |
| TS 23.057 vj00 | Mobile Execution Environment (MExE) Specification | Rel-19 |
| TS 23.140 v1600 | MMS Non-Realtime Service Definition | Rel-6 |
| TS 23.141 vj00 | Presence Service Stage 2 Architecture | Rel-19 |
| TS 23.218 vj00 | IMS Call Model Specification | Rel-19 |
| TS 23.228 vj50 | IMS Stage-2 Service Description | Rel-19 |
| TS 23.701 vc00 | WebRTC Access to IMS Architecture Study | Rel-12 |
| TS 24.380 vj10 | MCPTT Media Plane Control Protocol | Rel-19 |
| TS 24.483 vj20 | Mission Critical Services Management Object | Rel-19 |
| TS 24.484 vj30 | MCS Configuration Management | Rel-19 |
| TS 24.581 vj00 | MCVideo Media Plane Control Protocol Specification | Rel-19 |
| TS 25.323 vj00 | Packet Data Convergence Protocol (PDCP) Specification | Rel-19 |
| TS 25.414 vj00 | UTRAN Iu Interface User Plane Transport Protocols | Rel-19 |
| TS 25.415 vj00 | Iu Interface User Plane Protocol | Rel-19 |
| TS 25.442 vj00 | Node B Implementation Specific O&M Transport via RNC | Rel-19 |
| TS 25.444 vj00 | HNB User Data Transport Protocols | Rel-19 |
| TS 26.102 vj00 | Mapping of AMR and other codecs to interfaces | Rel-19 |
| TS 26.202 vj00 | AMR-WB Speech Codec Mapping Specification | Rel-19 |
| TS 26.233 vf00 | 3GPP Packet-Switched Streaming Service (PSS) | Rel-15 |
| TS 26.234 vj00 | 3GPP PSS Protocols and Codecs Specification | Rel-19 |
| TS 26.235 vc00 | Default Codecs for 3GPP IP Multimedia Subsystem | Rel-12 |
| TS 26.236 vc00 | Packet Switched Conversational Multimedia Protocols | Rel-12 |
| TS 26.247 vj00 | 3GPP Progressive Download & DASH over HTTP | Rel-19 |
| TS 26.454 vj00 | EVS Codec Mapping for 3G CS Networks | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TS 26.851 vb20 | Enhancements to Multimedia (EMM) for PSS, MMS, MBMS | Rel-11 |
| TR 26.902 vj00 | Video Codec Performance for 3GPP Packet Services | Rel-19 |
| TR 26.962 vj00 | ITT4RT Operation and Usage Guidelines | Rel-19 |
| TR 26.998 vj00 | 5G AR/MR Glasses Integration Study | Rel-19 |
| TS 29.173 vj00 | Diameter-based SLh Interface for LCS | Rel-19 |
| TS 29.199 v1900 | Multimedia Messaging Web Services | Rel-9 |
| TS 29.229 vj10 | Diameter Protocol for Cx/Dx Interfaces | Rel-19 |
| TS 29.232 vj00 | Mc Interface Protocol Profile | Rel-19 |
| TS 29.329 vj10 | Diameter Protocol for Sh Interface | Rel-19 |
| TS 29.332 vj00 | MGCF-IM-MGW Interface Protocol (Mn) | Rel-19 |
| TS 29.380 vj00 | MCPTT-LMR Interworking Media Plane Control | Rel-19 |
| TS 29.412 v1810 | Trunking Gateway Control Procedures | Rel-8 |
| TS 29.414 vj00 | Nb Interface Bearer Transport & Control Protocols | Rel-19 |
| TS 29.424 v801 | H.248 Profile for Trunking Media Gateways | Rel-8 |
| TS 29.433 v1811 | ETSI TISPAN Endorsement of 3GPP Cx/Dx Interfaces | Rel-8 |
| TS 29.582 vj00 | MCData Interworking with LMR Systems | Rel-19 |
| TR 29.835 vh10 | Study on Port Allocation for 3GPP Interfaces | Rel-17 |
| TS 31.112 v1800 | USAT Interpreter System Architecture | Rel-8 |
| TS 33.822 v1800 | Security Architecture for Inter-Access Mobility | Rel-8 |
| TR 33.978 v1800 | Interim Security for Early IMS | Rel-8 |
| TS 36.323 vj00 | PDCP Protocol Specification | Rel-19 |
| TS 36.462 vj00 | Xw Interface Signalling Transport | Rel-19 |
| TS 38.323 vj00 | Packet Data Convergence Protocol (PDCP) | Rel-19 |
| TS 48.103 vj00 | A Interface User Plane Transport Protocols | Rel-19 |