Re: [MMUSIC] RFC 6190 Single Session Transport

Jonathan Lennox <jonathan@vidyo.com> Fri, 19 July 2013 14:55 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 6423B21E80E1 for <mmusic@ietfa.amsl.com>; Fri, 19 Jul 2013 07:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.049, 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 3PkSFa5FqygH for <mmusic@ietfa.amsl.com>; Fri, 19 Jul 2013 07:54:33 -0700 (PDT)
Received: from mxout.myoutlookonline.com (mxout.myoutlookonline.com [64.95.72.243]) by ietfa.amsl.com (Postfix) with ESMTP id 4CEFC11E8249 for <mmusic@ietf.org>; Fri, 19 Jul 2013 07:54:33 -0700 (PDT)
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id CFD258BE947; Fri, 19 Jul 2013 10:54:42 -0400 (EDT)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB028.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 80EBA8BE830; Fri, 19 Jul 2013 10:54:42 -0400 (EDT)
Received: from BE235.mail.lan ([10.110.32.235]) by HUB028.mail.lan ([10.110.17.28]) with mapi; Fri, 19 Jul 2013 10:54:22 -0400
From: Jonathan Lennox <jonathan@vidyo.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Date: Fri, 19 Jul 2013 10:54:26 -0400
Thread-Topic: [MMUSIC] RFC 6190 Single Session Transport
Thread-Index: Ac6Ej4v+6jWzG2xqSoq9enQcMW5ZTg==
Message-ID: <3AD93742-DBA4-4EDD-80AD-A667994ECE8D@vidyo.com>
References: <BLU169-W630D4FBAA70899F6C54A0593830@phx.gbl>, <3879D71E758A7E4AA99A35DD8D41D3D91D487E63@xmb-rcd-x14.cisco.com>, <EE556E46-54C1-4AAB-B03A-56FB8971D8A2@vidyo.com> <BLU169-W1208949649FACAC3137B05C93630@phx.gbl>
In-Reply-To: <BLU169-W1208949649FACAC3137B05C93630@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_3AD93742DBA44EDD80ADA667994ECE8Dvidyocom_"
MIME-Version: 1.0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] RFC 6190 Single Session Transport
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, 19 Jul 2013 14:55:03 -0000

On Jul 18, 2013, at 10:02 PM, Bernard Aboba <bernard_aboba@hotmail.com<mailto:bernard_aboba@hotmail.com>> wrote:

Jonathan said:

"I don't understand how single-session multi-source transmission will work without either a) signaling "a=ssrc-group DDP" decoding dependencies, or b) making various implementation-specific assumptions about the structure of the SVC streams."

[BA] In terms of SDP choices for expressing layering within a single m line, you can either go the a=ssrc-group:DDP route, or use distinct payload types for each layer and RFC 5583 a=group:DDP (this is what "Unified Plan" Section 4.7 appears to advocate).

I'm not sure how "MST within a single session" could be expressed in SDP without BUNDLE.  Was the idea to use multiple m lines and group them together but use the same port?

I think the authors of RFC 6190 didn't see a use case for MST within a single RTP session -- all of the interesting MST use cases they saw involved separate transport flows for the separate layers, and if you're sending all the layers on a single transport flow, SST is significantly simpler.

What requirement are you trying to achieve that's met by MST in a single session, but not by SST?

--
Jonathan Lennox
jonathan@vidyo.com<mailto:jonathan@vidyo.com>