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

Christian Groves <Christian.Groves@nteczone.com> Wed, 01 October 2014 23:24 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 AE1191A8835 for <mmusic@ietfa.amsl.com>; Wed, 1 Oct 2014 16:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 0-747AeydotE for <mmusic@ietfa.amsl.com>; Wed, 1 Oct 2014 16:24:51 -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 511731A8830 for <mmusic@ietf.org>; Wed, 1 Oct 2014 16:24:51 -0700 (PDT)
Received: from ppp118-209-169-149.lns20.mel8.internode.on.net ([118.209.169.149]:51553 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 1XZTEo-0000O9-LC for mmusic@ietf.org; Thu, 02 Oct 2014 09:23:14 +1000
Message-ID: <542C8D3C.7070105@nteczone.com>
Date: Thu, 02 Oct 2014 09:24:44 +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> <542C0DA1.4000903@alum.mit.edu>
In-Reply-To: <542C0DA1.4000903@alum.mit.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
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/pVJqzBbf-UPEYZZSMreQIvXygyk
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:24:53 -0000

Hello,

On 2/10/2014 12:20 AM, Paul Kyzivat wrote:
> On 10/1/14 3:29 AM, Salvatore Loreto wrote:
>
>>>> 7) Cl.10: How will this registry relate to the “WebSocket 
>>>> Subprotocol Name Registry” 
>>>> (http://www.iana.org/assignments/websocket/websocket.xml#subprotocol-name)?
>>
>> <Sal>
>> It is not related. The 'association-usage' specifies how the SCTP 
>> association will be used.
>> For example in the case of webrtc-datachannel value it would indicate 
>> how to pair certain streams,
>> how to consider specific stream etc.
>> as described in 
>> https://tools.ietf.org/html/draft-ietf-rtcweb-data-protocol-08 and in
>> http://tools.ietf.org/wg/rtcweb/draft-ietf-rtcweb-data-channel/
>>
>> the WebSocket Subprotocol Name Registry is used to populate the 
>> protocol field in the
>> protocol field in 
>> https://tools.ietf.org/html/draft-ietf-rtcweb-data-protocol-08#section-5
>
> I agree.
>
> The association-usage is describing how the association as a whole, 
> including all of the streams, is used/managed.
>
> It doesn't provide a means to separately describe how individual 
> streams within it are to be used. If that is to be done in SDP then 
> something like draft-ejzak... would be required.

[CNG] My comments on this are in the context of the note in cl.10 of the 
draft: "[Note] TBD whether a new registry is necessary to register the 
different possible "association-usage" values."

I'm just thinking of the specification effort to introduce new 
sub-protocols. Consider a gateway scenario where I have a DTLS/SCTP 
association running datachannel with bfcp and on the other side a SCTP 
association running BFCP. In either scenario bfcp runs in an SCTP 
stream. However it means to introduce BFCP (and any other protocol) we 
have to update two registries with essentially the same value.

If we do have a new registry just for "association-usage" it would be 
good to have some text with regards to a template of information that 
someone registering the information would need to consider. i.e. what 
information would someone need to specify to registry BFCP as opposed to 
just registering BFCP as websocket sub-protocol.

Regards, Christian


>
>     Thanks,
>     Paul
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>