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

Emil Ivov <emcho@jitsi.org> Mon, 27 May 2013 13:39 UTC

Return-Path: <emcho@sip-communicator.org>
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 2919421F900C for <mmusic@ietfa.amsl.com>; Mon, 27 May 2013 06:39:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 9TabaAoDG2rT for <mmusic@ietfa.amsl.com>; Mon, 27 May 2013 06:39:14 -0700 (PDT)
Received: from mail-pa0-f42.google.com (mail-pa0-f42.google.com [209.85.220.42]) by ietfa.amsl.com (Postfix) with ESMTP id 3A8AE21F9350 for <mmusic@ietf.org>; Mon, 27 May 2013 06:39:14 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id bj1so1618613pad.1 for <mmusic@ietf.org>; Mon, 27 May 2013 06:39:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=b0+PpCXM6w/Kt8qlNifvbDQ8Q2JBP25hixO+OFxPv8U=; b=PKv3r2obHAY0eg2sklmY1X7qFO7iSBXfxhEmnvM0OD1uNfO4P8xU11Vxg0ki/5Wpbf DE5lD0OSXP6bvsuWSCICxah97aEdsG7suLvJSQsXXmRJsxmShk6kHPbOgtQjOOTEoCvd R52r7izrLWk/SCWqnWT+NugguK5Em2pgoNCHLOjbyWhDyONgjsu7nvOnLd3ZUWlu+gUc eL/VwnsijtbTZQQf36ANSOiK1N/Cf4NX8qwryOQqoYbZhp7ugKO5DSMgULmVe/tzRjzX 5Kt8DJelIvtZrf2+eq74aXfmU+4WB3vY3mxQEKACpSaG1tAgmj/b0YTELGyNaczeTSPj Fpag==
X-Received: by 10.68.194.202 with SMTP id hy10mr29220026pbc.44.1369661953871; Mon, 27 May 2013 06:39:13 -0700 (PDT)
Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com [209.85.220.50]) by mx.google.com with ESMTPSA id vz8sm30666551pac.20.2013.05.27.06.39.12 for <mmusic@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 May 2013 06:39:13 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id fb11so5517723pad.37 for <mmusic@ietf.org>; Mon, 27 May 2013 06:39:12 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.66.88.38 with SMTP id bd6mr30720026pab.184.1369661952716; Mon, 27 May 2013 06:39:12 -0700 (PDT)
Received: by 10.66.89.234 with HTTP; Mon, 27 May 2013 06:39:12 -0700 (PDT)
Received: by 10.66.89.234 with HTTP; Mon, 27 May 2013 06:39:12 -0700 (PDT)
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1135184BE@xmb-aln-x02.cisco.com>
References: <749DCA95-2D40-46B3-9A3D-E63356C7A2C1@csperkins.org> <C5E08FE080ACFD4DAE31E4BDBF944EB1135184BE@xmb-aln-x02.cisco.com>
Date: Mon, 27 May 2013 16:39:12 +0300
Message-ID: <CAPvvaaJmRgL1YeB3H2NWSi7fyQOYDCJ1hnU=XLiEqVN7WpN4kw@mail.gmail.com>
From: Emil Ivov <emcho@jitsi.org>
To: Cullen Jennings <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary=f46d042dfeaf27a59204ddb346c4
X-Gm-Message-State: ALoCoQms/aRD8HqeXxSzRfb2xNTFV365PZa7hpCsnWFyVEuJYzH92KQrYi84I9L5sL18bhiN/UTf
Cc: Colin Perkins <csp@csperkins.org>, mmusic <mmusic@ietf.org>
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: Mon, 27 May 2013 13:39:20 -0000

On May 27, 2013 4:27 PM, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
wrote:

> Sure, suspect many people agree with you but the media pipeline is
>  more than just the codec. So if I have 150 thumbnail videos that all
> using VP8, using one PT for all of them might be fine given they are all
> the same codec but they still might need SSRC to be able to figure out
> which window to render them in.

How is tuis a demuxing issue?

Isn't this more closely related to application policies and hence subject
to application specific signalling? Of course that signalling can use SSRCs
but this does this make it an RTP issue?

Emil

--sent from my mobile