RFC 4817: Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3
In plain English — editorial summary, not part of the RFC
The Layer 2 Tunneling Protocol, Version 3 (L2TPv3) defines a protocol for tunneling a variety of payload types over IP networks. This document defines how to carry an MPLS label stack and its payload over the L2TPv3 data encapsulation. This enables an application that traditionally requires an MPLS-enabled core network, to utilize an L2TPv3 encapsulation over an IP network instead. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4817
- Published
- March 2007
- Authors
- M. Townsley; C. Pignataro; S. Wainner; T. Seely; J. Young
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4667Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP)Current
September 2006
- RFC 5611Layer Two Tunneling Protocol version 3 - Setup of Time-Division Multiplexing (TDM) PseudowiresCurrent
August 2009
- RFC 7885Seamless Bidirectional Forwarding Detection (S-BFD) for Virtual Circuit Connectivity Verification (VCCV)Current
July 2016
- RFC 8159Keyed IPv6 TunnelCurrent
May 2017
- RFC 8596MPLS Transport Encapsulation for the Service Function Chaining (SFC) Network Service Header (NSH)Current
June 2019
- RFC 4816Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous Transfer Mode (ATM) Transparent Cell Transport ServiceCurrent
February 2007
- RFC 4803Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information BaseCurrent
February 2007
- RFC 4802Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information BaseCurrent
February 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?