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:11 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 ED13821E8119 for <mmusic@ietfa.amsl.com>; Wed, 26 Jun 2013 00:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level:
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 m76IGKZfPIU0 for <mmusic@ietfa.amsl.com>; Wed, 26 Jun 2013 00:11:40 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 68C4521E808E for <mmusic@ietf.org>; Wed, 26 Jun 2013 00:11:40 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f146d00000411d-11-51ca942bdbf5
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 36.BB.16669.B249AC15; Wed, 26 Jun 2013 09:11:39 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.6]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.02.0328.009; Wed, 26 Jun 2013 09:11:39 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "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: Ac5xlz4qXnbgXU0zSAKuYyddRY0NgwAIStwAACDM+QA=
Date: Wed, 26 Jun 2013 07:11:38 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3BB713@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C3BAA2F@ESESSMB209.ericsson.se> <51C9D2DA.7090703@alum.mit.edu>
In-Reply-To: <51C9D2DA.7090703@alum.mit.edu>
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+NgFtrDLMWRmVeSWpSXmKPExsUyM+Jvra72lFOBBmvPKVlMXf6YxWLFhgOs Dkwef99/YPJYsuQnUwBTFJdNSmpOZllqkb5dAlfGjq+1Bb3CFY+P/GRsYJzE38XIySEhYCKx ePoSVghbTOLCvfVsXYxcHEIChxkl1n3azgrhLGKUODj5GnMXIwcHm4CFRPc/bZAGEQFfiWeP b7OBhIUF4iT27DIDMUUE4iUOzTKCqLCS+N2wjxHEZhFQlXj1vo8FpIQXqPNmqzNIWEggX+LC syawCzgFdCRuPWlgBrEZga75fmoNE4jNLCAOFJ/PBHGlgMSSPeeZIWxRiZeP/0FdryjR/rSB EaJeR2LB7k9sELa2xLKFr8HqeQUEJU7OfMIygVF0FpKxs5C0zELSMgtJywJGllWM7LmJmTnp 5YabGIExcHDLb90djKfOiRxilOZgURLn/XBqV6CQQHpiSWp2ampBalF8UWlOavEhRiYOTqkG RsGyf/7bBKrzr1bsaLgm8jM88GLLrmSHV/4FFxinOvYmxKRsvZ55etaeT7KR2kUsJ564BBnd tdn+U7jfxD9sys05Wa4P+T47ucW2JDWXZ27/lmtgafD1R9fEC+f4lr9gNtYp+MxfKh1s55Bp cP2ZldN67Q8Rx0Rud7grvTDe/8VLrya0ZM9GJZbijERDLeai4kQAsdwZDE8CAAA=
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:11:46 -0000

Hi,

> I guess if you want to call this a "default" MTI mechanism *for RTP*, then I won't object.

Yes, I should have clarified that it was for RTP.

> But doing so is mostly stating the obvious.

We should be careful to make such assumptions :)

> The reason it can be the default is because there is no way to have an RTP m-line without a PT. So if you are bundling RTP m-lines, then you have PT available on every m-line to use for associating packets with m-lines.
>
> But that is only sufficient if a given PT only appears on a single m-line. 

Correct, and I think it is good to point that out, eventhough it may seem obvious to many.

> Its also insufficient if there are non-RTP m-lines.
>
> If you choose to have non-RTP m-lines in the bundle, or multiple RTP m-lines with the same PT, then you are obligated to support some other 
> mechanism, and for it to be signaled in such a way that both sides will understand what it is.

The mechanism to find the right "type" of m- line is a separate issue :)

Regards,

Christer



On 6/25/13 7:34 AM, 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?
>
> *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?
>
> 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
>

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic