IETF Logo Mail Archive

Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?

Suhas Nandakumar <suhasietf@gmail.com> Mon, 03 March 2014 11:14 UTC

Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90A371A0CC6 for <mmusic@ietfa.amsl.com>; Mon, 3 Mar 2014 03:14:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UI61X6p8865u for <mmusic@ietfa.amsl.com>; Mon, 3 Mar 2014 03:14:47 -0800 (PST)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 8CCF11A0DE4 for <mmusic@ietf.org>; Mon, 3 Mar 2014 03:14:47 -0800 (PST)
Received: by mail-we0-f169.google.com with SMTP id w62so1193827wes.0 for <mmusic@ietf.org>; Mon, 03 Mar 2014 03:14:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rWYrd4KjGVB0VKRGZS6pDTFyF0fQf7sG80wp6iiGWNo=; b=TXHi7O23GRvGLPCaohrWKHf0w7PgpBe1Dpjqd09MgxWzbzHo1Nz53AMzRwBUVtP7TX d2nOHz7IeGwrIxm2E8ALGF0S6zOXucHgG84KHKIx1Z7YYS75TAhFj0L+mh6+mQVjLAZX U2diCfYLkd5RnBlgdq7rpeeEVDjARGw637GZnqGewr7blk5o7acnFeSpg+dxWvZgNxV1 IoTaaw7gzJ0BD1KPdVyxUkD+ENBUfMDH09RGjbPNC0kCr+p+lPsTRID1KjDDjUyj/ytz 7F9Ug+oFKt88jwIH30M0/Nfy4XgEXWNcybmi99xL+ZZLSOhV1iu1UmEHIyUbFn9BCF2s ItNg==
MIME-Version: 1.0
X-Received: by 10.194.21.193 with SMTP id x1mr16186395wje.33.1393845284312; Mon, 03 Mar 2014 03:14:44 -0800 (PST)
Received: by 10.195.12.134 with HTTP; Mon, 3 Mar 2014 03:14:44 -0800 (PST)
In-Reply-To: <A140A09A-20C9-4294-82F7-487606F98C68@csperkins.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se> <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5CCE@ESESSMB209.ericsson.se> <FF73D8EC-D4EB-4E53-8D05-63D4624F4B01@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5DDF@ESESSMB209.ericsson.se> <331AFD56-7C29-4BB3-9B63-00D1E9317F9C@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5E15@ESESSMB209.ericsson.se> <A140A09A-20C9-4294-82F7-487606F98C68@csperkins.org>
Date: Mon, 03 Mar 2014 11:14:44 +0000
Message-ID: <CAMRcRGRYLUSiz3FOTqhj=W3x++VLVW+Lwa42-PASRDEB-QLEYw@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Colin Perkins <csp@csperkins.org>
Content-Type: multipart/alternative; boundary="047d7b5d56100b1a6104f3b1e570"
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/KAtqCtVgnMS1Djkva1OrD1yyhjg
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Mar 2014 11:14:50 -0000

On Monday, March 3, 2014, Colin Perkins <csp@csperkins.org> wrote:

> On 3 Mar 2014, at 11:05, Christer Holmberg <christer.holmberg@ericsson.com<javascript:_e(%7B%7D,'cvml','christer.holmberg@ericsson.com');>>
> wrote:
>
>  Hi,
>
>  >The same way you separate every other stream: SSRC to identify the
> media source, then direct to >the right decoder path based on the PT
> mapping table.
>
>
>
> Yes, but then you need to know which SSRC(s) are going to be used for each
> media stream.
>
>
>
> Huh? You may have to explain, because I don't see that.
>
>
>
> Assume you have two video m- lines.
>
> On both m- lines, you indicate that you can receive a codec using PT value
> Y.
>
> Then, you receive a video media packet, with PT value Y, and SSRC value
> 1234567. How do you know which of the two m- lines this media packet is
> associated with?
>
> We've discussed this multiple times before. If payload types numbers are
> unique across m= lines, then obviously you can use them to identify the m=
> line. If you reuse payload type values across m= lines, then you need some
> other way of identifying m= lines, if you care about doing so. Signalled
> SSRC values are one approach, something like AppID might be another.
>
>
I agree with Colin. There needs to be a way to correlate incoming rtp
streams in this scenario and early media scenario

>
> --
> Colin Perkins
> http://csperkins.org/
>
>
>
>

v2.23.0 | Report a Bug | By Email