IETF Logo Mail Archive

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

Jonathan Lennox <jonathan@vidyo.com> Mon, 24 September 2012 18:41 UTC

Return-Path: <jonathan@vidyo.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 18E8C21F884D for <mmusic@ietfa.amsl.com>; Mon, 24 Sep 2012 11:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level:
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, J_CHICKENPOX_16=0.6]
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 n0szzmmXBpLa for <mmusic@ietfa.amsl.com>; Mon, 24 Sep 2012 11:41:31 -0700 (PDT)
Received: from mxout.myoutlookonline.com (mxout.myoutlookonline.com [64.95.72.241]) by ietfa.amsl.com (Postfix) with ESMTP id 80CE021F8449 for <mmusic@ietf.org>; Mon, 24 Sep 2012 11:41:31 -0700 (PDT)
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id C1EEB8BE5C8; Mon, 24 Sep 2012 14:41:30 -0400 (EDT)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB027.mail.lan (unknown [10.110.2.1]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mxout.myoutlookonline.com (Postfix) with ESMTPS id 7CE698BE5B9; Mon, 24 Sep 2012 14:41:30 -0400 (EDT)
Received: from BE235.mail.lan ([10.110.32.235]) by HUB027.mail.lan ([10.110.17.27]) with mapi; Mon, 24 Sep 2012 14:41:29 -0400
From: Jonathan Lennox <jonathan@vidyo.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Date: Mon, 24 Sep 2012 14:41:28 -0400
Thread-Topic: [MMUSIC] Possible BUNDLE alternative syntax: explicit m-line for bundled session
Thread-Index: Ac2ahDQOMJqhOA3YTlO85jEENn3nfQ==
Message-ID: <46F70838-8689-4C1C-9C49-B981B1E2D208@vidyo.com>
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>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05853409FF2FB4@ESESSCMS0356.eemea.ericsson.se>
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
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 18:41:32 -0000

On Sep 23, 2012, at 4:37 PM, Christer Holmberg wrote:
> 
>> 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.

--
Jonathan Lennox
jonathan@vidyo.com

v2.29.0 | Report a Bug | By Email | System Status