Re: [MMUSIC] Scope of RTP payload types in BUNDLE?

Cullen Jennings <fluffy@iii.ca> Wed, 05 June 2013 00:02 UTC

Return-Path: <fluffy@iii.ca>
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 E34CA21F9A21 for <mmusic@ietfa.amsl.com>; Tue, 4 Jun 2013 17:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.655
X-Spam-Level:
X-Spam-Status: No, score=-1.655 tagged_above=-999 required=5 tests=[AWL=0.725, BAYES_00=-2.599, DATE_IN_PAST_24_48=1.219, RCVD_IN_DNSWL_LOW=-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 00ykFGmybFxf for <mmusic@ietfa.amsl.com>; Tue, 4 Jun 2013 17:01:58 -0700 (PDT)
Received: from fallback-in2.mxes.net (fallback-out2.mxes.net [216.86.168.191]) by ietfa.amsl.com (Postfix) with ESMTP id 877CB21F9A2C for <mmusic@ietf.org>; Tue, 4 Jun 2013 17:01:58 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by fallback-in1.mxes.net (Postfix) with ESMTP id D55102FD7BF for <mmusic@ietf.org>; Tue, 4 Jun 2013 20:01:51 -0400 (EDT)
Received: from [10.70.232.182] (unknown [64.104.46.217]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A55F922E255; Tue, 4 Jun 2013 20:01:49 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <EC6422F6-8049-4E28-937F-54282EF5CD06@csperkins.org>
Date: Mon, 03 Jun 2013 16:51:11 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <F207AD72-A395-4697-BD72-27C3EC2954C9@iii.ca>
References: <749DCA95-2D40-46B3-9A3D-E63356C7A2C1@csperkins.org> <1892A917-C408-4E8F-AB19-206ED508762C@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1C3799BC@ESESSMB209.ericsson.se> <4EDA75BD-D753-4153-929B-10427274224D@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1C3799EE@ESESSMB209.ericsson.se>, <599C780A-F483-470E-91F2-68DBA605C79C@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1C379D6E@ESESSMB209.ericsson.se>, <64C06EE8-A16D-4C3E-8A11-D6400F620A8E@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1C379DC8@ESESSMB209.ericsson.se> <71ED9E54-DF0C-4DB9-A7F4-09A0BC90B177@csperkins.org> <51A3B070.1090006@alum.mit.edu> <EC6422F6-8049-4E28-937F-54282EF5CD06@csperkins.org>
To: Colin Perkins <csp@csperkins.org>
X-Mailer: Apple Mail (2.1503)
Cc: mmusic@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Scope of RTP payload types in BUNDLE?
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, 05 Jun 2013 00:02:08 -0000

On May 27, 2013, at 1:24 PM, Colin Perkins <csp@csperkins.org> wrote:

> 
> But, again, let's keep the discussion of mapping RTP/RTCP packets onto RTP sources separate from the discussion of how to map the RTP sources onto m= lines. The former is well-defined by RTP, the latter is not yet defined. Proposals for solving the latter shouldn't start with "when a packet arrives, first do this", because that's the domain of the RTP source de-multiplexing process; rather they should consider "how do we map this RTP-level source (i.e., a sequence of RTP and RTCP packets identified by SSRC, whether signalled or not) onto an m= line". 

I think this thread has convinced me that it was a mistake for my original proposal merged what was happening at what Colin had layer B and C in his digram. I'm roughly talking about how this gets connected up with the right m line at the application layer (layer C). 

I agree with the fact that RTCP and such is reported by SSRC as the layer B.