Re: [Dart] [AVTCORE] Treatment of RTCP (was Re: Colin Perkins comments - WGLC: draft-ietf-dart-dscp-rtp-02)

Michael Welzl <> Wed, 27 August 2014 18:47 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 0C3C51A007D; Wed, 27 Aug 2014 11:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.668] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ufcLNKelW1JC; Wed, 27 Aug 2014 11:47:08 -0700 (PDT)
Received: from ( [IPv6:2001:700:100:10::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 78B581A6F0C; Wed, 27 Aug 2014 11:47:08 -0700 (PDT)
Received: from ([]) by with esmtp (Exim 4.80.1) (envelope-from <>) id 1XMiFN-00016X-GY; Wed, 27 Aug 2014 20:47:05 +0200
Received: from ([] helo=[]) by with esmtpsa (TLSv1:AES128-SHA:128) user michawe (Exim 4.80) (envelope-from <>) id 1XMiFM-0000Jk-Kj; Wed, 27 Aug 2014 20:47:05 +0200
Content-Type: multipart/alternative; boundary="Apple-Mail=_B0CEE16D-C655-4D5C-A948-D1AB874731FD"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Michael Welzl <>
In-Reply-To: <>
Date: Wed, 27 Aug 2014 20:47:03 +0200
Message-Id: <>
References: <embac59e09-6dad-42df-94b2-7daa46d31d5d@sydney> <> <> <> <> <>
To: Colin Perkins <>
X-Mailer: Apple Mail (2.1878.2)
X-UiO-Ratelimit-Test: rcpts/h 13 msgs/h 3 sum rcpts/h 18 sum msgs/h 5 total rcpts 19576 max rcpts/h 44 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, TVD_RCVD_IP=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 82E6BEA8F050D04A54E242733969D6EB6CC4B95A
X-UiO-SPAM-Test: remote_host: spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 3 total 180 max/h 7 blacklist 0 greylist 0 ratelimit 0
Cc: "Paul E. Jones" <>, "Black, David" <>, "" <>, " WG" <>, "" <>
Subject: Re: [Dart] [AVTCORE] Treatment of RTCP (was Re: Colin Perkins comments - WGLC: draft-ietf-dart-dscp-rtp-02)
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"DiffServ Applied to RTP Transports discussion list\"" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 27 Aug 2014 18:47:10 -0000

On 27. aug. 2014, at 20:42, Colin Perkins <> wrote:

> On 27 Aug 2014, at 19:39, Michael Welzl <> wrote:
>> On 27. aug. 2014, at 18:00, Colin Perkins <> wrote:
>>> On 26 Aug 2014, at 17:38, Black, David <> wrote:
>>>>> The more difficult case is when an SSRC is sending video using different
>>>>> markings for RTP packets carrying the I- and P-frames. Should that SSRC then
>>>>> mark its RTCP packets like the RTP packets carrying I-frames, like the RTP
>>>>> packets carrying P-frames, or what?
>>>> Answering a question w/a question :-), how are those reports likely to be used?
>>>> For example, if the primary use of these reports is to adjust a variable rate
>>>> codec's sending rate, the P-frame info is probably more useful as indicative
>>>> of what's happening to the traffic that the network drops first when the going
>>>> gets rough (or whose delivery w/o loss indicates that a sending rate increase
>>>> may be reasonable), which suggests P-frame-like RTCP report marking.
>>> I doubt the RTT estimate derived from RTCP is used for congestion control, since it’s too infrequent to get insight into the dynamics. It’s for user experience reporting, maybe rough clustering of receivers, that sort of thing. 
>> I'd agree if I didn't have the impression, in RMCAT, that nothing but RTP / RTCP is allowed?!  So can we send extra packets to probe for the RTT?
> I’d expect RMCAT will probe the one-way delay variation by measuring the arrival times of RTP packets, and report that in RTCP once per video frame (or so). That would give a much more accurate measurement than a single-packet sample of the RTT derived from RTCP, and would still allow per-frame adaptation.

I agree that this is a useful signal to use - but I think you still need a rough idea of the RTT to be able to interoperate with TCP, else you may cause TCP to go into RTOs and be ignorant of that. But this could perhaps be a more coarse signal - maybe that's okay. I think this is reasonable.

I wonder if your RTCP draft in RMCAT should clarify this?  (sorry if it does already, didn't check)