IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Wed, 07 November 2018 02:56 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 83CA8127332 for <rtcweb@ietfa.amsl.com>; Tue, 6 Nov 2018 18:56:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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 Bu3vcAvU_MiR for <rtcweb@ietfa.amsl.com>; Tue, 6 Nov 2018 18:56:11 -0800 (PST)
Received: from mail-vs1-xe2e.google.com (mail-vs1-xe2e.google.com [IPv6:2607:f8b0:4864:20::e2e]) (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 E8186126CB6 for <rtcweb@ietf.org>; Tue, 6 Nov 2018 18:56:10 -0800 (PST)
Received: by mail-vs1-xe2e.google.com with SMTP id y27so6808542vsi.1 for <rtcweb@ietf.org>; Tue, 06 Nov 2018 18:56:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aliax-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=diH48zxE1jXlKd4RTpZievTuGDiGfkLUeX0SQI7glaU=; b=OSfrRf8z5+Qmh+OZQzH+tt9+tgaCct/GiZmsgD1bgHbWgRCxpWytsry6DFW+5gXOUJ 6l0RrMCUjP1PWYOe8Bx3apajm+AOghp2pb8zDOeKl27TpnEx+Sq7Nu/ihL3vMKMk82xv y2l4wxglLvE2aNp7/sl/uIqwe2xrGq5JwxkCZTBjyvgAUJ85QzdSBIZxTx6IVJh164lR rKfUjco+3+XCOkE9OSYF8U+co63c7po7LfDkG6pvZOQqoQP23kQTKPKMVYiaFZXKxweV 0SACkPEkAIouwdjy0+zJu4u2HOhOasMO24KNDa3Z2nCMhFmDfVUzxhikbjSHp82Vxs0O VqQA==
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:content-transfer-encoding; bh=diH48zxE1jXlKd4RTpZievTuGDiGfkLUeX0SQI7glaU=; b=JgtCBk0cuY6lxh6LQxlW6xa8C6Hpx7Voy958uVg+uJNGF3GImqDO3VsmwdUmZ1tXjL xm2CqOy5qK3/BkxuVVKzs85yNNTL8q9/uwOCuFYmEUe7j6nIop43gA0WE//sVJnms63M Y3b2KX0JDJrJCkUyzf5TK1nIHDrbzuIvIwJ3XVKc9AqYYyVt10H48tyoGZNercVD+BXP 7fekJSRfjcUWmXJlwNtNMo3vMRubc453FIMrk1Z4Qslap6QiXgKQHdzO9947/R7V3xCh rGVgPjbAdP9zWJOYqhP7hgjqBj8dYIOBEcgbN2UAR0KRo3A8tLF5ian/ZvqBsff8ndGp Ns+Q==
X-Gm-Message-State: AGRZ1gKki4wUpe394QbaOkPJt4XyI09UgGD7IQsxdmGOcvHYhEmkoEnm JJKVNqhDu2olupvOZ1e5wVKd8YRPeISLDLmVFDnkqg==
X-Google-Smtp-Source: AJdET5dwh9sqSvHe43TDzLSLz21CQbW9Nw+xPZE4CN/1nDAcy2188/K2xEF/SErN4E+TErMMnMWdDjolJ2ZiR8YippM=
X-Received: by 2002:a67:3659:: with SMTP id d86mr46095vsa.17.1541559369906; Tue, 06 Nov 2018 18:56:09 -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> <CALiegfnChcJ9W52e0C-CyyCw+9jUnJg0Wszv7DTd_CtpvEC2Xg@mail.gmail.com> <5FB0A50F-DAF3-47C4-A5F5-8DA20586C9E2@iii.ca> <CALiegf=tFL1zagfp7qyPBWn6r+NQ8SKW=OBKc=6ZOVwgHzcHWg@mail.gmail.com> <C6D65A1E-F701-4E47-9B82-B4EA444BA7A0@iii.ca>
In-Reply-To: <C6D65A1E-F701-4E47-9B82-B4EA444BA7A0@iii.ca>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Wed, 07 Nov 2018 03:55:58 +0100
Message-ID: <CALiegfk2cietY-W4mRQMnDbF-MAqESkNNom0W07abiMhEwDWuA@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Cc: Bernard Aboba <bernard.aboba@gmail.com>, rtcweb@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/NH4cm5gOOkVyj9kY8rGXbHucXKk>
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: Wed, 07 Nov 2018 02:56:14 -0000

On Wed, 7 Nov 2018 at 03:15, Cullen Jennings <fluffy@iii.ca> wrote:
>
>
> On Nov 5, 2018, at 7:14 PM, Iñaki Baz Castillo <ibc@aliax.net> wrote:
>
> If you excluded the word "interop" from any rationale, life would be
> much better, specially here where such an interop:
>
> 1) does not exist
> 2) is not needed
>
> To be clear: No app in the world is or will be NEVER ready to enable
> simulcast auto-magically just because it eventually receives a
> different SDP offer from the remote. The app developers would already
> figured out different ways to enable simulcast that would just not
> allow such an auto-magic "upgrade".
>
>
>
> Let me put this as politely and straight forward as I can. You are wrong.

May be. But all proposals here about enabling local simulcast upon
receipt of a remote SDP offer require app/JS interaction. The local
app must be able to decide whether send simulcast or not given the
current CPU/battery usage or network conditions. It does not make any
sense that just because the app receives a remote blob, it starts
sending 2-3 video layers without app consent.

That's why, as the discussion has been evolving, the winning proposal
is that in which, upon receipt of the remote SDP offer, the app must
enable simulcast by itself.


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

v2.23.0 | Report a Bug | By Email