Re: [Dart] DART dscp-rtp draft: Proposed RTCP text

Colin Perkins <> Thu, 28 August 2014 20:59 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id C5C381A01E2; Thu, 28 Aug 2014 13:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mo6wazB3t0fY; Thu, 28 Aug 2014 13:59:09 -0700 (PDT)
Received: from ( [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 (Postfix) with ESMTPS id 4A1681A01D0; Thu, 28 Aug 2014 13:59:09 -0700 (PDT)
Received: from [] (port=44391 helo=[]) by with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <>) id 1XN6mg-0005HN-Gk; Thu, 28 Aug 2014 21:59:07 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Colin Perkins <>
In-Reply-To: <>
Date: Thu, 28 Aug 2014 21:59:03 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: "Black, David" <>
X-Mailer: Apple Mail (2.1878.6)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Cc: "" <>, "" <>, " WG \(\)" <>
Subject: Re: [Dart] DART dscp-rtp draft: Proposed RTCP text
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: Thu, 28 Aug 2014 20:59:15 -0000

On 28 Aug 2014, at 20:45, Black, David <> wrote:
> Here's the proposed new section 5.4, with the RTCP multi-stream reporting
> optimizations text moved into that new section from its current location
> at the end of 5.3, plus the rewritten Section 6 guideline bullet:
> 5.4.  DiffServ and RTCP
>   The RTP Control Protocol (RTCP) [RFC3550] is used with RTP to monitor
>   quality of service and convey information about RTP session
>   participants.  A sender of RTCP packets that also sends RTP packets
>   (i.e., originates an RTP stream) should use the same DSCP marking for
>   both types of packets.  If an RTCP sender doesn't send any RTP
>   packets, it should mark its RTCP packets with the DSCP that it would
>   use if it did send RTP packets.  If the RTCP sender uses or would use
>   multiple DSCPs that differ only in drop precedence for RTP, then it
>   should use the DSCP with the least likelihood of drop for RTCP to
>   increase the likelihood of RTCP packet delivery.

This looks okay (the correction in your next message is good also). 

You might also add something along the lines of “If the SDP bundle extension [cite] is used to negotiate sending multiple types of media in a single RTP session, then the receivers will send separate RTCP reports for each type of media, using a separate SSRC for each media type; those RTCP reports need to be marked with the DSCP corresponding to the type of media handled by the reporting SSRC.” 

>   This guidance may result in different DSCP markings for RTP streams
>   and RTCP receiver reports about those RTP streams.  The resulting
>   variation in network QoS treatment by traffic direction could result
>   in unrepresentative round trip time (RTT) estimates that don't
>   correspond to consistent network QoS treatment in both directions.

I don’t think this is a problem. The media doesn’t get consistent network QoS treatment in both directions, and the RTCP is trying to sample the RTT seen by the media, so this is fine.

>   RTCP receiver reports may be relatively infrequent (e.g., may be sent
>   only once per video frame rendered) and hence the resulting RTT
>   estimates are of limited utility for congestion control (although
>   they have other important uses, see [RFC3550]).  For this reason, it
>   is not important that RTCP receiver reports receive the same network
>   QoS treatment as the RTP stream or streams being reported on.
>   RTCP multi-stream reporting optimizations for an RTP session
>   [I-D.ietf-avtcore-rtp-multi-stream-optimisation] assume that the RTP
>   streams involved experience the same network behavior, including
>   packet loss.  This mechanism is highly inappropriate when the RTP
>   streams involved use different DSCPs, even if the corresponding PHBs
>   differ solely in drop precedence.

This could maybe say “received RTP streams”, since it’s okay to use the rtp-multi-stream-optimisation if you send with different DSCPs (the optimisation is optimising how you send reports about what you receive).

> 6.  Guidelines
> [... snip ...]
>   o  Should use a single DSCP for RTCP packets, which should be a DSCP
>      used for RTP packets that are or would be sent by the same sender,
>      see Section 5.4.

Perhaps “Each SSRC should use a single DSCP for RTCP … used by RTP packets that are or would be sent by that SSRC…”? Just “sender" could be ambiguous, since an endpoint could be a sender for several streams, each of which has a separate SSRC and could use a different DSCP.

Colin Perkins