RFC 5458: Security Requirements for the Unidirectional Lightweight Encapsulation (ULE) Protocol
In plain English — editorial summary, not part of the RFC
The MPEG-2 standard defined by ISO 13818-1 supports a range of transmission methods for a variety of services. This document provides a threat analysis and derives the security requirements when using the Transport Stream, TS, to support an Internet network-layer using Unidirectional Lightweight Encapsulation (ULE) defined in RFC 4326. The document also provides the motivation for link-layer security for a ULE Stream. A ULE Stream may be used to send IPv4 packets, IPv6 packets, and other Protocol Data Units (PDUs) to an arbitrarily large number of Receivers supporting unicast and/or multicast transmission. The analysis also describes applicability to the Generic Stream Encapsulation (GSE) defined by the Digital Video Broadcasting (DVB) Project. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5458
- Published
- March 2009
- Authors
- H. Cruickshank; P. Pillai; M. Noisternig; S. Iyengar
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5463Sieve Email Filtering: Ihave ExtensionCurrent
March 2009
- RFC 5465The IMAP NOTIFY ExtensionCurrent
February 2009
- RFC 5466IMAP4 Extension for Named Searches (Filters)Current
February 2009
- RFC 5442LEMONADE Architecture - Supporting Open Mobile Alliance (OMA) Mobile Email (MEM) Using Internet MailCurrent
March 2009
- RFC 5437Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP)Current
January 2009
- RFC 5436Sieve Notification Mechanism: mailtoCurrent
January 2009
- RFC 5435Sieve Email Filtering: Extension for NotificationsUpdated
January 2009
- RFC 5429Sieve Email Filtering: Reject and Extended Reject ExtensionsCurrent
March 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?