RFC 5087: Time Division Multiplexing over IP (TDMoIP)
In plain English — editorial summary, not part of the RFC
Time Division Multiplexing over IP (TDMoIP) is a structure-aware method for transporting Time Division Multiplexed (TDM) signals using pseudowires (PWs). Being structure-aware, TDMoIP is able to ensure TDM structure integrity, and thus withstand network degradations better than structure-agnostic transport. Structure-aware methods can distinguish individual channels, enabling packet loss concealment and bandwidth conservation. Accessibility of TDM signaling facilitates mechanisms that exploit or manipulate signaling. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5087
- Published
- December 2007
- Authors
- Y(J). Stein; R. Shashoua; R. Insler; M. Anavi
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 50
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5254Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)Current
October 2008
- RFC 5287Control Protocol Extensions for the Setup of Time-Division Multiplexing (TDM) Pseudowires in MPLS NetworksCurrent
August 2008
- RFC 5542Definitions of Textual Conventions for Pseudowire (PW) ManagementCurrent
May 2009
- RFC 5003Attachment Individual Identifier (AII) Types for AggregationCurrent
September 2007
- RFC 4717Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS NetworksCurrent
December 2006
- RFC 4667Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP)Current
September 2006
- RFC 4619Encapsulation Methods for Transport of Frame Relay over Multiprotocol Label Switching (MPLS) NetworksCurrent
September 2006
- RFC 4618Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS NetworksCurrent
September 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?