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

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Tue, 06 November 2018 01:10 UTC

Return-Path: <sergio.garcia.murillo@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 50BB012F295 for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 17:10:30 -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 LLWXzWRBz3mT for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 17:10:28 -0800 (PST)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 16B72126DBF for <rtcweb@ietf.org>; Mon, 5 Nov 2018 17:10:28 -0800 (PST)
Received: by mail-wr1-x432.google.com with SMTP id y15-v6so11582913wru.9 for <rtcweb@ietf.org>; Mon, 05 Nov 2018 17:10:27 -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=euyh7wRYq1Yf7oxftp+8CwfETr4OXTpp3kpYidqKVXM=; b=Rl9Uiq2l1tdZAcH9GoSRe/CBjSUU2CIr9WXAIn7UxjxgBAxTvvQtddUZsL03wQVQ+n 50wQT40QpEYH3PgDnKXuJpGF4AWu0WH5H773ps5tEAZaQcTe3xXnDbpB3tNPh9DCX4kU PDXax72qScIT3LTUKBhwtygRHG5T0FrTjIY6piZeZc9UuglHol5Zh3INFrf7vrILgKzq X5ArgVsYomSKPr/t9QeWo238MWhlU6cejkNwhLuU1hA0CiaTy/Fe2bwqfHBjJIuYXxbg rQHad83xPuW+0sWrbOQhgZP3DKk9baavPMnuV5iQdBdOVEvw/a5rkj4BrCFU073T1cm3 eAVQ==
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=euyh7wRYq1Yf7oxftp+8CwfETr4OXTpp3kpYidqKVXM=; b=p9nM1jGFGVJXByFmDmpFdVSK7ePH0pD8XWC6WbHvE115REom1DgTLreP75ag0a7NJo OJ7Zc4oTiyP03sDlG2KGROxdDvkMJ3JhqNNdd2OdHpd/NhCmbV9+YnF+9uMNzhtQh9Jw onQZ6wMJvQv4Rp1wXF2yMksZ4uy9wtnH5ARHZ+t/LnLjOeFQuGweGMyWwtffIapC1z/a rnFxGgcEElbOl4Wj9GggWsayYH06ItlCXDid3fVf8F4sc1mLnnVcu/sPbpy7lHWTlqvu SOigF7cesfeDYSPixZvHs5Up9uqAepZdBYl6McTEPrx2BckDGUxwC0nG0d7XuA+sw1nL ZMag==
X-Gm-Message-State: AGRZ1gJxBaZw8wRnPzqf76/G1BLn3JNUKwDS8fv+LqeiSBHdP6qtT4u8 sHJA6PdAtlXsoojvYQ34R2BTJL7waPcJdlwKTlw=
X-Google-Smtp-Source: AJdET5fVBMJNeOknWy9GHMvPTQXhXN/3lqUw7MtmEovKCHAP4HFeUaeouLIP95m68dJkWuVmudU6TXcHwyu/syV8kho=
X-Received: by 2002:adf:9170:: with SMTP id j103-v6mr17424278wrj.217.1541466626574; Mon, 05 Nov 2018 17:10:26 -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> <150c76b7-64eb-2e75-c9e0-2f503e705e4b@alvestrand.no> <CAOW+2duSN5u7u+JrSpvE509k47j7Uuu4=gKy5eMFeAnw5p=kiA@mail.gmail.com> <e547e9b3-90c5-fe3b-8f72-6038f2bfd5a6@alvestrand.no> <50f7f9d1-5259-57d0-4d49-093e98164961@gmail.com>
In-Reply-To: <50f7f9d1-5259-57d0-4d49-093e98164961@gmail.com>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Date: Tue, 06 Nov 2018 02:10:14 +0100
Message-ID: <CA+ag07ZzFQZ5g4e8ATJxKMRgyCuSZjEKJ6ra3=713h2E2sAp7Q@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>, Bernard Aboba <bernard.aboba@gmail.com>
Cc: RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b5cccd0579f4aa7c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/Xi4VJj3FoXm1LJUAOsiOaohNzfs>
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: Tue, 06 Nov 2018 01:10:31 -0000

changed my mind, as there is a corner case:

addTrack
setParameters with multiple encodings
SRD with a simulcast recv offer with imcompatible rids than the one in the
transceiver

what will happen then?


El mar., 6 nov. 2018 1:59, Sergio Garcia Murillo <
sergio.garcia.murillo@gmail.com> escribió:

> On 06/11/2018 0:50, Harald Alvestrand wrote:
> >> [BA] Most of the code examples I have seen that use addTrack for
> >> simulcast call setParameters prior to createOffer().  To allow this,
> >> we might consider saying that when addTrack returns, the encodings
> >> are initially null, and so can be set by setParameters().
> >
> > We could also allow the number of encodings to be changed in general,
> > with the proviso that if you increase the number, you have to inspect
> > the result to see how many you got (browser would drop extra elements).
>
> IMHO the number of encodings should be allowed to be changed by
> setParameters (either for a transceiver started via addTrack or
> addTransceiver) until the corresponding m-line is negotiated by an SDP
> O/A (until it has a mid value?). Changing the number of encodings after
> that, I don't think it is allowed by the simulcast draft.
>
> Best regards
>
> Sergio
>
>