Re: [rtcweb] Rejecting MediaStreamTracks in JSEP

Magnus Westerlund <magnus.westerlund@ericsson.com> Thu, 13 February 2014 09:05 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE6511A01B6; Thu, 13 Feb 2014 01:05:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level:
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 h8kVPa9nfwdO; Thu, 13 Feb 2014 01:05:51 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 21F071A018B; Thu, 13 Feb 2014 01:05:50 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-43-52fc8aedd2a7
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id F5.B2.10875.DEA8CF25; Thu, 13 Feb 2014 10:05:49 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.47) with Microsoft SMTP Server id 14.2.347.0; Thu, 13 Feb 2014 10:05:47 +0100
Message-ID: <52FC8AEB.6020906@ericsson.com>
Date: Thu, 13 Feb 2014 10:05:47 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Justin Uberti <juberti@google.com>, Jonathan Lennox <jonathan@vidyo.com>
References: <CAOJ7v-22T7hLMdC2je0nLk34MXQ8L+JFWLtAz--6Ryt+DMaMvQ@mail.gmail.com> <C433A27C-348A-402A-B036-07060746FADA@vidyo.com> <CAOJ7v-0S4C+P6hv2rrTCpFvvq1eVBfbuxb+QGQyAP5mG0yb2uQ@mail.gmail.com> <9E51C939-CCFE-4EA6-83BF-9B871D64CDA0@vidyo.com> <CAOJ7v-3wieadkcvhvS1EbkO42MGEzE+8z6Ex1ivWuO1z=xCgcg@mail.gmail.com>
In-Reply-To: <CAOJ7v-3wieadkcvhvS1EbkO42MGEzE+8z6Ex1ivWuO1z=xCgcg@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDLMWRmVeSWpSXmKPExsUyM+Jvje7brj9BBkt3KVl0TGazOHHjNLPF /sXnmS22ThWymLr8MYvF2n/t7A5sHlN+b2T1WLCp1GPJkp9MHm3P7rAHsERx2aSk5mSWpRbp 2yVwZfza08RUsI+rYu2l62wNjNs5uhg5OSQETCTOXP/BBGGLSVy4t56ti5GLQ0jgEKPEvfYm RghnOaNE4+sOsCpeAW2J771P2UFsFgFVifeL5rGC2GwCFhI3fzSygdiiAsESOw/8ZoSoF5Q4 OfMJSxcjB4eIgI/Em02CIDOZBboZJS4e6gGrERawlFgzu40dYtkeJom587eAJTgFAiWmr+pk AmmWEBCX6GkMAgkzC+hJTLnawghhy0s0b53NDGILAd3W0NTBOoFRaBaS1bOQtMxC0rKAkXkV I3tuYmZOernhJkZgiB/c8lt3B+OpcyKHGKU5WJTEeT+8dQ4SEkhPLEnNTk0tSC2KLyrNSS0+ xMjEwSnVwKgWut7jq/6/Ds9u8WglvueC9xKPiIvlralaVS3ALV+qbCfQdEV126HjYh+Mb/a+ OrtqnsXp/MvNy31P2m4ti+jlu/oj+1dV172MrQpLbLPfTngVHtN1RSbSU1Y8x511Ov/Knp33 Izd4FC7X2Hgr21PoH+vWL1zP5OW47rZtP9UYrPyvWWjffyWW4oxEQy3mouJEALB1gMY/AgAA
Cc: Cullen Jennings <fluffy@cisco.com>, Harald Alvestrand <hta@google.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [rtcweb] Rejecting MediaStreamTracks in JSEP
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 13 Feb 2014 09:05:55 -0000

On 2014-02-04 01:05, Justin Uberti wrote:

> 
> Agree that msid should map m-line to MST, but it would seem recv-msid
> could map RTP flow to m=line as well as indicate whether the receiver is
> in fact interested in receiving the MST associated with said m= line.
> Note that recv-msid doesn't specify an actual MSID; its purpose is to
> indicate that the receiver wants to receive data from the remote side's
> MST, and provide a mechanism for the sender to mark the data
> accordingly. (Which ends up seeming a lot like appid.)
> 

A question here, what are you really trying to reject?

Is it the MST, a particular RTP Stream (Id by SSRC) or the usage of this
media description (m= block)  in a particular direction (i.e. SDP internal)?

I think the solution differs quite a lot depending on what you really
try to accomplish.

cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------