Re: [AVTCORE] [rtcweb] I-D Action: draft-lennox-rtcweb-rtp-media-type-mux-00.txt

Colin Perkins <csp@csperkins.org> Sun, 13 November 2011 16:04 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD3921F8B0D; Sun, 13 Nov 2011 08:04:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pl5pyTqUfgCE; Sun, 13 Nov 2011 08:04:55 -0800 (PST)
Received: from anchor-msapost-2.mail.demon.net (anchor-msapost-2.mail.demon.net [195.173.77.165]) by ietfa.amsl.com (Postfix) with ESMTP id 1C77A21F8B08; Sun, 13 Nov 2011 08:04:55 -0800 (PST)
Received: from dhcp-4355.meeting.ietf.org ([130.129.67.85]) by anchor-post-2.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RPcYB-0005yP-jH; Sun, 13 Nov 2011 16:04:55 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <0B68D2E0-3480-47FB-8427-4032FD7B18F6@vidyo.com>
Date: Mon, 14 Nov 2011 00:04:48 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C0CDA262-3B5E-4BD5-8B67-EA399136D98B@csperkins.org>
References: <20111024232740.11885.97235.idtracker@ietfa.amsl.com> <C66DE732-1C39-4AB6-A7E0-A4CF687BB0D8@vidyo.com> <462F77C3-8CAD-4699-9238-71B5C9EF7F9B@csperkins.org> <0B68D2E0-3480-47FB-8427-4032FD7B18F6@vidyo.com>
To: Jonathan Lennox <jonathan@vidyo.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] [rtcweb] I-D Action: draft-lennox-rtcweb-rtp-media-type-mux-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sun, 13 Nov 2011 16:04:56 -0000

Jonathan,

A more compelling argument for reporting from all SSRCs may be that various AVPF and RTCP XR packets make no sense unless sent from the SSRC corresponding to the correct media type. Sending just those, but not regular RTCP reports, will cause havoc to the RTCP participant timeout rules, and SSRC collision detection, unless you signal and heavily special-case the code. This doesn't seem worth it, for tiny bandwidth savings.

Reporting on yourself is harder to defend, I agree, but the potential to confuse monitoring equipment (and given the activity in XRBLOCK, someone must care about that…), and the additional signalling needed, again seem to outweigh the bandwidth cost.

Colin



On 27 Oct 2011, at 23:57, Jonathan Lennox wrote:
> Hi, Colin --
> 
> Thanks for taking a look my draft!
> 
> I saw this recommendation in the multiplex-architecture draft, after I finished my own (I didn't get a chance to read any other -00 drafts before finishing my own before the deadline).
> 
> I think this is an AVTCore issue, so I'm following up there...further discussion should probably just be on AVTCore, unless there are WebRTC-specific issues.
> 
> 
> The multiplexing-architecture draft in general is a very good draft -- it's extremely thorough and useful -- but I admit to not being very convinced by that section of it.
> 
> At small numbers of sources, self-reporting and cross-reporting does indeed use a fairly small amount of bandwidth, but the problem is that their bandwidth usage is quadratic in the number of sources, since every source must report on every other. So as the number of sources grows, they begin to consume all RTCP bandwidth sending redundant or trivial information.
> 
> And this for the sake of third-party monitors, which (personally) I've never seen deployed outside a research environment, and seem architecturally dubious to me, at least for offer-answer negotiated streams. (IPTV and other declarative-SDP architectures are probably different.)
> 
> On Oct 27, 2011, at 11:12 AM, Colin Perkins wrote:
> 
>> Jonathan,
>> 
>> Thanks for submitting. This is a good draft.
>> 
>> One comment: Section 3.1 suggests that a source generating multiple RTP streams, with multiple SSRCs, should not send RTCP reports for its own media, and should pick a single SSRC to use when sending reports on other media. I agree that this would save a small amount of bandwidth, but I think the savings are negligible, it complicates the monitoring model, and so is a mistake. We talk about this in draft-westerlund-avtcore-multiplex-architecture-00 (Section 9, in particular).
>> 
>> Cheers,
>> Colin
> 
> --
> Jonathan Lennox
> jonathan@vidyo.com
> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb



-- 
Colin Perkins
http://csperkins.org/