Description
The Point-to-Point Protocol (PPP) is a robust data link layer (Layer 2) protocol defined by the IETF (RFC 1661) and widely adopted in telecommunications. Its primary function is to transport multi-protocol datagrams over a point-to-point link. PPP operates by first establishing a link, then optionally authenticating the peer, and finally negotiating network-layer protocol configurations. The protocol frame structure includes fields for protocol identification, allowing it to encapsulate and multiplex packets from different network protocols (like IP, IPX, or AppleTalk) over the same physical link. A key component is the Link Control Protocol (LCP), which is responsible for link establishment, configuration, testing, and termination. LCP negotiates parameters like maximum receive unit, authentication protocol, and magic number for loop detection.
Following successful LCP negotiation, PPP typically proceeds to authentication using protocols like Password Authentication Protocol (PAP) or the more secure Challenge-Handshake Authentication Protocol (CHAP). Once authenticated, PPP uses a family of Network Control Protocols (NCPs) to configure the specific network-layer protocols to be used on the link. For IP traffic, the IP Control Protocol (IPCP) is used to negotiate parameters such as the IP addresses for the endpoints. This layered negotiation makes PPP highly flexible and adaptable to different underlying physical media, including serial lines, phone lines, trunk lines, cellular networks, and fiber optic links.
In 3GPP contexts, PPP has been used historically as the Layer 2 protocol for certain types of Packet Data Protocol (PDP) contexts in 2G (GPRS) and 3G (UMTS) networks, particularly for interworking with legacy external packet data networks. The Gateway GPRS Support Node (GGSN) could use PPP to terminate connections from the mobile station, providing a familiar interface for IP address allocation and authentication. While largely superseded in the 4G and 5G user plane by Ethernet and GTP-U based encapsulation, PPP principles influenced later protocols, and its authentication mechanisms see continued relevance. Its design ensures reliable, full-duplex communication with built-in error detection, making it a foundational protocol for direct link management.
Purpose & Motivation
PPP was created to solve the limitations of its predecessor, the Serial Line Internet Protocol (SLIP). SLIP was a very simple framing protocol that only supported IP, had no error detection, required manually configured addresses, and offered no authentication. As the internet expanded beyond academic and research networks, there was a critical need for a standardized, robust, and feature-rich protocol for point-to-point links, especially for the burgeoning dial-up internet access market.
PPP addressed these shortcomings by providing a standardized frame format, the ability to carry multiple network layer protocols simultaneously, dynamic IP address negotiation, and mandatory link quality testing and error detection. Its integrated authentication support (PAP/CHAP) was crucial for Internet Service Providers (ISPs) to securely authenticate subscribers over telephone lines. Within 3GPP, PPP provided a well-understood and reliable mechanism for establishing the data link for mobile data sessions in early cellular data systems, facilitating interworking with existing ISP infrastructure and corporate remote access servers. It served as a crucial bridging technology between the mobile packet core and the fixed internet.
What changed in its specifications
The latest release-to-release comparison of specifications that define PPP. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 brings only minor changes to TS 23.060: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.060 →Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Introduced in 3GPP for UMTS as a supported data link protocol for Packet Data Protocol (PDP) contexts. It was used between the User Equipment (UE) and the GGSN to establish a point-to-point link for IP traffic, supporting authentication and dynamic address allocation within the 3G packet core architecture.
Defining Specifications
3GPP specifications that define or reference PPP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TR 22.816 ve10 | 3GPP TV Service Enhancement Technical Report | Rel-14 read |
| TR 22.829 vh10 | Enhancement for UAVs; Stage 1 | Rel-17 read |
| TR 22.945 v300 | Fax Services Guidance for GSM/UMTS | R99 read |
| TS 23.060 vj00 | GPRS Stage 2 Service Description | Rel-19 read |
| TS 23.146 vj00 | 3G Facsimile Group 3 Technical Realization | Rel-19 read |
| TS 23.228 vk10 | IP Multimedia Core Network Subsystem | Rel-20 read |
| TS 23.841 v600 | Presence Service Architecture Specification | Rel-6 read |
| TS 25.323 vj00 | Packet Data Convergence Protocol (PDCP) Specification | Rel-19 read |
| TS 25.412 vj00 | Iu Interface Signalling Transport Specification | Rel-19 read |
| TS 25.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 read |
| TS 25.414 vj00 | UTRAN Iu Interface User Plane Transport Protocols | Rel-19 read |
| TS 25.422 vj00 | Signalling Transport for Iur Interface | Rel-19 read |
| TS 25.424 vj00 | UTRAN Iur Interface Data Transport & Signalling | Rel-19 read |
| TS 25.426 vj00 | UTRAN Iur/Iub Transport Bearers | Rel-19 read |
| TS 25.432 vj00 | Iub NBAP Signalling Transport Specification | Rel-19 read |
| TS 25.434 vj00 | UTRAN Iub Interface Data Transport and Signalling | Rel-19 read |
| TS 27.060 vj00 | TE-MT Interworking for Packet Domain | Rel-19 read |
| TS 29.007 vj00 | PLMN-PSTN/ISDN Interworking Requirements | Rel-19 read |
| TS 29.061 vk10 | Packet Domain Interworking Requirements | Rel-20 read |
| TS 29.161 vc00 | 3GPP-WLAN Interworking Requirements | Rel-12 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 read |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 36.305 vj00 | UE Positioning in E-UTRAN Stage 2 | Rel-19 read |
| TS 36.412 vj00 | S1 Signalling Transport Specification | Rel-19 read |
| TS 36.422 vj00 | X2 Signalling Transport Specification | Rel-19 read |
| TS 36.442 vj00 | Signalling transport for M2 and M3 interfaces | Rel-19 read |
| TS 36.458 vj00 | SLm Interface Signalling Transport | Rel-19 read |
| TS 36.462 vj00 | Xw Interface Signalling Transport | Rel-19 read |
| TS 37.355 vj30 | LTE Positioning Protocol (LPP) | Rel-19 read |
| TS 37.472 vj00 | W1 Interface Signalling Transport Specification | Rel-19 read |
| TS 37.482 vj00 | E1 Signalling Transport Specification | Rel-19 read |
| TS 38.305 vj30 | NG-RAN UE Positioning Stage 2 | Rel-19 read |
| TS 38.412 vj00 | NG Signalling Transport | Rel-19 read |
| TS 38.415 vj10 | PDU Session User Plane Protocol | Rel-19 read |
| TS 38.422 vj00 | Xn Signalling Transport Specification | Rel-19 read |
| TS 38.462 vj00 | E1 Signalling Transport Specification | Rel-19 read |
| TS 38.472 vj00 | F1 Interface Signalling Transport Specification | Rel-19 read |