Re: [rtcweb] #29: Section 12.2 Multiple Sources

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 26 August 2013 06:43 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 8FDCB11E8155 for <rtcweb@ietfa.amsl.com>; Sun, 25 Aug 2013 23:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.491
X-Spam-Level:
X-Spam-Status: No, score=-105.491 tagged_above=-999 required=5 tests=[AWL=0.758, 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 yr6C+YNOFbrR for <rtcweb@ietfa.amsl.com>; Sun, 25 Aug 2013 23:43:45 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 8882F11E8130 for <rtcweb@ietf.org>; Sun, 25 Aug 2013 23:43:44 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f738e000003ee3-0a-521af91fee6a
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 98.A7.16099.F19FA125; Mon, 26 Aug 2013 08:43:43 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.18) by smtp.internal.ericsson.com (153.88.183.29) with Microsoft SMTP Server id 14.2.328.9; Mon, 26 Aug 2013 08:43:42 +0200
Message-ID: <521AF966.9030901@ericsson.com>
Date: Mon, 26 Aug 2013 08:44:54 +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.079479d24d9b732c63d05138b2a56121@trac.tools.ietf.org>
In-Reply-To: <066.079479d24d9b732c63d05138b2a56121@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+NgFlrMLMWRmVeSWpSXmKPExsUyM+Jvja78T6kggz19ihb7l1xmtpjf1cpq sfZfO7vF/Z3lDiwej3vOsHksWfKTyePL5c9sHj/3bGYNYInisklJzcksSy3St0vgyrj54i9z wQquihvbn7E3MK7g6GLk5JAQMJFY2vCBEcIWk7hwbz1bFyMXh5DAYUaJad1dTBDOMkaJiZ9u sYJU8QpoSzTv+cIOYrMIqEoceLSFDcRmE7CQuPmjEcwWFQiWaN/+lQ2iXlDi5MwnLCC2iICV xJXLE8HizAJJEtsXnQZawMEhDNR74604SFhIwE3iy7LVzCA2p4C7xLWr86GOk5TYtugYO0Sr pkTr9t9QtrxE89bZzBC92hINTR2sExiFZiHZPAtJyywkLQsYmVcxsucmZuaklxtuYgQG9MEt v3V3MJ46J3KIUZqDRUmcd5PemUAhgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjIxixuu0JRMu Omeevym25rDh6knTf2VkPDghqPeoNmrSBp0AXdvHQYxrRFybX36/wKR5Tnry2+TVx+5M9trz IbPEqjxvsd690A2n50Rskp0gLevnzlrXYHBt3f/YmY5zD2z7KbbhiGF9/J2qSWFHnyu8yRZM 19nF/W5iQUZCy82D3/xvzWfW+6rEUpyRaKjFXFScCACKIAw3NgIAAA==
Cc: draft-ietf-rtcweb-rtp-usage@tools.ietf.org, rtcweb@ietf.org
Subject: Re: [rtcweb] #29: Section 12.2 Multiple Sources
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:43:50 -0000

On 2013-08-26 01:28, rtcweb issue tracker wrote:
> #29: Section 12.2 Multiple Sources
> 
>  tbd: there needs to be a way of indicating how RTP stream relate when
>     there are multiple sources, possibly with simulcast or layered
>     coding, and different types of mixer or other middlebox.  It is
>     possible that the various BUNDLE/Plan-X proposals will solve this,
>     but it might also need RTP-level stream identification.  To be
>     resolved once the outcome of the BUNDLE and plan-X discussions is
>     known.
> 
>  [BA] Suggest that the application token extension be considered as a
>  potential solution to this.
> 

Yes, it is one potential solution. From my perspective the goal must be
to resolve the use cases discussed in
https://datatracker.ietf.org/doc/draft-westerlund-avtext-rtcp-sdes-srcname/

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
----------------------------------------------------------------------