IETF Logo Mail Archive

Re: [MMUSIC] DECISION: Default mechanism to map RTP data to m- line is based on PT?

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 26 June 2013 07:14 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 C030921E808E for <mmusic@ietfa.amsl.com>; Wed, 26 Jun 2013 00:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level:
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, 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 S67STWoylP4m for <mmusic@ietfa.amsl.com>; Wed, 26 Jun 2013 00:14:42 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0551621E80B4 for <mmusic@ietf.org>; Wed, 26 Jun 2013 00:14:41 -0700 (PDT)
X-AuditID: c1b4fb25-b7fed6d000004760-de-51ca94e06b99
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 0B.CC.18272.0E49AC15; Wed, 26 Jun 2013 09:14:41 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.6]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.02.0328.009; Wed, 26 Jun 2013 09:14:40 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Harald Alvestrand <harald@alvestrand.no>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] DECISION: Default mechanism to map RTP data to m- line is based on PT?
Thread-Index: Ac5xlz4qXnbgXU0zSAKuYyddRY0NgwAhX+uAAAfyqoA=
Date: Wed, 26 Jun 2013 07:14:40 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3BB724@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C3BAA2F@ESESSMB209.ericsson.se> <51CA7B2D.5050601@alvestrand.no>
In-Reply-To: <51CA7B2D.5050601@alvestrand.no>
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: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C3BB724ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUyM+Jvre7DKacCDQ6dZrM41tfFZjF1+WMW ByaPKxOusHosWfKTKYApissmJTUnsyy1SN8ugSvj/uZfjAXf/SpeLtjA2sA4waWLkZNDQsBE YvXXhywQtpjEhXvr2boYuTiEBA4zShxoucQO4SxilGhfsJmpi5GDg03AQqL7nzZIg4hAsMTy T9vBwsICcRJ7dpmBmCIC8RKHZhlBVFhJdLydzAxiswioSmyauxnM5hXwlWh9/R9srZBAgcSV vinsIDangK7EgQcHWEFsRqBzvp9awwRiMwuIS9x6Mp8J4kwBiSV7zjND2KISLx//Y4WwFSXa nzYwQtTnS8yaso8NYpegxMmZT1gmMIrMQjJqFpKyWUjKIOJ6EjemTmGDsLUlli18zQxh60rM +HeIBVl8ASP7Kkb23MTMnPRyo02MwLg5uOW36g7GO+dEDjFKc7AoifN+PLUrUEggPbEkNTs1 tSC1KL6oNCe1+BAjEwenVANjceSxXS1fLh0L70/3mnjOesKOiBmT/bY+m8NwfEL8jLiMh+ka C+WDH5lcidh799MjeYl4hkcscc1n5GbrFXYuWDppzd1FTVMPnnI0ns3JcpXvTvwzlx3z3/WJ 7/695syEI1JhGgaMm1d6sRf/q930JdXUcxZb+1zGBVM1sw9x+1i65qycanL2vBJLcUaioRZz UXEiACDOXQZpAgAA
Subject: Re: [MMUSIC] DECISION: Default mechanism to map RTP data to m- line is based on PT?
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, 26 Jun 2013 07:14:47 -0000

Hi Harald,

Just for my clarification: Assuming we are talking about applications using RTP (instead of ANY BUNDLE application), is your answer to Q3 still "no"?

In other words, do you think there might be RTP cases where it is not needed to associate the RTP data with an m- line?

OR, do you think that BUNDLE simply shouldn't say anything about how to map RTP packets to m- lines?

Regards,

Christer


From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of Harald Alvestrand
Sent: 26. kesäkuuta 2013 8:25
To: mmusic@ietf.org
Subject: Re: [MMUSIC] DECISION: Default mechanism to map RTP data to m- line is based on PT?

On 06/25/2013 01:34 PM, Christer Holmberg wrote:
Hi,

Emil suggested that the default, "MTI", mechanism for mapping RTP data to m- lines should be based on PT. Applications are allowed to use whatever other mechanisms, but usage of such mechanisms must be negotiated (or, applications need to have some other means knowing that the other endpoint support such mechanisms).

Q3: Do we need to specify a default, MTI, mechanism for mapping RTP data to m- lines?

No. This makes the assumption that all applications have the need to map RTP data to m-lines; this assumption is not proven (and probably cannot be - it's hard to prove a negative. It might be possible to disprove it, though).



Q4: If Q3, do we mandate applications to support, and use (unless applications are made aware of other mechanisms supported by all endpoints) PT for mapping received RTP media?

If the WG disagrees with me on Q3, it might as well go down this path. I have no strong opinion.



This means that, when mapping RTP to m- lines is required (whether it is always mandated is discussed in another thread), within a BUNDLE group each PT value must be unique to an individual m- line.

NOTE: If your answer to Q3 is "yes", but your answer to Q4 is "no", please indicate which mechanism you prefer :)

Regards,

Christer




_______________________________________________

mmusic mailing list

mmusic@ietf.org<mailto:mmusic@ietf.org>

https://www.ietf.org/mailman/listinfo/mmusic

v2.23.0 | Report a Bug | By Email