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

Christian Groves <Christian.Groves@nteczone.com> Wed, 01 October 2014 23:57 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 460E01A886E for <mmusic@ietfa.amsl.com>; Wed, 1 Oct 2014 16:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level:
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 6diRNZ1SDbrN for <mmusic@ietfa.amsl.com>; Wed, 1 Oct 2014 16:57:09 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 002F41A886C for <mmusic@ietf.org>; Wed, 1 Oct 2014 16:57:08 -0700 (PDT)
Received: from ppp118-209-169-149.lns20.mel8.internode.on.net ([118.209.169.149]:52174 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 1XZTk3-0005Lo-Pe for mmusic@ietf.org; Thu, 02 Oct 2014 09:55:31 +1000
Message-ID: <542C94CE.50600@nteczone.com>
Date: Thu, 02 Oct 2014 09:57:02 +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.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
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>
In-Reply-To: <542C0C31.70506@alum.mit.edu>
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/o6kIh5Bb5u65w-P0sg3JW3Ik-SI
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: Wed, 01 Oct 2014 23:57:10 -0000

What is the status of the draft-ejzak-mmusic-data-channel-sdpneg-00?

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
>