Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-multi-stream-optimisation-12.txt
Colin Perkins <csp@csperkins.org> Wed, 02 March 2016 23:08 UTC
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF6B1B33FD for <avt@ietfa.amsl.com>; Wed, 2 Mar 2016 15:08:13 -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] autolearn=ham
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 OTa4dcL6O4YU for <avt@ietfa.amsl.com>; Wed, 2 Mar 2016 15:07:33 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B13021B33E9 for <avt@ietf.org>; Wed, 2 Mar 2016 15:07:33 -0800 (PST)
Received: from [81.187.2.149] (port=34965 helo=[192.168.0.86]) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1abFrf-0003lW-KJ for avt@ietf.org; Wed, 02 Mar 2016 23:07:31 +0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <20160302225718.3886.89543.idtracker@ietfa.amsl.com>
Date: Wed, 02 Mar 2016 23:07:30 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A68EAB2-E291-4A5D-B5EF-030FA5F5AA98@csperkins.org>
References: <20160302225718.3886.89543.idtracker@ietfa.amsl.com>
To: IETF AVTCore WG <avt@ietf.org>
X-Mailer: Apple Mail (2.3112)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/B1ZsGtKz32t2UPx92awoKCa-JDk>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-multi-stream-optimisation-12.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2016 23:08:13 -0000
> On 2 Mar 2016, at 22:57, Internet-Drafts@ietf.org wrote: > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Audio/Video Transport Core Maintenance of the IETF. > > Title : Sending Multiple RTP Streams in a Single RTP Session: Grouping RTCP Reception Statistics and Other Feedback > Authors : Jonathan Lennox > Magnus Westerlund > Qin Wu > Colin Perkins > Filename : draft-ietf-avtcore-rtp-multi-stream-optimisation-12.txt > Pages : 18 > Date : 2016-03-02 > > Abstract: > RTP allows multiple RTP streams to be sent in a single session, but > requires each Synchronisation 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 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. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-multi-stream-optimisation/ > > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-ietf-avtcore-rtp-multi-stream-optimisation-12 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-multi-stream-optimisation-12 Section 3.6 of the draft is updated, to clarify that the a=rtcp-rgrp SDP attribute is a property attribute with multiplexing category of IDENTICAL. The description of how the attribute is used with SDP offer/answer is also expanded and clarified, in the same section -- Colin Perkins https://csperkins.org/
- [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-mult… internet-drafts
- Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-… Colin Perkins