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:05 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 B197221E808E for <mmusic@ietfa.amsl.com>; Wed, 26 Jun 2013 00:05:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level:
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_14=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 RqbKrmySaaQD for <mmusic@ietfa.amsl.com>; Wed, 26 Jun 2013 00:05:06 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id CE9C521E80B4 for <mmusic@ietf.org>; Wed, 26 Jun 2013 00:05:04 -0700 (PDT)
X-AuditID: c1b4fb30-b7fab6d00000040c-12-51ca929fe0d5
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 71.4B.01036.F929AC15; Wed, 26 Jun 2013 09:05:03 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.6]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.02.0328.009; Wed, 26 Jun 2013 09:05:02 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>, Emil Ivov <emcho@jitsi.org>
Thread-Topic: [MMUSIC] DECISION: Default mechanism to map RTP data to m- line is based on PT?
Thread-Index: Ac5xlz4qXnbgXU0zSAKuYyddRY0NgwAHdeyAAABKWwAAIT/5AA==
Date: Wed, 26 Jun 2013 07:05:02 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3BB6D3@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C3BAA2F@ESESSMB209.ericsson.se> <51C9CD45.3050404@jitsi.org> <BLU403-EAS31453FD29F30B55A6F15CF1938B0@phx.gbl>
In-Reply-To: <BLU403-EAS31453FD29F30B55A6F15CF1938B0@phx.gbl>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrPLMWRmVeSWpSXmKPExsUyM+Jvre78SacCDV7uELbYv+Qys8WanRNY LKYuf8ziwOzxuOcMm8eSJT+ZPP6/CQxgjuKySUnNySxLLdK3S+DKuHlIvWCTbMX3S99ZGhgv yHQxcnJICJhIPOy+xAphi0lcuLeerYuRi0NI4DCjxKxzi1ghnEWMEk3dW4AcDg42AQuJ7n/a IA0iAl4S3+d/YAcJMwuoS1xdHARiCgvESezZZQZiigjESxyaZQRR7CRxr2M2E4jNIqAq8etS EzOIzSvgK3Hk4AuwC4QE5jJK3GorAbE5BWwlfs6dxAhiMwJd9v3UGrBeZgFxiVtP5jNBXCwg sWTPeWYIW1Ti5eN/UJ8oSrQ/bWCEOExTYv0ufYhWRYkp3Q/ZIdYKSpyc+YRlAqPYLCRTZyF0 zELSMQtJxwJGllWM7LmJmTnp5eabGIGRcnDLb4MdjJvuix1ilOZgURLn/XRqV6CQQHpiSWp2 ampBalF8UWlOavEhRiYOTqkGxjNFP75+vNN2N2RTvscqTgfjpZdEvk5fuuSFmneG6aPnYvKm vna1M85rNZosur901rJ3wguLFkz5bvnCN22WYMajTZ1tD/n0pE9NNc0QM9/a+zJ4AeM13V0n 4xN3pEQYnnR/Ind65Yr9DA2b1Odw1G3dczxD1li9faZx9L/bmSxLbhTvTuuzmq7EUpyRaKjF XFScCAAprKLEYgIAAA==
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
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:05:20 -0000

Hi,

> Agree with Emil that "default" makes more sense for use of PT for mapping to an m line. If a=SSRC is specified on an m line then that should take precedence over PT.

Sure, but a=SSRC would be "whatever other mechanism" :)

The question is, though, how much BUNDLE should talk about "other mechanisms".

Regards,

Christer



> On 25.06.13, 13:34, Christer Holmberg wrote:
>> Hi,
>> 
>> Emil suggested that the default, “MTI”, mechanism for mapping RTP 
>> data to m- lines should be based on PT.
> 
> Actually, what I thought was important was having it as the "default" mechanism. Personally I don't mind having it as MTI might but it might be a tad too strong: implementations that deem PT demux insufficient and wouldn't want to use bundle without it, don't need implement it.
> 
> We should probably also agree on how an answerer can determine whether or not it is expected to provide additional demuxing information (e.g. SSRCs) or if the offerer is using the default mechanism.
> 
> One way would be for the answerer to inspect all m= lines and try to detect duplicating PTs. This could be a bit clumsy though. The offerer could expect SSRCs but its first offer may not yet contain PT reuse.
> 
> With that in mind ... (more below)
> 
>> 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?
> 
> I am in favour of having a "default" one.
> 
> Without this BUNDLE would have to be an abstract spec and I don't see why we would want to leave it that way.
> 
>> *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?
> 
> In favour.
> 
> Cheers,
> Emil
> 
>> 
>> 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 J
>> 
>> Regards,
>> 
>> Christer
>> 
>> 
>> 
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
> 
> --
> https://jitsi.org
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic