Re: [Dart] Treatment of RTCP - proposed text

Colin Perkins <csp@csperkins.org> Thu, 28 August 2014 08:56 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: dart@ietfa.amsl.com
Delivered-To: dart@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B7451A0B80; Thu, 28 Aug 2014 01:56:23 -0700 (PDT)
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 RUzDhZSvN6A7; Thu, 28 Aug 2014 01:56:20 -0700 (PDT)
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 25AF71A0B73; Thu, 28 Aug 2014 01:56:20 -0700 (PDT)
Received: from [130.209.247.112] (port=57845 helo=mangole.dcs.gla.ac.uk) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1XMvV5-0005ut-Ft; Thu, 28 Aug 2014 09:56:13 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <emc6d51676-add4-404b-bd0a-d6dbf3833abb@sydney>
Date: Thu, 28 Aug 2014 09:55:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <439DC2BA-155E-4880-A665-0DFCEB48BFAC@csperkins.org>
References: <emc6d51676-add4-404b-bd0a-d6dbf3833abb@sydney>
To: "Paul E. Jones" <paulej@packetizer.com>
X-Mailer: Apple Mail (2.1878.6)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: http://mailarchive.ietf.org/arch/msg/dart/DiXYO4_Ye5CqtN-lZqbslIlOwsc
Cc: Ben Campbell <ben@nostrum.com>, Michael Welzl <michawe@ifi.uio.no>, "draft-ietf-dart-dscp-rtp.all@tools.ietf.org" <draft-ietf-dart-dscp-rtp.all@tools.ietf.org>, "Black, David" <david.black@emc.com>, "dart@ietf.org" <dart@ietf.org>, "avt@ietf.org WG" <avt@ietf.org>
Subject: Re: [Dart] Treatment of RTCP - proposed text
X-BeenThere: dart@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"DiffServ Applied to RTP Transports discussion list\"" <dart.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dart>, <mailto:dart-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dart/>
List-Post: <mailto:dart@ietf.org>
List-Help: <mailto:dart-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dart>, <mailto:dart-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Aug 2014 08:56:23 -0000

Paul, David,

On 28 Aug 2014, at 04:13, Paul E. Jones <paulej@packetizer.com> wrote:
> Should it be the DSCP value of the SSRC being reported on or the DSCP of the SSRC sender?  My thought that was if Alice and Bob are sending flows to each other and Bob is sending audio using EF, then when Bob sends out a Sender Report, the packet would be marked EF.  

Agree. An SSRC should use the same marking it would use to send packets, and not the marking of the received packets.

> The way this is worded, if Alice is sending packets using CS0, then Bob would mark his SR's using CS0.
> 
> I'm not sure how to handle the RR's, though, particularly of a receive-only device.  We could say it would be the same as the flow being reported on, but there might be 31 such flows being reported on.  Perhaps if there is agreement that the RTCP packets will be marked in the same way as the sender would send its media, then we say the reports should be marked in the same was as it would if it did send media.

A receive-only device should mark in the way it would if it sent media, I agree.

> So, do we want RTCP packets to be marked the same as the media flow transmitted or the same as the received media flow?

Transmitted, I think.

Colin



