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

Iñaki Baz Castillo <ibc@aliax.net> Mon, 05 November 2018 13:23 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 CA93612D4E8 for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 05:23:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=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 y_8NItsVC7SB for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 05:23:07 -0800 (PST)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (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 99EBC1298C5 for <rtcweb@ietf.org>; Mon, 5 Nov 2018 05:23:07 -0800 (PST)
Received: by mail-vs1-xe34.google.com with SMTP id v205so5068403vsc.3 for <rtcweb@ietf.org>; Mon, 05 Nov 2018 05:23:07 -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; bh=vToioPivPVy7pVCRzQzSH/SnlPp3R3gwi6APhSPUrZM=; b=QazsxnMSEQdUhz4cPsXoi/lB6ZfwBSzYbwOZEz4TIuONkTTAWlkfzSljf06sbhqC// 8MDIa64CcWQ/rTNor7u8yUJyfq/Rv8RClIoDAaSDMb8jqeVGVrouw/gHWIxdqkGp0vcr heUJUvsNV8AvWb+AmVuUQQbUAM+jTsYAiziiLJFADjWe2noreI3Vkf1anuJQx88W/Gqg 37TbIv5YtjiOgz7b8MgrHtrbW98tgeObFHkg6y/v1aSJi7+pysn2jjIOHWsZYBx6g5oe CRICkdCPdYzdMrovLqd5YtDWp72hsdGDVfGxPXScpuQhfmIXDpcz3hMsD9w3VpIcHKaw S0sQ==
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=vToioPivPVy7pVCRzQzSH/SnlPp3R3gwi6APhSPUrZM=; b=PqQUiQ/iA0j6sj7gApMzFDVpR05bgHqLDNpndBhf2dV+Mby57OSf55PVw00IJ2fNSl XsSUk029fwBtJc4+dU59T+BVLDZqGPnIWMj36IeaA/P81DKq/1UKdU2FypF72UDm9MJR omO6MAoo7H6oMxvDK4BzWIgyC7d6U2/kVqYqv4e/39u4TmzurojJRWoLP4NqjVYUuqe0 RS4bSvvPYSYkxBK2xFWdyUwtc5cauDyud5QKbTt59y8sLBN0HK8zZ7Zr37jPJgHnm+H8 +yL5xrZA8ijhxnhnM5sxdoS/f4E7/4QnXgdfu7/6wIAbF1QQT60A4hBqsf3HWbmRzfJ0 2NnA==
X-Gm-Message-State: AGRZ1gIghnHycz3Zpg2Rg3hTwBF8RV1/CRAg/MdO37O9ZltBoPbIFnV6 vsk6lconWAMH7nEhG+/W2AmKbey8SvdJW2S82WIRI0QY
X-Google-Smtp-Source: AJdET5fydruL3/6G591khDiMf0FBFbbDjIgeUJx34kgLPzjiVVSmM4YHvfpywYTs4//CmLvfTfiHAOu1qoZAD6dQ/B0=
X-Received: by 2002:a67:6346:: with SMTP id x67mr8993238vsb.114.1541424186323; Mon, 05 Nov 2018 05:23:06 -0800 (PST)
MIME-Version: 1.0
References: <185c8d1d-3971-ad09-eee0-a26bed446a96@alvestrand.no> <CALiegfmbghnBtDt=wfCAbOWi5SDFTi2qPgDOuXHRazKSvvCKNQ@mail.gmail.com> <CA+ag07YD3oSuL=R=h-28waha4b7xf7haU+-oWuNbzO_sBY4MQw@mail.gmail.com> <e567832e-1918-d51c-6f00-a732547c0a8e@alvestrand.no> <CA+ag07byo1vReeo2uMKxmF1tnzW+4CJSMPLaJO79H0s9j0PO0g@mail.gmail.com> <31fb92c1-2934-c33f-a3cf-552f027eacda@alvestrand.no> <bb7f863b-510c-f460-c9b0-843d500784b8@gmail.com> <5db76ada-b896-7eba-b42e-85b2e239dc42@alvestrand.no> <db90e287-145b-5ffe-18c0-f38faed76c07@gmail.com> <CALiegf=7yJJEbGT9SrbcEBBo9cnBbPimDP_oaTzJL63hrnXGoQ@mail.gmail.com> <CA+ag07ZuGYBhr=djPP=nLXLX96Yp2O4H8rJT2z8RVvNTiky2qw@mail.gmail.com>
In-Reply-To: <CA+ag07ZuGYBhr=djPP=nLXLX96Yp2O4H8rJT2z8RVvNTiky2qw@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 05 Nov 2018 14:22:54 +0100
Message-ID: <CALiegfmOsLgeO-jkj20qKa0=w-xwHJdKD12Py_Dvades8Jjnrw@mail.gmail.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Cc: Harald Alvestrand <harald@alvestrand.no>, rtcweb@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001311cf0579eac96f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/-MPpUicWzIIAcVtsr8aaTVl9u2s>
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 13:23:12 -0000

May be, but without knowing in advance the limit in different
devices/browsers, how many rids do you expect those SFUs will place in the
offer? It would be the "lowest common denominator" which would not satisfy
to anyone.

El lun., 5 nov. 2018 14:17, Sergio Garcia Murillo <
sergio.garcia.murillo@gmail.com> escribió:

> if remote offer has more rids than what the browser support then the m
> line should be rejected.
>
>
> El lun., 5 nov. 2018 14:14, Iñaki Baz Castillo <ibc@aliax.net> escribió:
>
>> As Harlad said before, sender.getParameters() should not return more
>> times than the number of encodings the browser supports, so of the remote
>> offer has more than those, we have an API problem.
>>
>> El lun., 5 nov. 2018 14:03, Sergio Garcia Murillo <
>> sergio.garcia.murillo@gmail.com> escribió:
>>
>>> On 05/11/2018 12:45, Harald Alvestrand wrote:
>>> > I do fear that simulcast will continue to affect parts of the spec that
>>> > we don't expect it to. But we don't have the luxury of specifying it
>>> > halfway; either we rip it out altogether, or we specify it in enough
>>> > detail for interoperable implementation.
>>>
>>> I agree to that. If we are able to find an "easy" (i.e. not introducing
>>> too many changes) I would not have any issues adding support to that.
>>>
>>> Something like:
>>>
>>> - Browser adds a track via addTrack
>>>
>>> - Browser call SRD with a recv simulcast m-line offer
>>>
>>> - The transceiver is created with one send encoding per rid offered by
>>> the SFU with default values and all send encodings except first one with
>>> active=false (this would be the only required change)
>>>
>>> ----- browser encodes/sends a single rtp stream, same as if the remote
>>> offer was a non simulcast stream--
>>>
>>> -Browser calls sender.getParameters(), modifies the desired send
>>> encoding parameters ( scaleResolutionDownBy,  maxFramerate, maxBitrate,
>>> etc) and enables them by setting active=true
>>>
>>> Would this approach fulfill the requirements?
>>>
>>> Best regards
>>>
>>> Sergio
>>>
>>>
>>>