Re: [rtcweb] Rejecting MediaStreamTracks in JSEP

Adam Roach <adam@nostrum.com> Mon, 03 February 2014 20:42 UTC

Return-Path: <adam@nostrum.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 293D21A0213 for <rtcweb@ietfa.amsl.com>; Mon, 3 Feb 2014 12:42:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level:
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=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 sL-N1_p8IhNz for <rtcweb@ietfa.amsl.com>; Mon, 3 Feb 2014 12:42:51 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3769C1A020C for <rtcweb@ietf.org>; Mon, 3 Feb 2014 12:42:51 -0800 (PST)
Received: from orochi-2.roach.at (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s13KghI7041649 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 3 Feb 2014 14:42:44 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <52EFFF3E.9080705@nostrum.com>
Date: Mon, 03 Feb 2014 14:42:38 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Justin Uberti <juberti@google.com>
References: <CAOJ7v-22T7hLMdC2je0nLk34MXQ8L+JFWLtAz--6Ryt+DMaMvQ@mail.gmail.com> <52EFF9E0.40808@nostrum.com> <CAOJ7v-2adSjCiwEp=QRcY+=cYKiiubyjz=rjeMHH4qC56BP1Vg@mail.gmail.com>
In-Reply-To: <CAOJ7v-2adSjCiwEp=QRcY+=cYKiiubyjz=rjeMHH4qC56BP1Vg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
Cc: Cullen Jennings <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@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: Mon, 03 Feb 2014 20:42:52 -0000

On 2/3/14 14:25, Justin Uberti wrote:
> It's not clear to me that adding a new attribute would solve any 
> problem that appid doesn't solve; you still need to deal with the 
> "other end not using it" issue.

Regardless of whether you think there's a problem in the legacy interop 
case, the big benefit here is that an explicit indicator by definition 
makes the operation explicit, and that in-and-of-itself is a good thing.

The core issue is that you're trying to make the operation implicit; 
your proposal edges awfully close to the DWIM model of design, which we 
know causes problems when we try to add further extensions.

/a