Re: [AVTCORE] SSRC multiplexing of RTP

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 14 March 2011 16:16 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2362A3A6DB8 for <avt@core3.amsl.com>; Mon, 14 Mar 2011 09:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.49
X-Spam-Level:
X-Spam-Status: No, score=-106.49 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l9Oe4psTN+yQ for <avt@core3.amsl.com>; Mon, 14 Mar 2011 09:16:10 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 0E9703A6972 for <avt@ietf.org>; Mon, 14 Mar 2011 09:16:09 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bbbae000005311-ef-4d7e3f9cc0c2
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 19.DE.21265.C9F3E7D4; Mon, 14 Mar 2011 17:17:33 +0100 (CET)
Received: from [147.214.183.8] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.2.234.1; Mon, 14 Mar 2011 17:17:32 +0100
Message-ID: <4D7E3F9C.4010505@ericsson.com>
Date: Mon, 14 Mar 2011 17:17:32 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com> <4D7798A9.7080006@omnitor.se> <4D779F79.8090001@ericsson.com> <4D79FEC3.9060204@alvestrand.no>
In-Reply-To: <4D79FEC3.9060204@alvestrand.no>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 16:16:11 -0000

Harald Alvestrand skrev 2011-03-11 11:51:
> On 03/09/11 16:40, Magnus Westerlund wrote:
>> Hi Gunnar,
>>
>> Gunnar Hellström skrev 2011-03-09 16:11:
>>> Cullen
>>>
>>> I agree. I have also got negative feedback on SSRC multiplexing.
>>>
>>> I had it described in the draft for multi-party handling of real-time
>>> text in draft-hellstrom-text-conference-02.txt
>>> in order to easily separate the streams from different sources and
>>> display them in a way that the receiver decides.
>>>
>>> But the feedback was that many RTP implementations would just regard it
>>> to be an error if a new SSRC appeared in the session and it would cause
>>> problems.
>> Well, this is how you are supposed to use cases when you have multiple
>> sources. And text chat is case when implementations can't really say
>> that they don't have the rendering capabilities for it. But I do
>> understand that most implementations sucks at handling multiple SSRCs
>> which is very bad.
>>
>> My hope is that we will see a bit of signalling support for handling
>> multiple SSRCs as part of the CLUE work. But, we do need to push that
>> support for multiple SSRCs, it needs to be in the stacks.

> Seems to me that since this isn't clear from current specs, there needs 
> to be a specification of what a new SSRC appearing in a session means, 
> possibly agreed to at call setup time, and if both renumbering and 
> multiple streams are to be supported:
> 
> - if it is a new stream, how to tell that it's a new stream
> - if it is an old stream, renumbered, how to tell what the old stream was

I don't think the specs are that unclear on what is what. You do need
the CNAME to determine which case it is. Sure it can be clarified. I
mostly think the issue is with the state of the implementations. They
haven't considered the implications and need for multiple SSRC support.

> 
> This will certainly be an RTCWEB discussion item, so I'm happy to see 
> AVTCORE pick it up to be worked on.

Lets figure out what is considered the issues here.

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