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 12:06 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 57F48128CFD for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 04:06:19 -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 ilW8LJqpV0U7 for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 04:06:16 -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 C14171277CC for <rtcweb@ietf.org>; Mon, 5 Nov 2018 04:06:16 -0800 (PST)
Received: by mail-vs1-xe34.google.com with SMTP id y27so3099847vsi.1 for <rtcweb@ietf.org>; Mon, 05 Nov 2018 04:06:16 -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=Tluvj3eR/4eFIal7my+hdNLELT/Glw7xEhyBFqAvy7M=; b=gTLd9X1wbWiyk9TwjYDh9524+zFwLSaBCr7eQre3IVjwxBNGmkB1QUetTriF9zh1gJ jB1uvhLaKmdBjQwyFpuwkA2RvI+e3tpKYk0jM4iETI2dJ/E+MZrKak7kMeHqLkdKBNuE 6VlodAcCS9rr8pyoJnvoyAIr2W9/hU6o8ZKvPdV6AMqfrM/dSrQXmh1dvp+K9Bv7g1Ao SaLk84PsPRehzJDwCBn9jDCGUvN4L3UMufgJHFeB8GwGkEz30eAgjewATL9u0j2bG7dh 4jRiWUwRh5UIqiMf8D1b3kDYKgW4cSlAzybTG8vxpzylwn3EYJmzMMYY+Zl3cD+r6bcB 5GEA==
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=Tluvj3eR/4eFIal7my+hdNLELT/Glw7xEhyBFqAvy7M=; b=Enpg8Ymn041+f+S89Qhom65njXcfBGHV4F4hf/5bOj8QJSGBBntMXgdtrMVgLUxkqj iaCx/g0meXtEGMxdtjUuOwZ04VTAWy8H5IDtHkXLDBCWp1GT5EuG8JN1Y6FIVD49NwEN wf6k0EfZeGfcj3RNff9PAh7ZBA306UflrtmiOkTg8MZTxyDohBwLNix764X0985TLQrm oo7TVpNA8LIptu1m9dSTQRmygKNpcH7E1/onvZ8mxrlU615Yd4iUHxFRR6ByrqKyxOuG DPpxeF6aN5rKkevmhnfGWADi5Q5tQWKxUyytagUcCo/nVOdhc6eVIIBCIsCdKijX25aO e4bA==
X-Gm-Message-State: AGRZ1gI+tO7S756G0133U0gR3XC+I/TVwJr9gCh+q4uu5hER6cELpy1k f0zmFx8GYg8GdQm+J5E6pxyao6/MAJZuCBP4XNVJ6oGC
X-Google-Smtp-Source: AJdET5eVJ605KMr78UiJiOGrsylYv2RckVEJjFH7xpzpcG5w+mw6VOyADxxwrm8zlszNRKgOjEjwQ42KNS5k5sWeU1o=
X-Received: by 2002:a67:3659:: with SMTP id d86mr9144872vsa.17.1541419575378; Mon, 05 Nov 2018 04:06:15 -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> <d7fef958-1823-44c1-72a7-3840161a2626@alvestrand.no>
In-Reply-To: <d7fef958-1823-44c1-72a7-3840161a2626@alvestrand.no>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 05 Nov 2018 13:06:04 +0100
Message-ID: <CALiegfkqnm90YdhSNyjtqa9pGPe8+qSAiDVguqowdF00BR_wQw@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: sergio.garcia.murillo@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/noBCjl7ky_Dws4fvejRNMHg2uwk>
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 12:06:19 -0000

On Mon, 5 Nov 2018 at 03:57, Harald Alvestrand <harald@alvestrand.no> wrote:

> If the remote SDP indicates that the remote end is willing to receive 3
> simulcast layers, and the browser is able to send 3 simulcast layers,
> how many simulcast encodings should be represented in the
> sender.getParameters() returned after the negotiation completes - and
> what are the implications of that?

This is a very good point. Yes, even if we inspect
receiver.getParameters() after pc.setRemoteDescription(offer), we'd
just get the number of encodings wished by the remote, and having to
correlate such a number with the local limit (do we have an API to
know the local limit before calling sender.setParameters()?) would be
an implementation and usage nightmare.



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

v2.23.0 | Report a Bug | By Email