RFC 4591: Frame Relay over Layer 2 Tunneling Protocol Version 3 (L2TPv3)
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 data link protocols over IP networks. This document describes the specifics of how to tunnel Frame Relay over L2TPv3, including frame encapsulation, virtual-circuit creation and deletion, and status change notification. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4591
- Published
- August 2006
- Authors
- M. Townsley; G. Wilkie; S. Booth; S. Bryant; J. Lau
- 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 4593Generic Threats to Routing ProtocolsCurrent
October 2006
- RFC 4601Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)Obsoleted
August 2006
- RFC 4602Protocol Independent Multicast - Sparse Mode (PIM-SM) IETF Proposed Standard Requirements AnalysisCurrent
August 2006
- RFC 4577OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 2006
- RFC 4576Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 2006
- RFC 4606Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) ControlUpdated
August 2006
- RFC 4607Source-Specific Multicast for IPCurrent
August 2006
- RFC 4610Anycast-RP Using Protocol Independent Multicast (PIM)Current
August 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?