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

Bernard Aboba <bernard.aboba@gmail.com> Wed, 07 November 2018 03:09 UTC

Return-Path: <bernard.aboba@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 240FC128CE4 for <rtcweb@ietfa.amsl.com>; Tue, 6 Nov 2018 19:09:21 -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 nJ7PBl_qP8oj for <rtcweb@ietfa.amsl.com>; Tue, 6 Nov 2018 19:09:19 -0800 (PST)
Received: from mail-vk1-xa31.google.com (mail-vk1-xa31.google.com [IPv6:2607:f8b0:4864:20::a31]) (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 5392B130DC7 for <rtcweb@ietf.org>; Tue, 6 Nov 2018 19:09:19 -0800 (PST)
Received: by mail-vk1-xa31.google.com with SMTP id o10-v6so3394277vki.6 for <rtcweb@ietf.org>; Tue, 06 Nov 2018 19:09:19 -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=DA4c/thwcUvTh5XtTYzUFBFi0tNuw9Ck7KUHuaoqps8=; b=MBYUIhwHzTMDdrcWmKyohyEDiLy8hgoFUPCp8qxitELWaVRYVYgvSSkhaBDHxM+bCV nysAYJ2QmIY3cjLTwOxBhs+8AhdCnQjiyg/8JgVIjTw5vOT9q8U12YK8/Ur7ZckTkpVn qWLfyH8DGzkq62TYoh6SqxySEUIqzcdnda8lZYmjYuDZLH0Cb4RPxeKz4sVbnxp6sKIS wyziKj3ZHw9yYh/qDUy7HnDfnyw/cdqIdN+kVPCSUOO07CY5bG519vXa2IdJOay8bthN jDWOtkx5lpj/Eo7qUGrTz0LFRtdP48NlnQR7mcgzFgTvRQ/XlzcZo4pIUz4t1I0+cLVG 6Pcg==
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=DA4c/thwcUvTh5XtTYzUFBFi0tNuw9Ck7KUHuaoqps8=; b=frhBvSSjS+Ilq7/EWQn1UoMsIP7I3aykQ8axkqPIexUOFa8GHNmy2WJ6IE1l3oOWG9 j1nlSAzFMIdNwiO6VUbsWo7yXG51MWn7yWGtClI9Np9c1h9/Y4QEVmZDJybNq3QH27EL aMDY2+09eNG89d2CzXzOGgE6VZd5wo20c98hksiY3PUzAwYzgZeO1ZmQpakVgf1JOBy6 HYhyGca8K7Mk0oL1HiO1sMd00Tut5nR29SmDRk5toZ8r3BH1O3zctOA4mCDnEvTQZ3LS mMIhjz7gvDusZB9LLVqiaRtjYwAakb2jg2Eg1NwqgKHwNqleZsnNLkB1hD0TkjbUFbvu 34lw==
X-Gm-Message-State: AGRZ1gK6i883hqc7+pWWsMniFT5dcqv3obJj37v2yKzbNgY/1MKeaKoS 1nqFPFY7eJuiaBttoDyBjl71tMw1cAHAehMmAmew+g==
X-Google-Smtp-Source: AJdET5c8CIwxRwgpm1HcuEv59rZ47Ekl8MGowUM1c2njOEfX14OGcwqiwOP3XjujJy+KGf5krXaCep7WS2J4V8xrnTg=
X-Received: by 2002:a1f:2ed7:: with SMTP id u206mr59783vku.72.1541560158166; Tue, 06 Nov 2018 19:09:18 -0800 (PST)
MIME-Version: 1.0
References: <185c8d1d-3971-ad09-eee0-a26bed446a96@alvestrand.no> <A5687AE0-7D07-46C8-AF93-7B0D0DE0BC4B@mozilla.com> <CAOW+2dveTZ8jtAyNNftv=fMi_C8LifvE8RtUuszg0-eUYcgANg@mail.gmail.com> <CALiegfnChcJ9W52e0C-CyyCw+9jUnJg0Wszv7DTd_CtpvEC2Xg@mail.gmail.com> <5FB0A50F-DAF3-47C4-A5F5-8DA20586C9E2@iii.ca> <CALiegf=tFL1zagfp7qyPBWn6r+NQ8SKW=OBKc=6ZOVwgHzcHWg@mail.gmail.com> <C6D65A1E-F701-4E47-9B82-B4EA444BA7A0@iii.ca>
In-Reply-To: <C6D65A1E-F701-4E47-9B82-B4EA444BA7A0@iii.ca>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 06 Nov 2018 22:09:06 -0500
Message-ID: <CAOW+2duUbcQ3OCa-vdw57Y7676KOOyCN8wY17Vjw1up_7HDpCQ@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Cc: RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a0a2f2057a0a717e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/9NbFT2R6E3Gx5sxcbA98BWKEGqw>
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: Wed, 07 Nov 2018 03:09:21 -0000

Cullen said:

"Let me put this as politely and straight forward as I can.  You are wrong."

[BA] I would agree that API interoperability is needed for simulcast, even
if it doesn't yet exist because we're still ironing out the Issues.  The
interest in implementation appears to be quite high, so once we figure
these things out (assuming we make the specification clear enough to avoid
further confusion), we stand a chance of interoperablity in both APIs and
protocols, which is after all, the point of developing a standard.

In that respect, I would prefer if JSEP would include some guidance we
could cite in WebRTC-PC, rather than having to provide clarifications
within the API document itself.

On Tue, Nov 6, 2018 at 9:15 PM Cullen Jennings <fluffy@iii.ca> wrote:

>
> On Nov 5, 2018, at 7:14 PM, Iñaki Baz Castillo <ibc@aliax.net> wrote:
>
> If you excluded the word "interop" from any rationale, life would be
> much better, specially here where such an interop:
>
> 1) does not exist
> 2) is not needed
>
> To be clear: No app in the world is or will be NEVER ready to enable
> simulcast auto-magically just because it eventually receives a
> different SDP offer from the remote. The app developers would already
> figured out different ways to enable simulcast that would just not
> allow such an auto-magic "upgrade".
>
>
>
> Let me put this as politely and straight forward as I can. You are wrong.
>
>
>
>