Splicing for MPEG2-TS Problem Statement in RTP Sessions
draft-xia-avt-splicing-for-mpeg2ts-ps-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jinwei Xia , Hui Xia , Jinhui Zhang | ||
| Last updated | 2010-04-20 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The base MPEG2-TS splicing related protocols, i.e., Digital Program Insertion Splicing API [SCTE30] and Digital Program Insertion Cueing Message for Cable [SCTE35], only take into account how to insert the content (e.g., spot advertisements of various lengths, program substitution, public service announcements, etc) into any MPEG2-TS output multiplex on the splicer , as well as how to carry notification of upcoming splicing and other timing information in the transport stream, but not give enough mechanisms to direct the underlying transport protocol such as RTP how to compatibly work with the MPEG2-TS splicing. This memo highlights the issues of what's the impact on RTP and RTCP when performing splicing between the primary channel and the insertion channel.
Authors
Jinwei Xia
Hui Xia
Jinhui Zhang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)