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

Harald Alvestrand <harald@alvestrand.no> Wed, 26 June 2013 11:38 UTC

Return-Path: <harald@alvestrand.no>
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 CF6A321F9F9F for <mmusic@ietfa.amsl.com>; Wed, 26 Jun 2013 04:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.264
X-Spam-Level:
X-Spam-Status: No, score=-109.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_HEAD=1.334, RCVD_IN_DNSWL_HI=-8, 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 fNWqduomixpL for <mmusic@ietfa.amsl.com>; Wed, 26 Jun 2013 04:38:08 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id C797011E80E3 for <mmusic@ietf.org>; Wed, 26 Jun 2013 04:38:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id BE15439E17B; Wed, 26 Jun 2013 13:38:03 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wu2BgGU3ywNX; Wed, 26 Jun 2013 13:38:01 +0200 (CEST)
Received: from [10.243.75.72] (73-76-11.connect.netcom.no [176.11.76.73]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 3B40E39E166; Wed, 26 Jun 2013 13:37:55 +0200 (CEST)
User-Agent: K-9 Mail for Android
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C3BB724@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C3BAA2F@ESESSMB209.ericsson.se> <51CA7B2D.5050601@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B1C3BB724@ESESSMB209.ericsson.se>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----GBGLXOEQCGHTHMXF2KKSD0AV5SJZJ4"
From: Harald Alvestrand <harald@alvestrand.no>
Date: Wed, 26 Jun 2013 13:37:46 +0200
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Message-ID: <d70f6dba-4b41-4e12-bb00-2f34975a1cb5@email.android.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: Wed, 26 Jun 2013 11:38:13 -0000

I am on vacation now, so short answer:

Apps that use m-lines for rtp session negotiation and not for stream control need no such association.

If we mandate such association, we load those apps with extra luggage.


Christer Holmberg <christer.holmberg@ericsson.com> wrote:

>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

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.