IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Mon, 05 November 2018 22:20 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 D43271286D9 for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 14:20:11 -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 Bhi2xhkUX4PK for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 14:20:09 -0800 (PST)
Received: from mail-vk1-xa35.google.com (mail-vk1-xa35.google.com [IPv6:2607:f8b0:4864:20::a35]) (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 9B2141252B7 for <rtcweb@ietf.org>; Mon, 5 Nov 2018 14:20:09 -0800 (PST)
Received: by mail-vk1-xa35.google.com with SMTP id h128so2406635vkg.11 for <rtcweb@ietf.org>; Mon, 05 Nov 2018 14:20:09 -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=tsKZj8UF6siuRsa3sEODyMfz1kZyIRbO413hrla2Tdc=; b=JhDO14mZgUnN+SUWNwZZtS0SDcmvYcRLXxqLfFdpmgetBhRzOazOAWqEadg5oE40Ej 7YlxSU3HSEFU8fIjcTDigTZDLeGrYiLynqM4aVjcNMRDj2sj9wwWOMLPwvKGXH5bZ1pH 0Abzpw1Y6YiJFjvLLZhs3wprbeOF5Cx/zqW33chxTc4Ss1/xQkzNiOn23GbE1MnedlIT JQHjTifeNwAFQxrPDPGGdJ3wkER2UTiORVes++TU3WXSg8XXo+fBpw0tSe8QUmQVHft5 FBaOQxICnw8RKmyT+HuCt9YDcGNSJvBrg03uwz5M8cqVBzkvctTQ9LnfGScYGl4U2ecY Q/QA==
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=tsKZj8UF6siuRsa3sEODyMfz1kZyIRbO413hrla2Tdc=; b=Pg2uNAPP6X9INaK59iPWAzKFSDkocyS05M1XJY/mwcCPv/WYnaeCKSG1dhbfAB81Bx tIgT1hzT8R38Hr1q0moS2wSy2W4r22DY4ooeEYMhiken9gQ2yKokx4ltB/3d9IdTWHEX NAoyX5/CweJcZH5TuSO0rbIGz3LLu3pAf40qjiLSo/YCxAA34c2jVQ9ImGg5hDsNzN6r rcZoICIMWthcoVY8NvrD+ujYO4Cna/oZf4Y54EM72ZBEov2g5W4jjFpu8kVrEdQEtIlE Zwghz8r8xA+3uZIYLsL1GyQfXJ97R72o15aait5R1k2F8z0fTyB8/rV5ff2YACl2EqGV 0vCg==
X-Gm-Message-State: AGRZ1gKO392EaQYHCfriKu+S701i/HsB6TcSWeIfLpzsCFTLRfnRrL7X AnLNuw7FBVprV/FmT1fYxhHzMqEXJfZRmpOYMgXcC2Ub
X-Google-Smtp-Source: AJdET5fJUcu6djxZQCrePGuSc2bYCbVBWoJ6mY8LY9B8j1l9xbpfx4bOlQCXeY7we2P+neYsMIyWpx5e1scE9GJtxEA=
X-Received: by 2002:a1f:ed86:: with SMTP id l128mr10347848vkh.21.1541456408598; Mon, 05 Nov 2018 14:20:08 -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>
In-Reply-To: <CAOW+2duSN5u7u+JrSpvE509k47j7Uuu4=gKy5eMFeAnw5p=kiA@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 05 Nov 2018 23:19:56 +0100
Message-ID: <CALiegf=b=ToNsoOqaEpeqreXrYSru0BT6cB9ZonDHNwS-XfzVA@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Cc: Harald Alvestrand <harald@alvestrand.no>, rtcweb@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/uI-0fbSJ5Rp5TI5Hda6wDTotceQ>
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 22:20:12 -0000

On Mon, 5 Nov 2018 at 23:16, Bernard Aboba <bernard.aboba@gmail.com> 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().

I'm lost. I've enabled simulcast in Firefox using
sender.setParameters() after both pc.addTrack() and
pc.addTransceiver(), and before pc.createOffer().

So I'm not aware of such a limitation in addTrack that "produces just
1 encoding that cannot be increased". Why not? Why should it work with
addTransceiver() and not with addTrack()?

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

v2.23.0 | Report a Bug | By Email