[MMUSIC] BUNDLE and SCTP

Christian Groves <Christian.Groves@nteczone.com> Tue, 08 April 2014 04:14 UTC

Return-Path: <Christian.Groves@nteczone.com>
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 764051A00D7 for <mmusic@ietfa.amsl.com>; Mon, 7 Apr 2014 21:14:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2
X-Spam-Level: **
X-Spam-Status: No, score=2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_111=0.6, J_CHICKENPOX_12=0.6] 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 HRV7xa629gyL for <mmusic@ietfa.amsl.com>; Mon, 7 Apr 2014 21:14:53 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED6F41A00C3 for <mmusic@ietf.org>; Mon, 7 Apr 2014 21:14:52 -0700 (PDT)
Received: from ppp118-209-163-70.lns20.mel6.internode.on.net ([118.209.163.70]:54429 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1WXNQn-0002DJ-RP for mmusic@ietf.org; Tue, 08 Apr 2014 14:14:41 +1000
Message-ID: <534377B6.7070708@nteczone.com>
Date: Tue, 08 Apr 2014 14:14:46 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mmusic mailing list <mmusic@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/UVHza9cdUIh_gl_SgL2Qj5ZSkfA
Subject: [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: Tue, 08 Apr 2014 04:14:57 -0000

Hello

Currently the BUNDLE draft focuses of the use of BUNDLE wrt to RTP. 
However a recent email from Paul K highlighted a potential use for SCTP, 
e.g.

/Bundling would apply in a case such as in section 10.1 of 
draft-ietf-mmusic-sdp-bundle-negotiation-05. That example would be 
rewritten as follows: //
////
//  a=group:BUNDLE dc bfcp t38 //
//  m=application 12345 DTLS/SCTP webrtc-datachannel \ //
//          sctp-port#5000 streams#16 max-message-size#100000 //
//  c=IN IP4 example.com //
//  a=mid:dc //
//  m=application 12345 DTLS/SCTP bfcp \ //
//          sctp-port#5001 streams#1 max-message-size#16384 //
//  c=IN IP4 example.com //
//  a=mid:bfcp //
////
//  m=application 12345 DTLS/SCTP t38 \ //
//          sctp-port#5002 streams#1 max-message-size#65536 //
//  c=IN IP4 example.com //
//  a=mid:t38 /

Clause 7.1/draft-ietf-mmusic-sdp-bundle-negotiation-06 indicates several 
mechanisms that need to be described by a specification for new 
protocols (e.g. SCTP). I wonder if we should add a clause to 
draft-ietf-mmusic-sctp-sdp-06 to document the relation of the SCTP SDP 
to BUNDLE usage?

Regards, Christian