Re: [MMUSIC] BUNDLE and SCTP

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 09 April 2014 14:28 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 683C61A0346 for <mmusic@ietfa.amsl.com>; Wed, 9 Apr 2014 07:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id etGhhd_iYRrf for <mmusic@ietfa.amsl.com>; Wed, 9 Apr 2014 07:28:54 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id 8675A1A032E for <mmusic@ietf.org>; Wed, 9 Apr 2014 07:28:54 -0700 (PDT)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta07.westchester.pa.mail.comcast.net with comcast id noAq1n0031uE5Es57qUueK; Wed, 09 Apr 2014 14:28:54 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta16.westchester.pa.mail.comcast.net with comcast id nqUt1n00R3ZTu2S3cqUtGn; Wed, 09 Apr 2014 14:28:54 +0000
Message-ID: <53455925.4060002@alum.mit.edu>
Date: Wed, 09 Apr 2014 10:28:53 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <534377B6.7070708@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D2B210B@ESESSMB209.ericsson.se> <CABkgnnW4gG3NjHKjcY+Cmy_zqZOWpo9E6T4O_fc0oZoooJt=gw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D2B7844@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D2B7844@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1397053734; bh=azGDEcwkUEzegtCHbvo9HaiWT5sD8Jnn/k5Y0wmlifo=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ZxNWp93TodBDMJNNwpZ+QNz5Io9aQOhqv2nPqLaNwQoHxOk8ZDjgUK5gD0arSTwgQ HFFafIIFoYmju6krnxKBjtuHZMpZZ3BvrGIJpm7LxZBcdk3S8z0F++OclAGg+/PgZU XXX/u+OIiZjkmhJPJERlqsLLku2E7afwwitN7G8K7z0HR9hXmrKigD5lm6nnc+Ujzi Tt3BuVvnKf1TKiV7xx35JYYvRz5Kzjh4cWv/yVx45F9M+/9kYIv2pgZyGikbC7udXn NLejoGjIf3J0bFT7Fk/a89QdAxHCQAzSr2/zcJQYhqjBgU93utyEWJQjv82c2IgP4q hfvIjUFpM8DoQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/o7pZiDSuqQzf0g_oubx5VDSKWCM
Subject: Re: [MMUSIC] BUNDLE and SCTP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 09 Apr 2014 14:28:55 -0000

On 4/9/14 5:27 AM, Christer Holmberg wrote:
> Hi,
>
>>> Now, if you run multiple SCTP associations on top of that DTLS connection, you would use the SCTP port number to distinguish them.
>>
>> Or the PPID on individual frames.  The data channels draft doesn't really describe what to do with unknown PPIDs, but it could.
>
> Actually, if you have multiple SCTP associations within a BUNDLE group, none of the above would work. Because, you could end up using the same SCTP port numbers in each SCTP association.

If "two" SCTP associations have the same 5-tuple and the same SCTP ports 
on both ends then they are not really separate SCTP associations.

If the goal is to have two in the same bundle group, sharing the same 
5-tuple, then there must be a different SCTP port to distinguish them. 
That would have to be part of the rule for associating packets with 
m-lines in the bundle group.

If you wanted to associate to m-lines based on PPID, then you would need 
PPID-specific media sections. We don't currently have a way to do that.

	Thanks,
	Paul