Rapid Synchronisation of RTP Flows
draft-perkins-avt-rapid-rtp-sync-03

 
Document Type Replaced Internet-Draft (individual)
Last updated 2009-07-24 (latest revision 2009-03-09)
Replaced by draft-ietf-avt-rapid-rtp-sync
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-avt-rapid-rtp-sync
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-perkins-avt-rapid-rtp-sync-03.txt

Abstract

This memo outlines how RTP multimedia sessions are synchronised, and discusses how rapidly such synchronisation can occur. We show that most RTP sessions can be synchronised immediately, but that the use of video switching multipoint conference units (MCUs) or large source specific multicast (SSM) groups can greatly increase the initial synchronisation delay. This increase in delay can be unacceptable to some applications that use layered and/or multi-description codecs. This memo updates the RTP Control Protocol (RTCP) timing rules to reduce the initial synchronisation delay for SSM sessions. A new feedback packet is defined for use with the Extended RTP Profile for RTCP-based Feedback (RTP/AVPF), allowing video switching MCUs to rapidly request resynchronisation. Two new RTP header extensions are defined to allow rapid synchronisation of late joiners, and guarantee correct timestamp based decoding order recovery for layered codecs in the presence of clock skew.

Authors

Colin Perkins (csp@csperkins.org)
Thomas Schierl (thomas.schierl@hhi.fraunhofer.de)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)