Re: [MMUSIC] Another bundling proposal - Christer's comments

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 26 February 2013 08:04 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 C7BEA21F88A9 for <mmusic@ietfa.amsl.com>; Tue, 26 Feb 2013 00:04:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.256
X-Spam-Level:
X-Spam-Status: No, score=-6.256 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 OViikcj4bpMt for <mmusic@ietfa.amsl.com>; Tue, 26 Feb 2013 00:04:00 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id D261B21F88A1 for <mmusic@ietf.org>; Tue, 26 Feb 2013 00:03:59 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-89-512c6c6e01f0
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 66.A4.10459.E6C6C215; Tue, 26 Feb 2013 09:03:59 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.82]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.02.0318.004; Tue, 26 Feb 2013 09:03:58 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Dale R. Worley" <worley@ariadne.com>
Thread-Topic: [MMUSIC] Another bundling proposal - Christer's comments
Thread-Index: Ac4TVbJsbUziS577R021PX4477xAdwAVBnJJABNOU0A=
Date: Tue, 26 Feb 2013 08:03:58 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B107B87@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B106FE2@ESESSMB209.ericsson.se> <201302252244.r1PMiujk2613075@shell01.TheWorld.com>
In-Reply-To: <201302252244.r1PMiujk2613075@shell01.TheWorld.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM+JvjW5+jk6gwerdLBZTlz9msXh5osyB yWPy/q/MHkuW/GQKYIrisklJzcksSy3St0vgypjVvZy94CxvxeLpj9gbGN9ydTFyckgImEjM evqUDcIWk7hwbz2QzcUhJHCIUeLa8utQzmJGiZkbjjB2MXJwsAlYSHT/0wYxRQQ0JToW5ICY zALqElcXB4GMERZwlVi25TETiC0i4CaxvOceC4RtJbF2ziGwVSwCqhIrJm4Fs3kFvCV2NF1l htjUyCjRdX47E8hMTgEHiW3v+UBqGIFO+35qDdhMZgFxiVtP5jNBnCwgsWTPeWYIW1Ti5eN/ rBC2osTV6cuh6nUkFuz+xAZha0ssW/iaGWKvoMTJmU9YJjCKzUIydhaSlllIWmYhaVnAyLKK kT03MTMnvdxwEyMwOg5u+a27g/HUOZFDjNIcLErivGGuFwKEBNITS1KzU1MLUovii0pzUosP MTJxcEo1MIZtOXtnZ0z9wQUbkqVr+dh3HOBcseb2Sfnrjlc8KhPKz6/Mf/2ArWd2z1zv35e+ 9eiw+ISyLL/bff4rf4rK39yJC6K21TOtLhWK51h2bN6Boo0mN66bfyl1utQ08caV7wtSjz48 Hd+24c+Rsop/t5X8rj19apxwY1exgPvXfcr3Mo2YOKb0f1qlxFKckWioxVxUnAgA3qfZxlwC AAA=
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Another bundling proposal - Christer's comments
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, 26 Feb 2013 08:04:00 -0000

Hi,

>> I had previously provided comments to Dale off-line. Some has been 
>> addressed in the -03 version of the draft. But, I still have some 
>> questions.
>
>I'm now in the position to deal with technical improvements.
>
>> First, unless I've missed something, the mechanism is still for RTP 
>> ONLY. It is not possible to e.g. put the DataChannel in the bundle. I 
>> think we asap need to decide whether that is a requirement or not.
>
> That's true.  Although none of the other 5 proposals I've seen discuss SCTP/DataChannel multiplexing either.  Fortunately, adding support for SCTP isn't difficult, either with encapsulation or without.

You would encapsulate SCTP inside the new payload type?

>> Second, you use the non-bundle m- lines for codec negotiation etc. 
>> But, previously, when MMT was discussed, I believe that people 
>> indicated that they do not want to "refer" to other m- lines from the 
>> MMT m- line. Instead,  the information should be explicitly provided 
>> in the MMT m- line (which is the reason why the SDP size gets pretty 
>> big with MMT, as most information is duplicated).
>
> I've heard that mentioned before, but I've never seen the argument in favor of it.  Can someone tell me what it is, or provide a pointer?

It was indicated in a meeting (at the moment I can't remember which meeting, though), but I never checked whether it was added to the minutes. I guess it will be on audio recording.

But, as far as I remember, there were never much discussion about it. It was an open issue on one of my slides, and people simply indicated support for adding explicit information, rather the referencing.

Regards,

Christer