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 05:24 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 2E66B21E808E for <mmusic@ietfa.amsl.com>; Tue, 25 Jun 2013 22:24:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level:
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 PGf5O2xWW3yi for <mmusic@ietfa.amsl.com>; Tue, 25 Jun 2013 22:24:49 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 002B221E80EF for <mmusic@ietf.org>; Tue, 25 Jun 2013 22:24:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id C4E3539E176 for <mmusic@ietf.org>; Wed, 26 Jun 2013 07:24:46 +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 4Lfof4dlEflI for <mmusic@ietf.org>; Wed, 26 Jun 2013 07:24:42 +0200 (CEST)
Received: from [192.168.1.17] (unknown [188.113.88.47]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id D6FAF39E05D for <mmusic@ietf.org>; Wed, 26 Jun 2013 07:24:40 +0200 (CEST)
Message-ID: <51CA7B2D.5050601@alvestrand.no>
Date: Wed, 26 Jun 2013 07:25:01 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C3BAA2F@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C3BAA2F@ESESSMB209.ericsson.se>
Content-Type: multipart/alternative; boundary="------------000608080100000607000100"
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 05:24:54 -0000
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 J > > Regards, > > Christer > > > > _______________________________________________ > mmusic mailing list > mmusic@ietf.org > https://www.ietf.org/mailman/listinfo/mmusic
- [MMUSIC] DECISION: Default mechanism to map RTP d… Christer Holmberg
- Re: [MMUSIC] DECISION: Default mechanism to map R… Christer Holmberg
- Re: [MMUSIC] DECISION: Default mechanism to map R… Emil Ivov
- Re: [MMUSIC] DECISION: Default mechanism to map R… Bernard Aboba
- Re: [MMUSIC] DECISION: Default mechanism to map R… Paul Kyzivat
- Re: [MMUSIC] DECISION: Default mechanism to map R… Paul Kyzivat
- Re: [MMUSIC] DECISION: Default mechanism to map R… Harald Alvestrand
- Re: [MMUSIC] DECISION: Default mechanism to map R… Christer Holmberg
- Re: [MMUSIC] DECISION: Default mechanism to map R… Christer Holmberg
- Re: [MMUSIC] DECISION: Default mechanism to map R… Christer Holmberg
- Re: [MMUSIC] DECISION: Default mechanism to map R… Colin Perkins
- Re: [MMUSIC] DECISION: Default mechanism to map R… Harald Alvestrand
- Re: [MMUSIC] DECISION: Default mechanism to map R… Christer Holmberg
- Re: [MMUSIC] DECISION: Default mechanism to map R… Paul Kyzivat
- Re: [MMUSIC] DECISION: Default mechanism to map R… Colin Perkins
- Re: [MMUSIC] DECISION: Default mechanism to map R… Paul Kyzivat
- Re: [MMUSIC] DECISION: Default mechanism to map R… Christer Holmberg
- Re: [MMUSIC] DECISION: Default mechanism to map R… Colin Perkins
- Re: [MMUSIC] DECISION: Default mechanism to map R… Christer Holmberg
- Re: [MMUSIC] DECISION: Default mechanism to map R… Colin Perkins
- Re: [MMUSIC] DECISION: Default mechanism to map R… Paul Kyzivat