Re: [rtcweb] #28: Section 11: Track

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 26 August 2013 06:36 UTC

Return-Path: <magnus.westerlund@ericsson.com>
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 2BE9711E8165 for <rtcweb@ietfa.amsl.com>; Sun, 25 Aug 2013 23:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.428
X-Spam-Level:
X-Spam-Status: No, score=-105.428 tagged_above=-999 required=5 tests=[AWL=0.821, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80GV53UgPt6k for <rtcweb@ietfa.amsl.com>; Sun, 25 Aug 2013 23:36:34 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0D16A11E8164 for <rtcweb@ietf.org>; Sun, 25 Aug 2013 23:36:33 -0700 (PDT)
X-AuditID: c1b4fb25-b7eff8e000000eda-86-521af7709143
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 94.D8.03802.077FA125; Mon, 26 Aug 2013 08:36:32 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.148) by smtp.internal.ericsson.com (153.88.183.62) with Microsoft SMTP Server id 14.2.328.9; Mon, 26 Aug 2013 08:36:31 +0200
Message-ID: <521AF7B6.3010301@ericsson.com>
Date: Mon, 26 Aug 2013 08:37:42 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: rtcweb issue tracker <trac+rtcweb@trac.tools.ietf.org>
References: <066.4c4e5ce1c5da5cdef9f462930dc11306@trac.tools.ietf.org>
In-Reply-To: <066.4c4e5ce1c5da5cdef9f462930dc11306@trac.tools.ietf.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUyM+JvjW7Bd6kgg+69Shb7l1xmtpjf1cpq sfZfO7vF/Z3lDiwej3vOsHksWfKTyePL5c9sHj/3bGYNYInisklJzcksSy3St0vgypi2dR5b wRqeiq75F9kbGJ9wdjFyckgImEjM+LWRFcIWk7hwbz1bFyMXh5DAYUaJ0w2zGCGc5YwSN4+f Zwap4hXQlui7dpEFxGYRUJX4eLeNDcRmE7CQuPmjEcwWFQiWaN/+lQ2iXlDi5MwnYPUiAlYS Vy5PBIszCyRJbF90mgnEFhbQkTgxsQGsRkjATWJB9xWwXZwC7hKHvsyGuk5SYtuiY+wQvZoS rdt/Q9nyEs1bZzND9GpLNDR1sE5gFJqFZPUsJC2zkLQsYGRexciem5iZk15utIkRGNIHt/xW 3cF455zIIUZpDhYlcd7NemcChQTSE0tSs1NTC1KL4otKc1KLDzEycXBKNTDa3tNU23Bul61Q zJfF93LSligI+0xJ//cvvujbP7ZHWwLXKL9fkTB7v2xUZv3OC6LHVS/7/Zaft97pd+Sut/8l FE3b+Db+iuy0OzKjcvFj1f5VeUe1dtQ9cD77NHyh/vslCucK7E/NnTXL9PWkyy43qpRmfnj5 jXttlqpZs0GdqVbhlLy79+t/KrEUZyQaajEXFScCANGsebg3AgAA
Cc: draft-ietf-rtcweb-rtp-usage@tools.ietf.org, rtcweb@ietf.org
Subject: Re: [rtcweb] #28: Section 11: Track
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Aug 2013 06:36:47 -0000

On 2013-08-26 01:22, rtcweb issue tracker wrote:
> #28: Section 11: Track
> 
>  A track is an
>     individual stream of media from any type of media source like a
>     microphone or a camera, but also conceptual sources, like a audio
>     mix or a video composition, are possible.
> 
>  [BA] This doesn't seem quite right, if by "individual stream of media"
>  you mean RTP Media Stream as defined in Section 3, since a track can be
>  comprised of one or more channels.
> 

A media source according to the above can be multi-channel audio mix or
capture. The point is that a track is an independent media with an
time-line.

However, this comment do point towards two open issues around this.

First, the use of terminology that should be aligned and help contribute
to the taxonomy draft discussion.

Secondly, that we need to take a serious look at the mapping between the
API and the RTP level. As noted by the TBD in section 11:

   (tbd: This text needs to be improved and achieved consensus on.
   Interim meeting in June 2012 shows large differences in opinions.)

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------