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:12 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 B456E1277CC for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 04:12:14 -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 7WWT0u5H4Npw for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 04:12:08 -0800 (PST)
Received: from mail-vk1-xa41.google.com (mail-vk1-xa41.google.com [IPv6:2607:f8b0:4864:20::a41]) (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 C7296127133 for <rtcweb@ietf.org>; Mon, 5 Nov 2018 04:12:07 -0800 (PST)
Received: by mail-vk1-xa41.google.com with SMTP id y14so1949832vkd.1 for <rtcweb@ietf.org>; Mon, 05 Nov 2018 04:12:07 -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=ZYuUKrmrWMQ325PrXKeUWCGIv/ytiAdVGFfE3qa6BFQ=; b=Fdli9lvP0rIqaxX1OFUOBep9ToBNmVUr/hid/I6sYNQEPCKqGn7xI2gEvuSoFmAPSd lc3bpOoaAMEgY1JDjeeLhI1YOB13h0hi7UZOf8rj2SuE7fPWaBC56xKAho7/5svKABEt qxNMH1A1SN1o5Or5YOFe1Uh1/Qiwr4VQQ9wa1Zt2d/DF3AkCNGkS1EU8ugnc5jF4P5Yk BT5+dseA5U4aiHZ0Ugwg4AMzOcM9TYOCGj+PGZXA85Vl5DYC7Hdc/X2vrUY6tfwOzY14 9jDQo5F/xbBgmBjpz6Ye92DmQmwsMrYe9001eDwGjHppGMrneG30VLpHheH9sybpn2Ys RYwQ==
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=ZYuUKrmrWMQ325PrXKeUWCGIv/ytiAdVGFfE3qa6BFQ=; b=iHK4FSRJiIl8YHj41OA72QexcRPc4nSDYqyoagzOcwHFzXc+xFESnB8IY3Ko63wHOi 1Y+bWoY4ru9Fw86iX0NaZHKrGkOqdnb87BWIMVJ9o/3Kas2CnQXizXsBOjNz29vxuNgw lAlG0ihF1KcF9TgfRJcFELbJ2OYzvcVvgpT2Or9ii7xNXiD7xSTgKz6Hqk4Ty34sXMCw EMz0cqrppceqUL4gVbtonIjROD/BeKNKbPECD8bLZt0dEhUDeXLOGLuEDsDDrN1S8uFo yRCyXb3/nGvBpf2QNoLNDJmBPvEs6CD76C1StvoBJCxA+wp/UUcn3YylD75LTnHBEoqv CEIw==
X-Gm-Message-State: AGRZ1gLUsjI6IHMNT/bf3VzFkoagA8vfDTJB3C4nMOKWkrl+D3sCp5Nn S/AY0dUVO+tsj432NhnOD4Vj2NF9HeYQdSpRcGYWODah
X-Google-Smtp-Source: AJdET5cxBvDYY1CDeCbgfR+lRoSevgGqT4NytbLVyj99aqT3jOX/x3oKGo+0sRmpRf1kH9AziPtojoIb10KGRvOSHms=
X-Received: by 2002:a1f:ed86:: with SMTP id l128mr9367912vkh.21.1541419926505; Mon, 05 Nov 2018 04:12:06 -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>
In-Reply-To: <5db76ada-b896-7eba-b42e-85b2e239dc42@alvestrand.no>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 05 Nov 2018 13:11:55 +0100
Message-ID: <CALiegfmdxHVqndRYRP-gmTGKFweTdpPPGVOFBCPM7CpvLvVeYw@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/OqJ5iSPzAEJv5rMIRL7EAn3eeVI>
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:12:15 -0000

On Mon, 5 Nov 2018 at 12:45, Harald Alvestrand <harald@alvestrand.no> wrote:
>
> On 11/05/2018 10:03 AM, Sergio Garcia Murillo wrote:
> > I am not talking about replacing a transceiver but adding a new one
> > and renegotiate. The initial O/A will drop the simulcast attribute on
> > the answer and create a recvonly transceiver, and then create a new
> > transceiver with simulcast encoding that will require a O/A.

> OK, so we have the same picture in mind of what will happen in your
> proposal. We end up with an useless transceiver and a new transceiver
> that is suggested by the browser end, in a new media section; it's
> impossible to use the media section that the (initiating) server proposed.
>
> That seems ugly.

So:

- receive a remote offer with a single m=video section requesting
local simulcast
- reply with a=recvonly (fxxx you, conference server)
- reoffer with a new m=video with "correlated" simulcast settings
- have the conference server like that

And... all this party instead of just telling the client (via custom
messaging before it "joins" the conference) the desired simulcast
settings? :)


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