[rtcweb] JSEP question: dealing with entities that do not support a=msid
Philipp Hancke <fippo@goodadvice.pages.de> Mon, 05 November 2018 19:31 UTC
Return-Path: <fippo@goodadvice.pages.de>
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 E60051277D2 for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 11:31:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 LNPs_ha6X04y for <rtcweb@ietfa.amsl.com>; Mon, 5 Nov 2018 11:31:20 -0800 (PST)
Received: from lo.psyced.org (lost.in.psyced.org [188.40.42.221]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CAE4130E10 for <rtcweb@ietf.org>; Mon, 5 Nov 2018 11:31:19 -0800 (PST)
Received: from [192.168.1.230] (cADFE653E.dhcp.as2116.net [62.101.254.173]) (authenticated bits=0) by lo.psyced.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id wA5JVRRE018124 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <rtcweb@ietf.org>; Mon, 5 Nov 2018 20:31:29 +0100
To: rtcweb@ietf.org
From: Philipp Hancke <fippo@goodadvice.pages.de>
Message-ID: <7b6e7b96-c83d-a019-f2c3-f859ce1c14fe@goodadvice.pages.de>
Date: Mon, 05 Nov 2018 20:31:11 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/0V6OOQxKfRh7M0aSCKd9ZaDGyxo>
Subject: [rtcweb] JSEP question: dealing with entities that do not support a=msid
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 19:31:23 -0000
I just filed https://github.com/rtcweb-wg/jsep/issues/856 after noticing an issue with remote offers from something that does not support a=msid. It seems that for the seemingly simple case of a single audio and video track (which might be all a non-webrtc entity ever wants to send) both JSEP and w3c-pc specify a behaviour which differs from current implementations. Is that ok to change/break or are there ways to deal with this in a backward compatible manner?
- [rtcweb] JSEP question: dealing with entities tha… Philipp Hancke