IETF Logo Mail Archive

Re: [MMUSIC] BUNDLE and DATA CHANNEL

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 26 April 2013 07:44 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 CFCB021F86F4 for <mmusic@ietfa.amsl.com>; Fri, 26 Apr 2013 00:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.95
X-Spam-Level:
X-Spam-Status: No, score=-4.95 tagged_above=-999 required=5 tests=[AWL=1.299, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 UefEW3lukcp0 for <mmusic@ietfa.amsl.com>; Fri, 26 Apr 2013 00:44:57 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id D655621F8618 for <mmusic@ietf.org>; Fri, 26 Apr 2013 00:44:56 -0700 (PDT)
X-AuditID: c1b4fb30-b7f266d000000cb5-7b-517a3077b201
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 04.E6.03253.7703A715; Fri, 26 Apr 2013 09:44:55 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.02.0328.009; Fri, 26 Apr 2013 09:44:55 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Dale R. Worley" <worley@ariadne.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [MMUSIC] BUNDLE and DATA CHANNEL
Thread-Index: AQHOQgMEIk6q+PHpSI2jUL+JN2f+GpjoHi4g
Date: Fri, 26 Apr 2013 07:44:54 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C361D3A@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C35F47A@ESESSMB209.ericsson.se> <51796D46.9030300@alum.mit.edu> <201304252219.r3PMJv6C3392749@shell01.TheWorld.com>
In-Reply-To: <201304252219.r3PMJv6C3392749@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+NgFrrELMWRmVeSWpSXmKPExsUyM+JvrW65QVWgwcNZ5hZTlz9msVix4QCr xcsTZQ7MHn/ff2DymLz/K7PHkiU/mQKYo7hsUlJzMstSi/TtErgytvxYxVhwkKNizulzzA2M j9i6GDk5JARMJJbeXMMKYYtJXLi3HiwuJHCYUeLqdd4uRi4gewmjxJ6F+9i7GDk42AQsJLr/ aYPUiAgESmzrOs0KEmYWUJe4ujgIxBQW0JV4vDgGxBQR0JNoOVEDUWwkMbm5iQnEZhFQlXi1 5wTYIl4BX4nPe5+zQCxayigx4+YVsGs4BRwk1l76zghiMwJd9v3UGrBmZgFxiVtP5jNBXCwg sWTPeWYIW1Ti5eN/UJ8oSlydvhyqXkdiwe5PbBC2tsSyha+ZIRYLSpyc+YRlAqPYLCRjZyFp mYWkZRaSlgWMLKsY2XMTM3PSy803MQLj5eCW3wY7GDfdFzvEKM3BoiTOO0OqMlBIID2xJDU7 NbUgtSi+qDQntfgQIxMHp1QD4zY77fI1ofVP+NzLGHx0zm9u5tny8YF4S/RDwZK98pu5Lawk uXQeFvaub7D/Hzth95RrU6++XzpDovDKt8WLNj/USgjc9sNIPvXe9r28ziItaxz5Ni0Lq6x4 dXFh+eLQ7fplm2r+uP780/jt1QKPAOVPBZ8e1paf/apnlh4eNzf19vcZx1by3lFiKc5INNRi LipOBAA2A7+gZQIAAA==
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE and DATA CHANNEL
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: Fri, 26 Apr 2013 07:44:58 -0000

Hi,

>> Yes - we need a way to signal the demux mechanism to be used.
>> (Unless there is only one possibility. And we have already disproved 
>> that.)
>
> We could use different group "semantics" values to indicate the multiplexing mechanism.  One endpoint could probe the other to discover 
> which mechanisms it supplies by offering a collection of bundles containing no constituents, one for each mechanism.  The answer will show 
> which mechanisms the answerer supports.

My idea was the endpoint simply lists the media description proto values that it is capable of multiplexing for a given 5-tuple:

	Example: a=muxcap: RTP/AVP, SCTP/DTLS

...or something like that.

Of course, an endpoint needs to be able to multiplex all media that it inserts in a bundle group. But, it may not always insert m- lines for everything it is able to multiplex, so I think an explicit indication would be good.

It is important to remember that, whatever you multiplex, all media have to use the same IP transport (e.g. UDP).

Regards,

Christer

v2.23.0 | Report a Bug | By Email