RFC 5611: Layer Two Tunneling Protocol version 3 - Setup of Time-Division Multiplexing (TDM) Pseudowires
In plain English — editorial summary, not part of the RFC
This document defines extensions to the Layer Two Tunneling Protocol version 3 (L2TPv3) for support of structure-agnostic and structure-aware (Circuit Emulation Service over Packet Switched Network (CESoPSN) style) Time-Division Multiplexing (TDM) pseudowires. Support of structure-aware (Time-Division Multiplexing over IP (TDMoIP) style) pseudowires over L2TPv3 is left for further study. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5611
- Published
- August 2009
- Authors
- A. Vainshtein; S. Galtzur
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5287Control Protocol Extensions for the Setup of Time-Division Multiplexing (TDM) Pseudowires in MPLS NetworksCurrent
August 2008
- RFC 5087Time Division Multiplexing over IP (TDMoIP)Current
December 2007
- RFC 4817Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3Current
March 2007
- RFC 4667Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP)Current
September 2006
- RFC 7885Seamless Bidirectional Forwarding Detection (S-BFD) for Virtual Circuit Connectivity Verification (VCCV)Current
July 2016
- RFC 8159Keyed IPv6 TunnelCurrent
May 2017
- RFC 5613OSPF Link-Local SignalingCurrent
August 2009
- RFC 5614Mobile Ad Hoc Network (MANET) Extension of OSPF Using Connected Dominating Set (CDS) FloodingUpdated
August 2009
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?