[rmcat] Doubt regarding REMB and SSRCs

Iñaki Baz Castillo <ibc@aliax.net> Wed, 01 March 2017 13:49 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF6C1294F3 for <rmcat@ietfa.amsl.com>; Wed, 1 Mar 2017 05:49:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aliax-net.20150623.gappssmtp.com
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 P-FcL7hSA__n for <rmcat@ietfa.amsl.com>; Wed, 1 Mar 2017 05:49:53 -0800 (PST)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98AF8129493 for <rmcat@ietf.org>; Wed, 1 Mar 2017 05:49:53 -0800 (PST)
Received: by mail-wr0-x235.google.com with SMTP id u48so30608984wrc.0 for <rmcat@ietf.org>; Wed, 01 Mar 2017 05:49:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aliax-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=hugE3IuYKPPXw5Pxtc40kxDd3kBtoEUxc7PWtdUWvKc=; b=PN9Tk3s3eflqy9zorirqzteH5cn77tEeQRTZ32a4DZbMnJjt2HfD1/wOuf1RFOklhm zPm3EzgKrtHuIo6vOcibTcuiI8xaaUzWYh9/jSsJeLipYJyy1Fci0d3MloHBZCf7Jw6q AAfIRLTPvyrieHi347p1kPrvFuam7oA8ATaf+TvD//YKNHTbqeMKWVb9V1ky6bNI/ZSj 1mZvwaeNW7DKwX51pKhJ3qF/CBqc9NffkP+x6XIIby3D981Kf/u9pngm+jY8h0c56fx3 weKQfc4dyEoNVDqH90zsY9SB2ccD68VFQiENnEOEWwBNXc5HLHK/8zizJNamUQmZGq/V x6jA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=hugE3IuYKPPXw5Pxtc40kxDd3kBtoEUxc7PWtdUWvKc=; b=KPJuNiqS6g8fJyFr3ckKH+EddKnDWlHvgUtG3fkPPnPeAHb+ZtOT9kSxK+MJ7u8rno onmWN/guROtg2zh0EqsbQu74v8bjeNsE7hqcTGwnXLHfAFcECtCo6Lt2VkyfVLmAGcVs lwIM8PJC6fEthny3IoB/CNBMCFE4S+X4sI3zUyfi8XBXDz3Rx0+rDU1EB/v/KaMJmyEA 4/EJlbyrf6i4IpezNL1cYFfe8CtL/WQSKmJdX8SQBfnZB6gHaW9uYP037eOorucvcHsG X5bZdMlAjmiidp/kydyF9zF1irQQnAYM/1ztJUysESYtltTLC9VVGawe2D1gETRUYpjk cPnA==
X-Gm-Message-State: AMke39mvpLgeAJ0b8kstzpIUbHOFILiX+7D/xtLNPaMe11O6gijhLUvTqauaZcYhUa2w2cNwoqWzuK8uNQTzzQ==
X-Received: by 10.223.178.9 with SMTP id u9mr6865412wra.121.1488376191711; Wed, 01 Mar 2017 05:49:51 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.182.85 with HTTP; Wed, 1 Mar 2017 05:49:31 -0800 (PST)
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Wed, 1 Mar 2017 14:49:31 +0100
Message-ID: <CALiegf=jXMXtOBy=HKJqptWhB_xYGGshKTDJrnX2_n-gcB+d5A@mail.gmail.com>
To: rmcat@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/ZNGmTcO2LXXevzcCIxUPsL2xHcA>
Subject: [rmcat] Doubt regarding REMB and SSRCs
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2017 13:49:55 -0000

Hi,

It's not clear for me what the "SSRC feedback" entries in the REMB
message mean. According to the draft [*]:

--------------------
  Num SSRC (8 bits):  Number of SSRCs in this message.

  SSRC feedback (32 bits): Consists of one or more SSRC entries which
  this feedback message applies to.
--------------------

At the same time, the draft says:

---------------------
   This feedback message is used to notify a sender of multiple media
   streams over the same RTP session of the total estimated available
   bit rate on the path to the receiving side of this RTP session.
---------------------

The meaning of "RTP session" is hard to explain nowadays, so I'll
assume it means "a media transport" (which in the context of WebRTC
points to an ICE established "connection" which can carry multiple
SSRC streams).

So, if for example Alice is receiving audio (SSRC 1111) and video
(SSRC 2222) over a BUNDLEd transport, and assuming Alice can just
receive 500 kbits/s, how should REMB messages generated by Alice look
like?

Should these REMB messages contain both SSRC 1111 and SSRC 2222 and
indicate 500000 as media bit rate?

What would happen if Alice sends a REMB just including the SSRC 1111
and 500000 as media bit rate? Should Bob limit its audio bitrate up to
500kbit/s and send whatever he wants regarding its video stream?


Thanks a lot.



[*] https://tools.ietf.org/html/draft-alvestrand-rmcat-remb-03


-- 
Iñaki Baz Castillo
<ibc@aliax.net>