Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol (RTCP) Reception Statistics and Other Feedback
draft-ietf-avtcore-rtp-multi-stream-optimisation-12

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: avtcore-chairs@ietf.org, ben@nostrum.com, draft-ietf-avtcore-rtp-multi-stream-optimisation@ietf.org, avt@ietf.org, roni.even@mail01.huawei.com, "The IESG" <iesg@ietf.org>, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Sending Multiple RTP Streams in a Single RTP Session: Grouping RTCP Reception Statistics and Other Feedback' to Proposed Standard (draft-ietf-avtcore-rtp-multi-stream-optimisation-12.txt)

The IESG has approved the following document:
- 'Sending Multiple RTP Streams in a Single RTP Session: Grouping RTCP
   Reception Statistics and Other Feedback'
  (draft-ietf-avtcore-rtp-multi-stream-optimisation-12.txt) as Proposed
Standard

This document is the product of the Audio/Video Transport Core
Maintenance Working Group.

The IESG contact persons are Barry Leiba, Ben Campbell and Alissa Cooper.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-multi-stream-optimisation/

Ballot Text

Technical Summary

RTP allows multiple media streams to be sent in a single session, but requires each Synchronization Source (SSRC) to send RTCP reception   quality reports for every other SSRC visible in the session.  This causes the number of RTCP reception reports to grow with the number of SSRCs, rather than the number of endpoints.  In many cases most of these RTCP reception reports are unnecessary, since all SSRCs of an endpoint are co-located and see the same reception quality.  This memo defines a Reporting Group extension to RTCP to reduce the reporting overhead in such scenarios.

Working Group Summary

The document was discussed in the meetings and on the mailing list. The open issues were addressed and there are no open issues, there was consensus on the content of the document.

Document Quality

This work was done based on input from RTCWEB WG and vendors will support it.

Personnel

Roni Even is the Document Shepherd.
The responsible AD is Ben Campbell.

RFC Editor Note