RFC 4719: Transport of Ethernet Frames over Layer 2 Tunneling Protocol Version 3 (L2TPv3)
In plain English — editorial summary, not part of the RFC
This document describes the transport of Ethernet frames over the Layer 2 Tunneling Protocol, Version 3 (L2TPv3). This includes the transport of Ethernet port-to-port frames as well as the transport of Ethernet VLAN frames. The mechanism described in this document can be used in the creation of Pseudowires to transport Ethernet frames over an IP network. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4719
- Published
- November 2006
- Authors
- R. Aggarwal; M. Townsley; M. Dos Santos
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
- Updated by:
- RFC 5641
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7172Transparent Interconnection of Lots of Links (TRILL): Fine-Grained LabelingCurrent
May 2014
- RFC 7176Transparent Interconnection of Lots of Links (TRILL) Use of IS-ISCurrent
May 2014
- RFC 7968Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination DataCurrent
August 2016
- RFC 8383Transparent Interconnection of Lots of Links (TRILL): Address Flush MessageCurrent
May 2018
- RFC 4720Pseudowire Emulation Edge-to-Edge (PWE3) Frame Check Sequence RetentionCurrent
November 2006
- RFC 4717Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS NetworksCurrent
December 2006
- RFC 4724Graceful Restart Mechanism for BGPUpdated
January 2007
- RFC 4726A Framework for Inter-Domain Multiprotocol Label Switching Traffic EngineeringCurrent
November 2006
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?