Skip to main content

Early Event-Driven (EED) RTCP Feedback for Rapid IDMS

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Mario Montagud , Fernando Boronat , Hans Stokking
Last updated 2015-08-13 (Latest revision 2015-02-09)
RFC stream (None)
Intended RFC status (None)
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:


RFC 7272 defines two RTCP messages to enable Inter-Destination Media Synchronization (IDMS). However, if such RTCP messages are exchanged using the Regular RTCP reporting rules specified in RFC 3550, unacceptable delays can be originated when exchanging the synchronization information conveyed into RTCP packets. Accordingly, this document proposes Early Event-Driven (EED) RTCP reporting rules and messages to enable higher interactivity, dynamism, flexibility and accuracy when using RTP/RTCP for IDMS. Such IDMS extensions are targeted at providing faster reaction on dynamic situations, such as out-of-sync situations and channel change delays, as well as a finer granularity for synchronizing media-related events, while still adhering to the RTCP bandwidth bounds specified in RFC 3550. Besides, a new RTP/AVPF transport layer feedback message is proposed to allow the request of re-IDMS setting instructions (e.g., in case of RTCP packet loss) as well as rapid accommodation of latecomers in on-going sessions. Finally, this document also discusses various situations in which the reporting of Reduced-Size RTCP packets (RFC 3556) can be applicable and beneficial for IDMS.


Mario Montagud
Fernando Boronat
Hans Stokking

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