RFC 4454: Asynchronous Transfer Mode (ATM) 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 an extensible tunneling protocol to transport layer 2 services over IP networks. This document describes the specifics of how to use the L2TP control plane for Asynchronous Transfer Mode (ATM) Pseudowires and provides guidelines for transporting various ATM services over an IP network. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4454
- Published
- May 2006
- Authors
- S. Singh; M. Townsley; C. Pignataro
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 26
- 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 4456BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)Updated
April 2006
- RFC 4448Encapsulation Methods for Transport of Ethernet over MPLS NetworksUpdated
April 2006
- RFC 4447Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)Obsoleted
April 2006
- RFC 4461Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)Current
April 2006
- RFC 4446IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)Current
April 2006
- RFC 4444Management Information Base for Intermediate System to Intermediate System (IS-IS)Current
April 2006
- RFC 4428Analysis of Generalized Multi-Protocol Label Switching (GMPLS)-based Recovery Mechanisms (including Protection and Restoration)Current
March 2006
- RFC 4427Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS)Current
March 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?