RFC 8861 on Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol (RTCP) Reception Statistics and Other Feedback
rfc-editor@rfc-editor.org Tue, 19 January 2021 00:46 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2E633A0FB6; Mon, 18 Jan 2021 16:46:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I7N007-LBmW6; Mon, 18 Jan 2021 16:46:50 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EB563A106D; Mon, 18 Jan 2021 16:46:46 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E74FBF407C2; Mon, 18 Jan 2021 16:46:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8861 on Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol (RTCP) Reception Statistics and Other Feedback
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, avt@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210119004630.E74FBF407C2@rfc-editor.org>
Date: Mon, 18 Jan 2021 16:46:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/YP2CXB6dQe7bDKGv_gDe7yIxnwI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 00:46:58 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8861
Title: Sending Multiple RTP Streams in a Single
RTP Session: Grouping RTP Control Protocol (RTCP)
Reception Statistics and Other Feedback
Author: J. Lennox,
M. Westerlund,
Q. Wu,
C. Perkins
Status: Standards Track
Stream: IETF
Date: January 2021
Mailbox: jonathan.lennox@8x8.com,
magnus.westerlund@ericsson.com,
bill.wu@huawei.com,
csp@csperkins.org
Pages: 16
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-avtcore-rtp-multi-stream-optimisation-12.txt
URL: https://www.rfc-editor.org/info/rfc8861
DOI: 10.17487/RFC8861
RTP allows multiple RTP streams to be sent in a single session but
requires each Synchronization Source (SSRC) to send RTP Control
Protocol (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 normally 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.
This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC