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

Bernard Aboba <bernard_aboba@hotmail.com> Tue, 25 June 2013 17:11 UTC

Return-Path: <bernard_aboba@hotmail.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 3848211E8110 for <mmusic@ietfa.amsl.com>; Tue, 25 Jun 2013 10:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level:
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_14=0.6, USER_IN_WHITELIST=-100]
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 bAG+pzYREd77 for <mmusic@ietfa.amsl.com>; Tue, 25 Jun 2013 10:11:29 -0700 (PDT)
Received: from blu0-omc3-s14.blu0.hotmail.com (blu0-omc3-s14.blu0.hotmail.com [65.55.116.89]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB4611E810D for <mmusic@ietf.org>; Tue, 25 Jun 2013 10:11:29 -0700 (PDT)
Received: from BLU403-EAS314 ([65.55.116.73]) by blu0-omc3-s14.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 25 Jun 2013 10:11:29 -0700
X-TMN: [HttogwBUHEmppodiDQtuDE/wGb5NBW2S]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU403-EAS31453FD29F30B55A6F15CF1938B0@phx.gbl>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
References: <7594FB04B1934943A5C02806D1A2204B1C3BAA2F@ESESSMB209.ericsson.se> <51C9CD45.3050404@jitsi.org>
From: Bernard Aboba <bernard_aboba@hotmail.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <51C9CD45.3050404@jitsi.org>
Date: Tue, 25 Jun 2013 10:11:20 -0700
To: Emil Ivov <emcho@jitsi.org>
X-OriginalArrivalTime: 25 Jun 2013 17:11:29.0011 (UTC) FILETIME=[082FE430:01CE71C7]
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
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: Tue, 25 Jun 2013 17:11:34 -0000

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.

On Jun 25, 2013, at 10:03 AM, "Emil Ivov" <emcho@jitsi.org> wrote:

> 
> 
> 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