IETF Logo Mail Archive

Re: [MMUSIC] BUNDLE and SCTP

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 08 April 2014 06:32 UTC

Return-Path: <christer.holmberg@ericsson.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 9B5C41A00E6 for <mmusic@ietfa.amsl.com>; Mon, 7 Apr 2014 23:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.04
X-Spam-Level:
X-Spam-Status: No, score=-0.04 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_111=0.6, J_CHICKENPOX_12=0.6, SPF_PASS=-0.001] 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 XbI1JzTQOzum for <mmusic@ietfa.amsl.com>; Mon, 7 Apr 2014 23:32:23 -0700 (PDT)
Received: from sesbmg21.mgmt.ericsson.se (sesbmg21.ericsson.net [193.180.251.49]) by ietfa.amsl.com (Postfix) with ESMTP id 552A61A0032 for <mmusic@ietf.org>; Mon, 7 Apr 2014 23:32:23 -0700 (PDT)
X-AuditID: c1b4fb31-b7f688e000003e64-52-534397f08c23
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg21.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 5C.E6.15972.0F793435; Tue, 8 Apr 2014 08:32:16 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.191]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0174.001; Tue, 8 Apr 2014 08:32:16 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christian Groves <Christian.Groves@nteczone.com>, mmusic mailing list <mmusic@ietf.org>
Thread-Topic: [MMUSIC] BUNDLE and SCTP
Thread-Index: AQHPUuEbwayfPpGMZEGm2abKWEa/45sHQSRA
Date: Tue, 08 Apr 2014 06:32:16 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D2B210B@ESESSMB209.ericsson.se>
References: <534377B6.7070708@nteczone.com>
In-Reply-To: <534377B6.7070708@nteczone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsUyM+Jvje6H6c7BBpd7NS2+vG9ksZi6/DGL A5PHkiU/mTxWnJ/JEsAUxWWTkpqTWZZapG+XwJXx599+loK7/BX7p75maWC8x9PFyMkhIWAi MeHmKVYIW0ziwr31bF2MXBxCAicZJQ7c2MgK4SxmlJh5cw5TFyMHB5uAhUT3P22QBhGBWInG qdvZQWxhAVWJSS/PsUPE1SSOzT/FAmEbSTRf+Aa2gEVARaL910pGEJtXwFfi+e9mNhBbSEBb ouHoabAaTgEdiX8XToLZjEAHfT+1hgnEZhYQl7j1ZD4TxKECEkv2nGeGsEUlXj7+B/WAosTO s+3MEPU6Egt2f2KDsLUlli18zQyxV1Di5MwnLBMYRWchGTsLScssJC2zkLQsYGRZxShZnFqc lJtuZKiXm55bopdalJlcXJyfp1ecuokRGC8Ht/w23ME48Zr9IUZpDhYlcV6G6Z1BQgLpiSWp 2ampBalF8UWlOanFhxiZODilGhh3650UPPvF1fC53iOL8Gp1OQUtvYnLVwde3O0grX5MSXrC vbTzL1eaHS261bLm/lkpxvz1e5f8yEvJu/V+1ppvV2RLHCYfnPh21cWrizUjPr+5tuXOznLz 8n7rHMuGP2HzXS5c2L/jl8WtDwv/P+122ZIe6rWNo+WUZb5Xweae3a8eVl701pVUVmIpzkg0 1GIuKk4EAGIohAplAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/P0HCbzj9BjQ9QEpDAi5p0DOIy8M
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: Tue, 08 Apr 2014 06:32:27 -0000

Hi,

In the example below, SCTP is running on top of DTLS, and BUNDLE does describe how to distinguish between DTLS and (S)RTP.

Now, if you run multiple SCTP associations on top of that DTLS connection, you would use the SCTP port number to distinguish them.

The general agreement has been that we, within the BUNDLE draft, describe what is needed for RTCWEB (the main "customer" for BUNDLE at the moment), but that we allow extensibility.

Regards,

Christer

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christian Groves
Sent: 8. huhtikuuta 2014 7:15
To: mmusic mailing list
Subject: [MMUSIC] BUNDLE and SCTP

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

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic

v2.23.0 | Report a Bug | By Email