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

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 27 May 2013 17:55 UTC

Return-Path: <christer.holmberg@ericsson.com>
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 E3E5921F8CB4 for <mmusic@ietfa.amsl.com>; Mon, 27 May 2013 10:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.221
X-Spam-Level:
X-Spam-Status: No, score=-5.221 tagged_above=-999 required=5 tests=[AWL=-0.172, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
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 JBcZ9vOtsL+S for <mmusic@ietfa.amsl.com>; Mon, 27 May 2013 10:55:49 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 363D521F8AD1 for <mmusic@ietf.org>; Mon, 27 May 2013 10:55:49 -0700 (PDT)
X-AuditID: c1b4fb25-b7efb6d000007c26-2b-51a39e236f9b
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 4D.58.31782.32E93A15; Mon, 27 May 2013 19:55:48 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.02.0328.009; Mon, 27 May 2013 19:55:47 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] Scope of RTP payload types in BUNDLE?
Thread-Index: AQHOWtXocH/Y1zQW/EWt7TkWSefrJ5kY2NQAgAAiw8D//+EkAIAAIgyA///fnwCAAHHXZg==
Date: Mon, 27 May 2013 17:55:46 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C379D6E@ESESSMB209.ericsson.se>
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>
In-Reply-To: <599C780A-F483-470E-91F2-68DBA605C79C@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFLMWRmVeSWpSXmKPExsUyM+Jvra7KvMWBBvePslksf3mC0WLq8scs Dkwe0+7fZ/NYsuQnUwBTFJdNSmpOZllqkb5dAlfGsQlX2Qr2cVZM3LOVuYFxB3sXIyeHhICJ xLuZe1ggbDGJC/fWs4HYQgKHGSUm7SvuYuQCspcwSszc9B0owcHBJmAh0f1PG6RGREBVYsfx f4wgYWYBLYnObdYgprCAtcTBOewQFTYSDdP/s0DYYRKfnn1gBLFZgDofzt3PBGLzCvhK/Lry lRVi02smibOzFoM1cAo4SrSu3AnWwAh02vdTa8AamAXEJW49mc8EcbKAxJI955khbFGJl4// sULYihLtTxsYIep1JBbs/sQGYWtLLFv4mhlisaDEyZlPWCYwis1CMnYWkpZZSFpmIWlZwMiy ipE9NzEzJ73caBMjMD4ObvmtuoPxzjmRQ4zSHCxK4rx6vIsDhQTSE0tSs1NTC1KL4otKc1KL DzEycXBKNTCKLNZ6r/ix+O4/yfB/JmXuphe/NZSKusWcvGPT0Pj2f/bpKSwivPutOlb99VlT 8GCffr8Q36RDWiUulWoqkTUSxzl/px4UvRr9I9euWjiBa9H9Y07MNrsmX6lJXrX5kP4tfaY9 Qpvzz8TN2D5lRrbSG11hrQ8L2ta9kLqdHbA/eP+FjYqccWuVWIozEg21mIuKEwF6tOiEXQIA AA==
Cc: "mmusic@ietf.org WG" <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 17:55:55 -0000

Hi,

>>>> v=0
>>>> o=alice 2890844526 2890844526 IN IP4 host.anywhere.com s= c=IN IP4
>>>> host.anywhere.com
>>>> t=0 0
>>>> m=audio 49170 RTP/AVP 96
>>>> a=rtpmap:96 AMR-WB/16000
>>>> m=audio 49170 RTP/AVP ???
>>>> a=rtpmap:??? AMR-WB/16000
>>>
>>> Not sure I get your point. You can have two different payload types that map to the same payload format in a single RTP session, since
>>> you can always distinguish what payload format is intended. You can't have the same payload type mapping to two different payload
>>> formats in a single RTP session, since you can't then infer what payload format was meant.
>>
>> Please not that both PTs map to the SAME payload format :)
>
> I thought I addressed that in my reply.

I am not sure you did - at least I didn't get it :)

Again, my understanding of what you said is that, for any payload format within an RTP session, the PT value has to be unique.

In the example above the same payload format, within the same RTP session, is used in two separate m- lines. But, I still can't use the same PT value for both m- lines, even if the payload format is the same, can I?

Regards,

Christer