Re: [MMUSIC] BUNDLE TEXT: De-mux procedures (June 19th)

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 19 June 2013 19:24 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EB2B21F9B8F for <mmusic@ietfa.amsl.com>; Wed, 19 Jun 2013 12:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level:
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
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 foEouCRXwexO for <mmusic@ietfa.amsl.com>; Wed, 19 Jun 2013 12:24:11 -0700 (PDT)
Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:228]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB3A21F9BA5 for <mmusic@ietf.org>; Wed, 19 Jun 2013 12:24:11 -0700 (PDT)
Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta15.emeryville.ca.mail.comcast.net with comcast id qG7Z1l0041vN32cAFKQBwR; Wed, 19 Jun 2013 19:24:11 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([63.226.120.12]) by omta22.emeryville.ca.mail.comcast.net with comcast id qKN21l00m0G8kgX8iKN4SY; Wed, 19 Jun 2013 19:22:08 +0000
Message-ID: <51C204DA.9030203@alum.mit.edu>
Date: Wed, 19 Jun 2013 15:22:02 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C3AFDB7@ESESSMB209.ericsson.se>, <51C1A4A3.6070105@alvestrand.no>, <7594FB04B1934943A5C02806D1A2204B1C3AFEA1@ESESSMB209.ericsson.se>, <51C1A89A.9020603@alvestrand.no>, <BLU169-W56DEA51EC84C8180A7DCD5938D0@phx.gbl>, <7594FB04B1934943A5C02806D1A2204B1C3B0B60@ESESSMB209.ericsson.se>, <BLU169-W1288AEADA7A090C209F376C938D0@phx.gbl> <7594FB04B1934943A5C02806D1A2204B1C3B0EF1@ESESSMB209.ericsson.se> <51C1DD3A.8030705@alvestrand.no>
In-Reply-To: <51C1DD3A.8030705@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1371669851; bh=AB/iihruDweEyx9dG1ygJ2RMqsqeEzP1qMxRbXj14Bg=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=AGQY1ThuDjoLIfEtmCvQ5hjuC9UfvHzL/EoNZjN9X9yNwaBwVZl5W0MH/2n2G2UkA nwu11VkVZz80ECEdTDlNvqaTx7x9ezsJTSL2Tqa4noloYbgtwHIyp5gGmPnONBMI/B jvvawh+51gfgtQscRb80T1tMUmh1Aguv/2FPokxUTPItDSCL5TVFiA3a20ZSslsRA/ vWrwP1j0sZILtmviEJFQ2IUl9srApTPPVAB5InCT7RpLT6HAq7nkiOFgxoxFoflrFP 1A1Df1y18FztWUcJbsiajhrKcheAQuIKjQlGboLwpwUFgbqhhTX39HV4EVJZv+kBCV cWn30Vz1ov8VQ==
Subject: Re: [MMUSIC] BUNDLE TEXT: De-mux procedures (June 19th)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 19:24:17 -0000

On 6/19/13 12:32 PM, Harald Alvestrand wrote:
> On 06/19/2013 05:56 PM, Christer Holmberg wrote:
>> Hi,
>> The question is whether we shall specify exactly how entities
>> associate RTP packets with the correct m= lines, or whether we shall
>> simply give some guidelines and hints.
>> For example, a client can choose to use unique PT values per m-
>> values, within a given BUNDLE group, and everything should work fine.
>> And, if the endpoint runs out of PT values, the create a new BUNDLE
>> group. Now, whether it's religiously correct, I don't know :)
>> OR, if the endpoints are able to signal which SSRCs they are going to
>> use, they can use that.
>> OR, if the endpoints support some kind of RTP header extension for
>> this purpose, they can use that.
>
> OR, if they don't care which M-line the stream is associated with, the
> question may be moot.

I think this is a silly argument. If they don't care which m-line the 
stream is associated with then there was no need to insert the m-line.

If there is a reason to have the m-lines, then there needs to be a way 
to associate packets with m-lines.

	Thanks,
	Paul