RFC 4326: Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS)
In plain English — editorial summary, not part of the RFC
The MPEG-2 Transport Stream (TS) has been widely accepted not only for providing digital TV services, but also as a subnetwork technology for building IP networks. This document describes a Unidirectional Lightweight Encapsulation (ULE) mechanism for the transport of IPv4 and IPv6 Datagrams and other network protocol packets directly over the ISO MPEG-2 Transport Stream as TS Private Data. ULE specifies a base encapsulation format and supports an extension format that allows it to carry additional header information to assist in network/Receiver processing. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4326
- Published
- December 2005
- Authors
- G. Fairhurst; B. Collini-Nocker
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 42
- Also known as
- —
- Updated by:
- RFC 7280
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 4331Quota and Size Properties for Distributed Authoring and Versioning (DAV) CollectionsCurrent
February 2006
- RFC 4314IMAP4 Access Control List (ACL) ExtensionCurrent
December 2005
- RFC 4356Mapping Between the Multimedia Messaging Service (MMS) and Internet MailCurrent
January 2006
- RFC 4287The Atom Syndication FormatUpdated
December 2005
- RFC 4259A Framework for Transmission of IP Datagrams over MPEG-2 NetworksCurrent
December 2005
- RFC 4239Internet Voice Messaging (IVM)Current
November 2005
- RFC 4238Voice Message Routing ServiceUpdated
October 2005
- RFC 4237Voice Messaging Directory ServiceCurrent
October 2005
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?