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 23:55 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 AED48128D09 for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 15:55:52 -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 WG2x3ek5hx_J for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 15:55:51 -0800 (PST)
Received: from mail-ua1-x930.google.com (mail-ua1-x930.google.com [IPv6:2607:f8b0:4864:20::930]) (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 DFC84126DBF for <rtcweb@ietf.org>; Mon, 5 Nov 2018 15:55:50 -0800 (PST)
Received: by mail-ua1-x930.google.com with SMTP id u19so2828940uae.4 for <rtcweb@ietf.org>; Mon, 05 Nov 2018 15:55:50 -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=2b56qXiD26imokbJBdBcuakU4DZ0dxrBzinL7MkvXeM=; b=QAyNOW8HbHCXpHjMQuEwfGOX5lDAheU8kwQrpI+jaI0oYyQS+rIXWRv7aSNut2AR1p LibaLA0lvMRHa7cstCSAM8AQMAKxpmb5mfkdwOzeWHqwlP3K24j16HqrHCDqlylhH4Rz DNze9mSE4oXU5aTYd2t20TWWq+IDHu69WXFLLlrdvcIhYA6vbIXwbKfSOF16+qxrcXsX bqRXMgbXSYunTBW1weutgnfduSwknfLIyhw6Z1QkWuV803zUGjSW2YmVJFumEL8s2nbs 637ipnRv7a+ZvTF/LX6HRjsh1FMBRjoHb8Y13keqfXqKp7rHjeMSsm5vGpS1EB2h6JWC yjuw==
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=2b56qXiD26imokbJBdBcuakU4DZ0dxrBzinL7MkvXeM=; b=RjyRi5IcYOwlXTUVmOVdh9efbk/cJOiIaUdL46caDJ9PLhht98azWxRqaFhRZ1cMpe eTTlsnq/sNlTAVhyW2hp9Dq8QCmC2DF3Ru4da3KzsiOdtPKRCbvFu6+Jj+WNJ9fGI0Yh FtAWXPhohJRZXPRwIITtGE92cVw3l8G7/nQsGmbNkSPNCSb3/hzvHrpMQc7FZfXMzRkV 6c4xWAN57zVXA/FG8xFe4C0CvjRDk8gB7JTuEl+bMuw58uwa1HO5cL9ncxw4UyywqhI7 uQHPIsUCWD39nXqt7QG/o8Fc0ysr69mNWNFQTOSF048K9dvyFRZ5jZIkm/VC68H06jRM 4Zyw==
X-Gm-Message-State: AGRZ1gKK8hasJa01KuW9q+N2AXAn6x/NxHr71LjrmeCkY3fVTSkjQOZ7 Z10QePhvWfdsusFN6xxg4Y6RbL3AMbrZTltOFHojEg==
X-Google-Smtp-Source: AJdET5eeRLGk0mhlq5SsukPq6jalYnCxWq+/cnjYue6NPT1JHp7fJQ8d8VBdOQ1qadvm6pm5LGsTYrG8RJc9IPU0c3k=
X-Received: by 2002:ab0:5a4d:: with SMTP id m13mr10565161uad.65.1541462149839; Mon, 05 Nov 2018 15:55:49 -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>
In-Reply-To: <e547e9b3-90c5-fe3b-8f72-6038f2bfd5a6@alvestrand.no>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Tue, 06 Nov 2018 00:55:38 +0100
Message-ID: <CALiegf=+VAft9vP_eGBroRXsV3YL6OKxfe08GpvSX3Bnk=QgYA@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
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/L9jj6mFutML8S-44mHPdGtGksnE>
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 23:55:53 -0000

On Tue, 6 Nov 2018 at 00:50, Harald Alvestrand <harald@alvestrand.no> wrote:

> But this is now deep in API-land, and has wandered far from the original point: That JSEP doesn't allow configuring simulcast from an incoming offer.
>
> I think that if JSEP did not make this statement, it would be OK - since we would then be able to obey the rules in -simulcast (if the browser supported it), and leave the rest of the discussion to the API documents.

Can I say that it does make any sense that JSEP draft exists? Why
should a separate document *also* specify, for example, the
PeerConnection setRemoteDescription() or addTransceiver() methods?


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

v2.23.0 | Report a Bug | By Email