L2TP

Layer Two Tunneling Protocol

Protocol →
Introduced in Rel-4

L2TP is a tunneling protocol used in 3GPP networks to transport Layer 2 packets over IP, primarily in the PGW to establish user data tunnels to external packet data networks.

Category
Protocol
Introduced
Rel-4
Where
Core Network › 5G Core
Specifications
4 specs
L2TP Description Purpose Related Detected Changes Specifications

Description

Layer Two Tunneling Protocol (L2TP) is a standardized tunneling protocol, originally defined by the IETF (RFC 2661, later updated), that is adopted and referenced within 3GPP specifications for specific interfaces. In the 3GPP architecture, L2TPv2 is used primarily over the SGi interface (between the Packet Data Network Gateway - PGW and an external packet data network) and within the Packet Data Network (PDN) connection setup. It provides a mechanism to tunnel Point-to-Point Protocol (PPP) frames or other Layer 2 traffic over an IP network, creating a virtual point-to-point link.

L2TP operates by establishing a control connection and one or more sessions within that connection. The L2TP Access Concentrator (LAC) and L2TP Network Server (LNS) are the two endpoints. In a 3GPP context, the User Equipment (UE) acts as a PPP peer, the PGW often incorporates the LNS function, and an external broadband network server (BNS) or the UE's enterprise network may act as the LAC. The protocol encapsulates the original PPP frames inside L2TP packets, which are then further encapsulated in UDP/IP for transport across the network. This creates a secure, logical extension of a Layer 2 network over an IP infrastructure.

Key components within 3GPP include the L2TP control message exchange for tunnel/session establishment, maintenance, and teardown, and the data encapsulation process. Its role is crucial for certain types of PDN connectivity, especially for interworking with legacy dial-up networks, providing Virtual Private Network (VPN) access for users, or for specific fixed-mobile convergence scenarios. It allows mobile operators to offer seamless secure access to corporate networks or ISP services by extending a traditional dial-up or broadband PPP session over the mobile core network.

Purpose & Motivation

L2TP was incorporated into 3GPP specifications to solve the problem of providing remote, authenticated network access over IP-based core networks. In early 3GPP releases (Rel-4/5), there was a need to support interworking with existing Internet Service Provider (ISP) infrastructures that relied heavily on PPP for user authentication (like CHAP/PAP) and IP address assignment. L2TP provided a standardized way to tunnel these PPP sessions from the UE, through the mobile packet core, to the ISP's network server.

Its creation was motivated by the transition from circuit-switched data (where the UE had a direct modem-like connection) to packet-switched core networks. Simply sending raw PPP over the GPRS network was not feasible. L2TP addressed this by defining a robust tunneling mechanism that could traverse Network Address Translation (NAT) devices (using UDP), provide its own sequencing and delivery guarantees, and separate control and data planes. It enabled operators to leverage existing AAA (Authentication, Authorization, Accounting) and billing systems built for dial-up PPP users.

While newer, more integrated authentication methods like EAP have become prevalent for direct mobile access, L2TP remains relevant for specific use cases requiring transparent Layer 2 tunnel termination outside the mobile operator's network, such as certain types of enterprise VPNs or legacy service integration, providing a bridge between modern mobile IP architectures and traditional network access servers.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (33 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-4, normative work from Rel-16.

Rel-16 3 changes

In Release 16, the L2TP function was enhanced to introduce support for redundant transmission at the transport layer. This includes the necessary negotiation procedures for establishing this redundancy. Furthermore, the release added protocol support for Ethernet PDN types within the EPS architecture.

  • Protocol support for Ethernet PDN in EPS TS 29.244CR0281
  • Supporting redundant transmission at transport layer Negotiation TS 29.244CR0287
  • Redundant Transmission on transport layer TS 29.244CR0400
Rel-17 17 changes

In Release 17, the enhancements for the L2TP function focused on expanding its integration and support within the 5G architecture. Key additions included providing L2TP information through the N6 interface and enabling protocol impacts on N4, N4mb, Nmb8, Nmb9, and N6mb interfaces specifically for 5G Multicast/Broadcast Service (5G MBS) data delivery. The release also introduced updates to support L2TP within CUPS architectures and for its use in both RADIUS and Diameter message flows, alongside various procedural corrections and fixes.

  • Updates to support L2TP for CUPS TS 29.061CR0536
  • Updates to support L2TP in RADIUS message flow TS 29.061CR0537
  • Updates to support L2TP in Diameter message flow TS 29.061CR0538
  • L2TP Corrections TS 29.244CR0561
  • Protocol impact on N4mb for 5G MBS TS 29.244CR0559
  • Protocol impact on N4 for 5G MBS TS 29.244CR0560

+ 11 more changes

Rel-18 7 changes

In Release 18, the L2TP function was enhanced with new capabilities for marking the End of Data Burst and for handling tunnel failures with specific cause reporting. It was extended to support N6 tunneling between the V-UPF and V-EASDF for HR-SBO PDU sessions with overlapping IP addresses. Furthermore, the protocol description received extensions, procedural enhancements, and necessary corrections.

  • Protocol Description for End of Data Burst marking TS 29.244CR0756
  • Protocol Description TS 29.244CR0769
  • Extensions to Protocol Description requested by SA4 TS 29.244CR0794
  • N6 tunneling between V-UPF and V-EASDF for HR-SBO PDU sessions with overlapping IP addresses TS 29.244CR0847
  • L2TP tunnel failure cause TS 29.244CR0670
  • Corrections to Protocol Description TS 29.244CR0793

+ 1 more changes

Rel-19 6 changes

In Release 19, the L2TP function was updated to support the MoQ (Media over QUIC) transport protocol on the N4 interface, including the necessary procedure descriptions. Additional enhancements introduced protocol-specific configuration parameters for N6 delay measurements, which included new security-related parameters for this function. The release also contained essential corrections, such as fixing a wrong reference to the Domain Name Protocol field and correcting the RTP Payload Type range within the protocol description.

  • Support of MoQ Transport protocol on N4 TS 29.244CR0897
  • Procedure description on support of MoQ protocol TS 29.244CR0921
  • Security related protocol-specific configuration parameters for N6 delay measurement TS 29.244CR0975
  • Wrong reference to the Domain Name Protocol field TS 29.244CR0878
  • Protocol-specific configuration parameters for N6 delay measurements TS 29.244CR0980
  • Essential correction on the RTP Payload Type range for Protocol Description TS 29.244CR0952

Explore further

Broader topics and technologies where L2TP plays a role.

Defining Specifications

3GPP specifications that define or reference L2TP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.060 vj00 GPRS Service Description Stage 2 Rel-19
TS 29.061 vj00 Packet Domain Interworking for PLMN Rel-19
TS 29.244 vj40 PFCP Specification for Control/User Plane Separation Rel-19
TS 29.561 vj30 5G Interworking with External Data Networks Rel-19