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

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 01 October 2014 14:20 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 2E62F1ACDC4 for <mmusic@ietfa.amsl.com>; Wed, 1 Oct 2014 07:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 CrqlM7UQmksD for <mmusic@ietfa.amsl.com>; Wed, 1 Oct 2014 07:20:19 -0700 (PDT)
Received: from resqmta-po-02v.sys.comcast.net (resqmta-po-02v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:161]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07D4D1ACDC2 for <mmusic@ietf.org>; Wed, 1 Oct 2014 07:20:18 -0700 (PDT)
Received: from resomta-po-19v.sys.comcast.net ([96.114.154.243]) by resqmta-po-02v.sys.comcast.net with comcast id xqJP1o0035FMDhs01qLJTp; Wed, 01 Oct 2014 14:20:18 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-19v.sys.comcast.net with comcast id xqLH1o00c3Ge9ey01qLJso; Wed, 01 Oct 2014 14:20:18 +0000
Message-ID: <542C0DA1.4000903@alum.mit.edu>
Date: Wed, 01 Oct 2014 10:20:17 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; 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>
In-Reply-To: <2AB21794-B955-48A3-ACC1-B0D838354BFA@ericsson.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1412173218; bh=/lU4OWE+HBTC1L+sU1zj1+U5/p4jvZk5bQRAIVMokg0=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=PDS97d7/h2/RnFzlLznXY1tRkOw/VRfDAaxDYIqzBWHOHm3VUxvQDaYTGEe5Hmsxx JTQ8hjFS7BhOMp1qgNlGcD2SVJ61i6epP+oI4wJ3vzAllzGoUVxIS3v2abSETWnvj5 wpftY52PI+rNNta7yjrbFWerqXln/lfy0rBCBG1VlGZobaJDNmCBuwLczkDewXNFEf 8vpbGL6eeh83Wp1tpwIBgNG3Tw/jqshf5Fm+Q3hYOlGRW4+W9fZETlum5tOdrNFC6s Kr3qmtKp0V5fjmMeWajLV4d+SM6hA98pJitIfbJfxdj7vfXysdp9vtVrpYRZEhVFG4 zO67fSW1nB/0A==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ZPTz6F6nhFWhB2Ojtz9Ron5fi9Q
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 14:20:20 -0000

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.

	Thanks,
	Paul