Re: [MMUSIC] Possible BUNDLE alternative syntax: explicit m-line for bundled session

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 24 September 2012 19:55 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 73AB021F88CA for <mmusic@ietfa.amsl.com>; Mon, 24 Sep 2012 12:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.818
X-Spam-Level:
X-Spam-Status: No, score=-5.818 tagged_above=-999 required=5 tests=[AWL=-0.169, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3z6GH66GTa1c for <mmusic@ietfa.amsl.com>; Mon, 24 Sep 2012 12:55:27 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC4821F88C1 for <mmusic@ietf.org>; Mon, 24 Sep 2012 12:55:26 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fea6d000002ccb-d0-5060baac952d
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id C8.BB.11467.CAAB0605; Mon, 24 Sep 2012 21:55:24 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.99]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Mon, 24 Sep 2012 21:55:24 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Jonathan Lennox <jonathan@vidyo.com>
Date: Mon, 24 Sep 2012 21:51:03 +0200
Thread-Topic: [MMUSIC] Possible BUNDLE alternative syntax: explicit m-line for bundled session
Thread-Index: Ac2ahDQOMJqhOA3YTlO85jEENn3nfQACbnhO
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05853409FF2FB8@ESESSCMS0356.eemea.ericsson.se>
References: <CE457B53-341D-48C8-8CD7-2A0958407F37@vidyo.com> <50222D44.5040105@alvestrand.no> <BLU401-EAS1263CBF056291C5313CA95193CD0@phx.gbl> <502258CA.5030009@alvestrand.no> <BLU002-W14079A44079EFA284B8E94793CC0@phx.gbl> <01C25C86-D664-468E-923F-4EEA506ACEDF@cisco.com> <5038E0EE.60608@alvestrand.no>, <BLU401-EAS1449593A32E42F2871B483E93BC0@phx.gbl> <7F2072F1E0DE894DA4B517B93C6A05853409FF2F24@ESESSCMS0356.eemea.ericsson.se> <503B29B6.5000000@alvestrand.no>, <0CC47B95-7817-4E2F-B7EE-04FD33E8113C@cisco.com> <7F2072F1E0DE894DA4B517B93C6A05853409FF2F97@ESESSCMS0356.eemea.ericsson.se>, <5E3FF4B9-1428-4273-8C07-CA7E09E94108@cisco.com> <7F2072F1E0DE894DA4B517B93C6A05853409FF2F98@ESESSCMS0356.eemea.ericsson.se>, <03FBA798AC24E3498B74F47FD082A92F1773E523@US70UWXCHMBA04.zam.alcatel-lucent.com> <7F2072F1E0DE894DA4B517B93C6A05853409FF2F9D@ESESSCMS0356.eemea.ericsson.se>, <03FBA798AC24E3498B74F47FD082A92F1773E53E@US70UWXCHMBA04.zam.alcatel-lucent.com> <7F2072F1E0DE894DA4B517B93C6A0585340 9FF2F9E@ESESSCMS0356. e emea.ericsson.se>, <03FBA798AC24E3498B74F47FD082A92F1773E645@US70UWXCHMBA04.zam.alcatel-lucent.com> <7F2072F1E0DE894DA4B517B93C6A05853409FF2F9F@ESESSCMS0356.eemea.ericsson.se>, <03FBA798AC24E3498B74F47FD082A92F1773E771@US70UWXCHMBA04.zam.alcatel-lucent.com> <7F2072F1E0DE894DA4B517B93C6A05853409FF2FA2@ESESSCMS0356.eemea.ericsson.se>, <03FBA798AC24E3498B74F47FD082A92F1773E7FC@US70UWXCHMBA04.zam.alcatel-lucent.com> <7F2072F1E0DE894DA4B517B93C6A05853409FF2FA4@ESESSCMS0356.eemea.ericsson.se> <DA165A8A2929C6429CAB403A76B573A5146A1409@szxeml534-mbx.china.huawei.com>, <000001cd9815$d0882190$719864b0$@co.in> <7F2072F1E0DE894DA4B517B93C6A05853409FF2FB1@ESESSCMS0356.eemea.ericsson.se>, <000601cd99bc$5b1e5bb0$115b1310$@co.in> <7F2072F1E0DE894DA4B517B93C6A05853409FF2FB4@ESESSCMS0356.eemea.ericsson.se>, <46F70838-8689-4C1C-9C49-B981B1E2D208@vidyo.com>
In-Reply-To: <46F70838-8689-4C1C-9C49-B981B1E2D208@vidyo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOLMWRmVeSWpSXmKPExsUyM+Jvre6aXQkBBp8vmlrsX3ye2eLgvlvM FlOXP2axmPypj9WityHcgdWj9dleVo+WI29ZPZYs+cnk8WH+F3aPtmd32ANYo7hsUlJzMstS i/TtErgy9qy9ylrwlLPiXuMhlgbGR+xdjJwcEgImEk2dF1kgbDGJC/fWs3UxcnEICZxilJh+ Zwo7hLOAUeJI7ymgDAcHm4CFRPc/bZAGEQENiYvPPoA1MAvsYpTY9m4GI0iCRUBV4u/EE2BT hQXiJVZsW8oM0ZAgsWvSWkYI20jiwNkTrCA2r0C4xLtXq6GWNfFL9F/7AZbgFLCVaN3dDdbA CHTe91NrmEBsZgFxiVtP5jNBnC0gsWTPeWYIW1Ti5eN/rBD1ohJ32tczQtTrSCzY/YkNwtaW WLbwNTPEYkGJkzOfsExgFJuFZOwsJC2zkLTMQtKygJFlFaNwbmJmTnq5oV5qUWZycXF+nl5x 6iZGYOQd3PJbdwfjqXMihxilOViUxHm5kvb7CwmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamC0 2fP7sffz/C0tZWnr9zaUr861sc76JtTuoKSkL5h97nOVXqTF9YSfStm9IXm+r6TfJl6+wVfG 7fGnYYuoQ9v8X4uj3/VIpZz5vOv0kXybwikaP6otquR0H6cuFumNzJvD5WUfWr9+5tJs/ykG oVmblWssu1mtz1Tc/OZxW7/V3cbXadaiViWW4oxEQy3mouJEAKGbqCOKAgAA
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Possible BUNDLE alternative syntax: explicit m-line for bundled session
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: Mon, 24 Sep 2012 19:55:27 -0000

Hi,

>>> Instead, Let us discuss the generic categories of attributes and mention in this draft.
>>
>> I am not sure I understood.
>>
>> For sure we will have to discuss how/if attributes are affected, but we need to have a general idea on how the multiplexing is going to be offered. Same ports, m=bundle, or something else...
>
> One of the major benefits of the "pure" m=bundle proposal is that we *don't* have to discuss categories of attributes (other than to make recommendations to 
> implementors).  The attributes inside each unbundled m= line need to be self-consistent, and the attributes inside the m=bundle line also need to be self-consistent, 
> but there doesn't need to be any standardized mechanism to infer the one from the others.

That is my current understanding also.

And, IF we need to define new attributes, we will of course define the usage of them from scrath :) 

For example, the m=bundle draft I'm working on defines a new SDP attribute, which maps a PT to a specific media type (audio, video etc), as it cannot be assumed that the rtpmap attribute always can be used to identity the media type (in most cases it can, though).

Regards,

Christer