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:14 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 3B0EB1277CC for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 04:14:38 -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 2LUHMW4x3Cm1 for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 04:14:36 -0800 (PST)
Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (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 205A1127133 for <rtcweb@ietf.org>; Mon, 5 Nov 2018 04:14:36 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id v205so4948935vsc.3 for <rtcweb@ietf.org>; Mon, 05 Nov 2018 04:14:36 -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=LYbD2wNPl+Q+kYR/HfalsOVG8oA1SakFwDryg4VmTRg=; b=r13IgTGNAGATRzNAiNypOeBNKxjIj4PdL1WxWladTQFjwF1oi1f4+bnPjlgtsrDPgv xe5xuwUZ+ce4YApIJpR4KbufUZc7Xs8D+flk4m9DLhQsnZUibYZj90COmUm1kP9EnvfE TUjGTTs+PNUeOQW5K9CRbgo6IdkpaMyxbBX+hzC5lYegaA6S6KO00w94e624HzlD6sAJ Qceaqh+M4ORd8hg5p9L17nk1VlxIw0DJMIeDb5Gmnd/blMPCxXXjwi+/zdppuxnEVLbt 9SRWo3DLGMS4JZTTKZ6DkYobVMlANX70XoBc2/Nry5CZJSWGNx1n+oXG0bVSTmiPD01i ZOxg==
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=LYbD2wNPl+Q+kYR/HfalsOVG8oA1SakFwDryg4VmTRg=; b=JMzFx9G9P44Xynwhvq83M9wk1pJc8XrZjjcrrU74JacmG0EWYfA+ToQlnybL9MomxO lqcVwuvNi83F8jXehbnIb8rTmZ6tVI2vNPSjp3YS6LRSBzenBziptoAKXxl/q0cYZyxj cIkAEjSKTGvsOLixuIAQFJbeT6Tl4SG0aA+qWXg5DPqPz7mPykbaHife3nZrxqa1IbsU gwICCa0G7QDNm36/CQUcpziRID/ON/XLsk5V7uXO+cUB9UDf0tDuUaJsvSj2cvjUypsq 4v4Adu7hOx0eSP9CdFQ6AmFO2JmAQK+pB243uWBm/ycS2SI7gxVPnr9OX6T3D3CI+HaD 0O/Q==
X-Gm-Message-State: AGRZ1gLaNCOE6JcYPzkSgxoxXs7bRuj/NaHT02IfosqX8ZuXm/kDoVo/ jHUYXVJVAHYT5CG1h1WG92gbFYAWkSCe78ASc4lJFQ==
X-Google-Smtp-Source: AJdET5cQ0BHGt1iIhv+WUmyduoTjtX+irU1F1NPpdmq033fBpA8E5YTJ87x/CI5wgBZj/I3lKLbZDnxxB1X5KunKtn8=
X-Received: by 2002:a67:584:: with SMTP id 126mr9025025vsf.67.1541420074811; Mon, 05 Nov 2018 04:14:34 -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>
In-Reply-To: <5FB0A50F-DAF3-47C4-A5F5-8DA20586C9E2@iii.ca>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 05 Nov 2018 13:14:23 +0100
Message-ID: <CALiegf=tFL1zagfp7qyPBWn6r+NQ8SKW=OBKc=6ZOVwgHzcHWg@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
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/JPgcm5Kx_n-8iDlYiBWpi4dkfoY>
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:14:38 -0000

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".

On Mon, 5 Nov 2018 at 06:16, Cullen Jennings <fluffy@iii.ca> wrote:
>
>
> On Nov 5, 2018, at 5:52 AM, Iñaki Baz Castillo <ibc@aliax.net> wrote:
>
> Hi Bernard, before entering into implementation details, do you really
> agree that the remote should be able to force the local peer what and
> how to send media?
>
>
> I agree with Bernard.
>
> It's not about force something to do something - the app can always do whatever it wants with offers and answers -  it's about the local side being able to interop with a changing remote side without having to worry about anything local. Every time the browsers add new features, it's pretty awesome if my application gets them without even worrying about them if there is no need to worry about them.
>
>
>


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

v2.23.0 | Report a Bug | By Email