Re: [MMUSIC] draft-ietf-mmusic-sctp-sdp-07 SCTP SDP syntax question

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 02 October 2014 12:00 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 E30151A1ABA for <mmusic@ietfa.amsl.com>; Thu, 2 Oct 2014 05:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Level:
X-Spam-Status: No, score=-3.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_111=0.6, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 phVEjcw4U4SS for <mmusic@ietfa.amsl.com>; Thu, 2 Oct 2014 04:59:59 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD3171A031C for <mmusic@ietf.org>; Thu, 2 Oct 2014 04:59:54 -0700 (PDT)
X-AuditID: c1b4fb30-f79736d0000053b8-a1-542d3e387a98
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 69.F2.21432.83E3D245; Thu, 2 Oct 2014 13:59:53 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0174.001; Thu, 2 Oct 2014 13:59:52 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] draft-ietf-mmusic-sctp-sdp-07 SCTP SDP syntax question
Thread-Index: AQHP3Kfo2bDak4IaK0OoRO9p0kjlCJwZfrEAgAE5WgCAAARMgIAAbMGAgACi2wCAABvpAIAAzvdA
Date: Thu, 2 Oct 2014 11:59:51 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D4637E9@ESESSMB209.ericsson.se>
References: <542A9E4B.2050608@nteczone.com> <542AA680.1030809@nteczone.com> <2AB21794-B955-48A3-ACC1-B0D838354BFA@ericsson.com> <542BB0F7.3090608@nteczone.com> <542C0C31.70506@alum.mit.edu> <542C94CE.50600@nteczone.com> <542CAC38.5020708@alum.mit.edu>
In-Reply-To: <542CAC38.5020708@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrLLMWRmVeSWpSXmKPExsUyM+Jvja6lnW6IwfyXfBZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJVx8MtL9oLXEhWTNnI1ME4Q6WLk4JAQMJG4 /kOui5ETyBSTuHBvPVsXIxeHkMBRRom3PXPZIZzFjBLNey4wgjSwCVhIdP/TBmkQEfCVePb4 NhuILSzgI/Hn5EN2mPiq3qtg5SICURJPbtuChFkEVCRWnL/BAmLzApVMW9/KDDG+kUniw6mT rCD1nAI6EhteRIDUMALd8/3UGiYQm1lAXOLWk/lMEHcKSCzZc54ZwhaVePn4HyvEK0oS07am QZTrSCzY/YkNwtaWWLbwNTPEWkGJkzOfsExgFJ2FZOosJC2zkLTMQtKygJFlFaNocWpxUm66 kZFealFmcnFxfp5eXmrJJkZgfBzc8ttgB+PL546HGAU4GJV4eBds1AkRYk0sK67MPcQozcGi JM678Ny8YCGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2MXdez+a+6G3ndW2bH0n596iWbnRf2 1pmsey2+MPjO2fs+bSrnTznlRbjFySaYh2g23auMNKprf//qtPBtw8XFQW8yE6b36fJHLdp2 +l13RI3k8WonAQWxkJPlH+Wes/FIZybZW2oKqfMtmiq6tX+rwnbDDX+e33x9gvX0Wb+CbL3V lc6qa/uUWIozEg21mIuKEwEW7iltcAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/O8589YmAVhNDwqPnUWTDpdXSI6k
Subject: Re: [MMUSIC] draft-ietf-mmusic-sctp-sdp-07 SCTP SDP syntax question
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: Thu, 02 Oct 2014 12:00:03 -0000

Hi,

Keep in mind that the purpose of draft-ejzak-mmusic-data-channel-sdpneg is NOT to negotiate the usage of the SCTP association.

It is assumed that the usage of the SCTP association is data channel, and the draft defines a mechanism to negotiate data channels on that SCTP association.

Regards,

Christer





-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Paul Kyzivat
Sent: 2. lokakuuta 2014 4:37
To: mmusic@ietf.org
Subject: Re: [MMUSIC] draft-ietf-mmusic-sctp-sdp-07 SCTP SDP syntax question

On 10/1/14 7:57 PM, Christian Groves wrote:
> What is the status of the draft-ejzak-mmusic-data-channel-sdpneg-00?

I don't know the status. The thought Keith Drage had indicated that he was picking up responsibility for it.

	Thanks,
	Paul

> It has expired and is based on the old SDP SCTP syntax. Particularly 
> the example in cl.4:
>
>     m=application 54111 DTLS/SCTP 5000 5001 5002
>     c=IN IP4 79.97.215.79
>     a=sctpmap:5000 webrtc-datachannel
>     a=sctpmap:5001 bfcp
>     a=sctpmap:5002 t38
>
> Wouldn't apply if we're saying to use multiple m-lines.
>
> I guess cl.5.1.1.3 would use the same Websocket subprotocol name 
> registry as data channel does?
>
> Regards, Christian
>
> On 2/10/2014 12:14 AM, Paul Kyzivat wrote:
>> On 10/1/14 3:44 AM, Christian Groves wrote:
>>
>>>> <Sal>
>>>> there have been several discussion about the ability to have more 
>>>> than one usage of the SCTP association, and has been agreed not to 
>>>> allow it.
>>>> So each 'm' line describes a single SCTP association;  each 
>>>> association has only one single specify usage.
>>>> </Sal>
>>>
>>> [CNG] So how would I specify in SDP a scenario where BFCP uses a 
>>> DTLS/SCTP association and MSRP uses a DTLS/SCTP association where 
>>> they both use the same DTLS connection? Are these to be separate m-lines?
>>
>> To have two different SCTP associations over the same DTLS 
>> connection, they would have to be distinguished by sctp-port. To 
>> achieve that you could write two m-lines. They would share the same 
>> ip address and port, and would have different "a=sctp-port" lines. 
>> Then they would have to be bundled.
>>
>> Doing that would require extending the definition of bundle to cover 
>> that case. (There is no *technical* problem in doing this.)
>>
>> OTOH, in principle they don't need their own SCTP association. AFAIK 
>> they each only use one sctp stream-pair (channel). If they could 
>> agree on how to choose channels then they could share an SCTP association.
>> That is where draft-ejzak... comes in.
>>
>>     Thanks,
>>     Paul
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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