[MMUSIC] DECISION: Default mechanism to map RTP data to m- line is based on PT?
Christer Holmberg <christer.holmberg@ericsson.com> Tue, 25 June 2013 11:34 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 998BD21F9F80 for <mmusic@ietfa.amsl.com>; Tue, 25 Jun 2013 04:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.867
X-Spam-Level:
X-Spam-Status: No, score=-5.867 tagged_above=-999 required=5 tests=[AWL=0.381, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, 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 w0XSdCMLAvA9 for <mmusic@ietfa.amsl.com>; Tue, 25 Jun 2013 04:34:12 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id A28C321F9F4E for <mmusic@ietf.org>; Tue, 25 Jun 2013 04:34:11 -0700 (PDT)
X-AuditID: c1b4fb25-b7f0a6d000005db8-d2-51c98032911d
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id A0.94.23992.23089C15; Tue, 25 Jun 2013 13:34:10 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.6]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.02.0328.009; Tue, 25 Jun 2013 13:34:09 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: DECISION: Default mechanism to map RTP data to m- line is based on PT?
Thread-Index: Ac5xlz4qXnbgXU0zSAKuYyddRY0Ngw==
Date: Tue, 25 Jun 2013 11:34:09 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3BAA2F@ESESSMB209.ericsson.se>
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: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C3BAA2FESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM+Jvra5Rw8lAgyWXpC2mLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujAlXnrIULFOtmL3ep4FxgkIXIyeHhICJxL9v+9ghbDGJC/fW s3UxcnEICRxmlJj3FMThBHIWMUosXOzdxcjBwSZgIdH9TxskLCKgLvF1bw8zSFhYIFBiWl8R RDhMYs2G14wQtp7ExW8drCA2i4CqxJpHr5hBbF4BX4m/7yYwgdiMQGu/n1oDZjMLiEvcejKf CeIcAYkle84zQ9iiEi8f/2OFsBUl2p82MELU50v8uPqDDWKmoMTJmU9YJjAKzUIyahaSsllI yiDiOhILdn9ig7C1JZYtfM0MY5858JgJWXwBI/sqRvbcxMyc9HKjTYzAgD+45bfqDsY750QO MUpzsCiJ8348tStQSCA9sSQ1OzW1ILUovqg0J7X4ECMTB6dUA2PukcXx/364Fe9UvLpvr8Ry y2KmZkfFKHZdozXptU+3JW9RXfL37pLi7StiMwW1pa4kqWx/eviRap29bumirKoHExN7Zywv Vqg92Z+4uXmK+fyOclmLDIM/WqoJFRn+YlE6m079YXG2WOqlFfo+UuTry4qoQ+dzfH63Xguq ORkjwtjgL9NhrcRSnJFoqMVcVJwIAKXgJfRGAgAA
Subject: [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 11:34:18 -0000
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 :) Regards, Christer
- [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