[MMUSIC] BUNDLE DISCUSION: Always mandate mechanism to map received data to m- line?

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 25 June 2013 11:16 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 756FE11E80E8 for <mmusic@ietfa.amsl.com>; Tue, 25 Jun 2013 04:16:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.066
X-Spam-Level:
X-Spam-Status: No, score=-4.066 tagged_above=-999 required=5 tests=[AWL=-1.468, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 9Ap5Rhk1QOV8 for <mmusic@ietfa.amsl.com>; Tue, 25 Jun 2013 04:16:14 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 9758921E8090 for <mmusic@ietf.org>; Tue, 25 Jun 2013 04:16:12 -0700 (PDT)
X-AuditID: c1b4fb38-b7f476d0000049c9-51-51c97bfbbea7
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id B6.13.18889.BFB79C15; Tue, 25 Jun 2013 13:16:11 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.6]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.02.0328.009; Tue, 25 Jun 2013 13:16:10 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE DISCUSION: Always mandate mechanism to map received data to m- line?
Thread-Index: Ac5xlSdsNUfHWYPzSBOEmKK71uD2NA==
Date: Tue, 25 Jun 2013 11:16:10 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3BA9EF@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_7594FB04B1934943A5C02806D1A2204B1C3BA9EFESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUyM+Jvre7v6pOBBk9WS1pMXf6YxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGXun32cumKZYcWHeLeYGxv0yXYycHBICJhLTt61jhbDFJC7c W88GYgsJHGWUOHlBsIuRC8hexCixqOcjexcjBwebgIVE9z9tkBoRAXWJr3t7mEFsYYEwidPt /WwQ8WiJ3tXTWUDKRQT0JO6vKwMJswioSkzuX8oOYvMK+Ep8fX8KrJURaO33U2uYQGxmAXGJ W0/mM0GcIyCxZM95ZghbVOLl439QZypKtD9tYISoz5c4f+cVI8RMQYmTM5+wTGAUmoVk1Cwk ZbOQlEHEdSQW7P7EBmFrSyxb+JoZxj5z4DETsvgCRvZVjBzFqcVJuelGBpsYgUF/cMtvix2M l//aHGKU5mBREuf9dGpXoJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbGU32LNf/dtHrj6hQS emZyxCFtvhlbVJhbVzdPZ+GMX5pvsUjkWrJQuKNZTvbXjsZ96VfUuu23ezz4nsDcFRrp7qx+ PnTurJqjJv8/ZCgEhQu/3271xuurgo2q4jXOb742D5R4bqh0PXscc95R5WCYPPuExdPWrwoT zpZmULpzpyCga06A/mQlluKMREMt5qLiRAD2btN4SAIAAA==
Subject: [MMUSIC] BUNDLE DISCUSION: Always mandate mechanism to map received data to m- line?
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:16:20 -0000

Hi,

There has been some discussions about whether BUNDLE should mandate that users are mandated to always (no matter what transport protocols are used in the BUNDLE group) have a mechanism to map received data to an m- line, or whether it from a generic BUNDLE perspective should be optional - IF there would be cases where it's not needed.

We haven't had that much discussion about it yet, so I will not ask a DECISION question at this point, but I would really like to get some input from people who have opinions about this :)

Note that this issue is NOT about HOW to map data to m- lines (there will be a separate question about how to map RTP to m- lines etc), or whether we should allow usage of the same PT value (for the same codec configuration) in multiple m- lines, but more about a general rule.

Regards,

Christer