[rtcweb] Clarification on simulcast and RID and RepairedRtpStreamId

Iñaki Baz Castillo <ibc@aliax.net> Sat, 01 December 2018 12:04 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5827E12F1A5 for <rtcweb@ietfa.amsl.com>; Sat, 1 Dec 2018 04:04:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.36
X-Spam-Level:
X-Spam-Status: No, score=-3.36 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 F_0eIuIZ9RBL for <rtcweb@ietfa.amsl.com>; Sat, 1 Dec 2018 04:04:20 -0800 (PST)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (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 3324F12D4F2 for <rtcweb@ietf.org>; Sat, 1 Dec 2018 04:04:20 -0800 (PST)
Received: by mail-vs1-xe2c.google.com with SMTP id v10so4931412vsv.12 for <rtcweb@ietf.org>; Sat, 01 Dec 2018 04:04:19 -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=1KHJJelN1KTfrot6EVxBAYJ22i/DRu3mViTCvIIdoWc=; b=0GljII3JhV9jQ55//idF7LeGxkRW1UnE9zIEFcyK/buHoHz07Q8ZwDnK1JjkVNoJeQ KiwcBRrld6M4qRyxYJCew6AQLskXF11ycMVuhB18Y2L38jwoWpXMnzxxHfIRnn4CbL/N KsOci4jMUy3J8Ia5v2CrV81RwkMvCduhABm5kjCqj4xf8+leziAT4Rhj7eNmNc+269pL XLxmcRXgCBiSeOOu+iBCcr3mrykvM5u0/TSnnDcyGf7YsAizZ63sedOPFPjTtl3YO97w 4wRUWYFsuvvFm8Om93k0oYVXiOeVddY7y98HAw/vXYu8XqCTLw6mxTeMxBgsHsQe7l1p qSLA==
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=1KHJJelN1KTfrot6EVxBAYJ22i/DRu3mViTCvIIdoWc=; b=uYzpkS60c5oGlKgd5jXBQrU4O7m9rz0KVPUSgyV1PgZLpbpSAcIVehrPFzI1dkurjG PrlC6mEtmGJsgPmful8FUHCvFzmITwZhOyfinmZP/nKorVXRfFdehx2T/bWBl1tMUrvj XDv9gWHB1I3FSQzRCChvRm3ne+dFIrSYNSYfYrdYqh12LrhDjEsRDaIQpxGkqZPwSi39 vpNrBjh7ZT70EDN+Uypyj5lkpSSK9YXW8aiZM4fm5om8ymfB3l4GdW/OVK/jBdWULeGm ohoJIRajrZYUZ4a+WxvcQD8ll9Q30DKME2y1is+lCmSsdm7BD1C1VTSSBnAbY1B2rZpa AorA==
X-Gm-Message-State: AA+aEWatsg0/i0Wu91QoE7Pl8L0Uz5/7qzUA0bt+DxX/rfJlkQUfIi4i jiArRIAohPQmYa5UirW9kQCtVjv+v0L+BAoVgZKFBYPvFCc=
X-Google-Smtp-Source: AFSGD/Vz3jd72gaPRyCWp8w4lyG4H9IFuqQROwJg7W9Sra9q04qXYvM3q6JICs4o8lKiiy8HnNIkUrTVvlAJhjrC7M0=
X-Received: by 2002:a67:6204:: with SMTP id w4mr4153708vsb.68.1543665858336; Sat, 01 Dec 2018 04:04:18 -0800 (PST)
MIME-Version: 1.0
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Sat, 1 Dec 2018 13:04:06 +0100
Message-ID: <CALiegfm=++8o=Ou1Tgu6bxyiVdw2ysgM5HnjRqi2hJBoy476yg@mail.gmail.com>
To: rtcweb@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/3JNZ8cyBz20YvbRQCJVz3b-WKuI>
Subject: [rtcweb] Clarification on simulcast and RID and RepairedRtpStreamId
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Dec 2018 12:04:23 -0000

Hi,

We are almost in 2019 and, personally, I don't know yet which the
proper/standard way for simulcast + RTX is.

Clearly, RID must be used to send simulcast so, instead of signaling
a=ssrc lines in the offer, the offerer signals a=rid values for all
the simulcast streams. The remote learns the associated SSRC upon
receipt of the first RTP packet by matching its RTP RID extension
value. This is clearly specified in
https://tools.ietf.org/html/draft-ietf-avtext-rid-09 and Firefox does
properly implement it.

Now, the issue is when adding RTX to simulcast streams. Theoretically
(if I'm not wrong) the sender should signal both the a=rid of media
streams and the a=rrid of their associated RTX streams, and then send
RTP RID in media RTP packets and RTP RepairedRtpStreamId in RTX RTP
packets.

NOTE: Not sure about a=rrid, I can't find it in any draft. So:

Q1: Is there any spec defining the SDP syntax to indicate
RepairedRtpStreamId values in the SDP?

Q2: Is THIS (RID + RepairedRtpStreamId) the proper way to go for
simulcast + RTX?


Also, when it comes to receive media with RTX it's clear that WebRTC
does not define how to receive simulcast streams for WebRTC clients
(browsers), so browsers must receive a single stream plus an optional
RTX stream.

In this case, as far as a=mid plus RTP MID extension is used (or
a=ssrc) signaled, there is zero need for RID. However, how is RTX
supposed to be signaled in this case? Chrome expects ""a=ssrc-group:
FID MEDIA_SSRC RTX_SSRC" in the remote SDP to be able to receive an
additional RTX stream.

Q3: Is this the way to go for receiving a single stream with RTX?


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