> Paul
> 
> ------ Original Message ------
> From: "Black, David" <david.black@emc.com>
> To: "Paul E. Jones" <paulej@packetizer.com>om>; "Ben Campbell" <ben@nostrum.com>om>; "Michael Welzl" <michawe@ifi.uio.no>no>; "Colin Perkins" <csp@csperkins.org>
> Cc: "draft-ietf-dart-dscp-rtp.all@tools.ietf.org" <draft-ietf-dart-dscp-rtp.all@tools.ietf.org>rg>; "dart@ietf.org" <dart@ietf.org>rg>; "avt@ietf.org WG" <avt@ietf.org>rg>; "Black, David" <david.black@emc.com>
> Sent: 8/27/2014 9:58:34 PM
> Subject: Treatment of RTCP - proposed text
> 
>> Trying to propose some text here:
>> 
>> OLD
>>   o Should use a single DSCP for an RTCP session, primarily to avoid
>>      RTCP reordering (and because there is no compelling reason for use
>>      of different drop precedences). One of the PHBs and associated
>>      DSCP used for the associated RTP traffic would be an appropriate
>>      choice. [Editor's note: This bullet is an open technical issue.]
>> NEW
>>   o Should use the same DSCP for RTCP reports as used for the RTP stream
>>      that is being reported on when that DSCP is known by the RTCP sender.
>>      When an RTP stream uses multiple DSCPs that differ only in drop
>>      precedence, RTCP reports on that RTP stream should use the DSCP with
>>      the least likelihood of drop to favor delivery of the RTCP reports.
>>      When a single RTCP message reports on multiple RTP streams that
>>      are sent with different DSCPs, the RTCP sender should choose one
>>      of those DSCPs. When the RTCP sender does not know what
>> DSCP or DSCPs were used to send an RTP stream, it should choose
>> a DSCP that it would use to send a similar RTP stream.
>> 
>> The latter sentence is courtesy of the fact that there will be cases
>> where the RTCP sender will not know what DSCP or DSCPs were used to send
>> the RTP stream, due to en-route remarking.
>> 
>> If that text looks close, I'll edit further and try to get the -05 submitted
>> by the end of this week.
>> 
>> Thanks,
>> --David
>> 
>>> -----Original Message-----
>>> From: Paul E. Jones [mailto:paulej@packetizer.com]
>>> Sent: Wednesday, August 27, 2014 6:53 PM
>>> To: Ben Campbell; Michael Welzl; Colin Perkins; Black, David
>>> Cc: draft-ietf-dart-dscp-rtp.all@tools.ietf.org; dart@ietf.org; avt@ietf.org
>>> WG
>>> Subject: Re: [Dart] [AVTCORE] Treatment of RTCP (was Re: Colin Perkins
>>> comments - WGLC: draft-ietf-dart-dscp-rtp-02)
>>> 
>>> RTCP might not be used for RTT calculations (it might; I just doubt it's
>>> terribly useful), but RTCP might be used to convey QoE measurements or
>>> one-way delay information useful for RMCAT.
>>> 
>>> I think there is agreement that the DSCP value applied to the RTCP
>>> packet for a given SSRC sender should align with the DSCP value used for
>>> the corresponding RTP packets of that sender. In the case where an AFxx
>>> class is used, I'm not sure there is agreement (though no disagreement).
>>>   I stated my view that we should use the lowest drop precedence in that
>>> case, but others should weigh in.
>>> 
>>> Paul
>>> 
>>> ------ Original Message ------
>>> From: "Ben Campbell" <ben@nostrum.com>
>>> To: "Michael Welzl" <michawe@ifi.uio.no>no>; "Colin Perkins"
>>> <csp@csperkins.org>rg>; "Paul E. Jones" <paulej@packetizer.com>om>; "Black,
>>> David" <david.black@emc.com>
>>> Cc: "draft-ietf-dart-dscp-rtp.all@tools.ietf.org"
>>> <draft-ietf-dart-dscp-rtp.all@tools.ietf.org>rg>; "dart@ietf.org"
>>> <dart@ietf.org>rg>; "avt@ietf.org WG" <avt@ietf.org>
>>> Sent: 8/27/2014 4:48:37 PM
>>> Subject: Re: [Dart] [AVTCORE] Treatment of RTCP (was Re: Colin Perkins
>>> comments - WGLC: draft-ietf-dart-dscp-rtp-02)
>>> 
>>> >On Aug 27, 2014, at 3:45 PM, Michael Welzl <michawe@ifi.uio.no> wrote:
>>> >
>>> >> I don't know the beginning of this but I can help go up the stack:
>>> >>
>>> >> for the short dialogue between Colin and me, the conclusion is: Colin
>>> >>is right. RTCP probably won't be used by congestion control to
>>> >>estimate the RTT.
>>> >>
>>> >
>>> >Thanks, Michael, I think that fits with some earlier conversations as
>>> >well.
>>> >
>>> >Colin and Paul (and David):
>>> >
>>> >Are we converging on what guidance to put into the DART draft?
>>> >
>>> >Thanks!
>>> >
>>> >Ben.
>>> >
>>> >
>>> >_______________________________________________
>>> >Dart mailing list
>>> >Dart@ietf.org
>>> >https://www.ietf.org/mailman/listinfo/dart
>> 
> 



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