Re: [rtcweb] JSEP question: How to set up simulcast for server-originated calls?

Bernard Aboba <bernard.aboba@gmail.com> Mon, 05 November 2018 20:46 UTC

Return-Path: <bernard.aboba@gmail.com>
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 5331C12D4ED for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 12:46:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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=gmail.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 PahTqR5TCdU7 for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 12:46:33 -0800 (PST)
Received: from mail-ua1-x935.google.com (mail-ua1-x935.google.com [IPv6:2607:f8b0:4864:20::935]) (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 317EC1286E7 for <rtcweb@ietf.org>; Mon, 5 Nov 2018 12:46:33 -0800 (PST)
Received: by mail-ua1-x935.google.com with SMTP id o17so3708794uad.8 for <rtcweb@ietf.org>; Mon, 05 Nov 2018 12:46:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zNDYiHTfxgpN3DbnFU6B8qolXEbVe8oABG6NqmIgGq8=; b=YuER9SFed7YBQz07pt0yYwykkuYvbPtDq0leWygyy7xxTtTrCSk9ptaqR7I+CUoijZ zYrtdfA/snYq0KWqocvNtmi87+shJXMIeW45dl3vx7x2us2DW2XP2gVMHHYeBJwBkPnP a0dfzo90XZcGyIEGL2OzV2Vmx4PLWL9qfevFzoO664po7dfHlaLkOeg8DBvPoySskOaz XmRkjbw+XOaiwtPGfAQnkPBhBVEcN3UjV3p3Fsft5RLTumby7C6dknBLF+kWXSCuqqcB 1v+deZvXSiokvcLSvVpfi1JTSynUT4kcXxFxeMV4OhgD1WEcLeHnGGYlCfV655/4V52W AABQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zNDYiHTfxgpN3DbnFU6B8qolXEbVe8oABG6NqmIgGq8=; b=E3ui3in6ZhJiEEDVfU1f4cwYxmLN0JRhPfEYpuZBhgs2oSRvA5pyoMZcHIoU5iYWRJ dtr5u1sBTx5mD1OeiFeuhc2ddBfKxbHDHhRppQPd6hJuHkPo+L3S0Cnr0dZIYtr4uGaP LgJoDiHi0S5NhlGGConSoj1x/a4iMrtk896jJg0V7G7JMkwHuHK9UA0zWwXBbHa3KqEW LUz2K7dgxd1HWEJKjUKJ/6mrzrqzIBZjCM2y3TRs5gjgBTud1sHb5xsh4MiRuUVltBg8 h1V5N5BbwLBsry5rWPk7cwlGm1OPDPD5G5HgMvIuMOgbNSNumQrgKGbjWw5bPYtNw1wQ OSSQ==
X-Gm-Message-State: AGRZ1gIOv5jpnzukixh5kCSc9xs8S8Hkg7hIEbAtW9JFICWcCLAOWqwt EQVoX1NplmMaF5mhGQq0Uzq1MdfBmsXh2uLaoj4=
X-Google-Smtp-Source: AJdET5e1NBPUA0kEJQBMECgRdnDy21Sg8omYHQmTQI7eSFus/q82p0T0hM1c60C4MylmvqwWD/c89ip7BmlDG+O/f0Y=
X-Received: by 2002:ab0:60da:: with SMTP id g26mr5057280uam.104.1541450792009; Mon, 05 Nov 2018 12:46:32 -0800 (PST)
MIME-Version: 1.0
References: <185c8d1d-3971-ad09-eee0-a26bed446a96@alvestrand.no> <A5687AE0-7D07-46C8-AF93-7B0D0DE0BC4B@mozilla.com> <CAOW+2dveTZ8jtAyNNftv=fMi_C8LifvE8RtUuszg0-eUYcgANg@mail.gmail.com> <CA+ag07ZhVkvG5DNumOePgJdU03VUw-zu5YR2vM49yZp92dHX1Q@mail.gmail.com> <CALiegfkf28G-5KghLV3wKYYyhVdbr-sAP7gy69S3YuexCd+q-Q@mail.gmail.com> <CAOW+2dsmkaL=wk=_FpoO_3aLsV8TZL_SgFBUksEzRujDfRMQ-w@mail.gmail.com> <CALiegfnHaeBLu44R+TP4Ev0gNQKLfTXCvSyOzAJOZUr_7JgEYw@mail.gmail.com> <BDB6BAD6-4182-455C-B7BB-8D951C66003E@mozilla.com> <CALiegf=yao_g4EkazEpy3Eo00mCXTwQEjtPGii0-Z3wQGx6LAA@mail.gmail.com> <CA+ag07acP8sS3WjNPrY5WS8a6Ds7kYD56GH7host4d7QfftV=A@mail.gmail.com>
In-Reply-To: <CA+ag07acP8sS3WjNPrY5WS8a6Ds7kYD56GH7host4d7QfftV=A@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Mon, 05 Nov 2018 15:46:20 -0500
Message-ID: <CAOW+2dvK+LDjJg-oLj+QGQZeYqK0uR8nUXvvZFz9595XsH4zFA@mail.gmail.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Cc: Iñaki Baz Castillo <ibc@aliax.net>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e5863d0579f0fafe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/gzYeaFkR4kZKckT5iF5ZzITQS8Y>
Subject: Re: [rtcweb] JSEP question: How to set up simulcast for server-originated calls?
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: Mon, 05 Nov 2018 20:46:37 -0000

Sergio said:

"here could be a way to overcome this by setting all the send encodings
active flag to false when receiving a simulcast offer. Then app can do a
getParameters, get layer num and rids, configure the settings and enable
the desired ones by setting active to true."

[BA] Yes, this makes sense, and from Nil's note, it appears that this is
the way things work now in Firefox.

On Sun, Nov 4, 2018 at 7:37 PM Sergio Garcia Murillo <
sergio.garcia.murillo@gmail.com> wrote:

> there could be a way to overcome this by setting all the send encodings
> active flag to false when receiving a simulcast offer. Then app can do a
> getParameters, get layer num and rids, configure the settings and enable
> the desired ones by setting active to true.
>
> Best regards
> Sergio
>
> El lun., 5 nov. 2018 1:26, Iñaki Baz Castillo <ibc@aliax.net> escribió:
>
>> (On Mon, 5 Nov 2018 at 01:21, Nils Ohlmeier <nohlmeier@mozilla.com>
>> wrote:
>> >
>> > Here is a fiddle which demonstrates that just putting simulcast into
>> the offer, but not calling setEncodings() does not activate simulcast:
>> https://jsfiddle.net/x6qgab87/
>> > So the other side can’t force simulcast on the browser. If you provide
>> me with a demo which shows that it is possible, then that is a bug I’ll
>> happily fix for you.
>>
>> Ok, that's new. I remember many months ago when I reported this (I was
>> in fact producing simulcast based on remote SDP offer) and it was not
>> necessary to call sender.setParameters({ encodings }) after sRD and
>> before createOffer.
>>
>> Ok, this behavior makes more sense. BUT: it's not feasible because you
>> need to use hardcoded/fixed rid values (or manually do SDP parsing).
>>
>>
>> --
>> Iñaki Baz Castillo
>> <ibc@aliax.net>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>