Re: [MMUSIC] updating draft-ietf-mmusic-sctp-sdp

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 10 October 2012 20:48 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59DA121F8543 for <mmusic@ietfa.amsl.com>; Wed, 10 Oct 2012 13:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.382
X-Spam-Level:
X-Spam-Status: No, score=-0.382 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xe611zjih4p0 for <mmusic@ietfa.amsl.com>; Wed, 10 Oct 2012 13:48:38 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id C949521F853B for <mmusic@ietf.org>; Wed, 10 Oct 2012 13:48:37 -0700 (PDT)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta15.westchester.pa.mail.comcast.net with comcast id 9Pct1k0081HzFnQ5FYp6RQ; Wed, 10 Oct 2012 20:49:06 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta14.westchester.pa.mail.comcast.net with comcast id 9Yjh1k00f3ZTu2S3aYjhxp; Wed, 10 Oct 2012 20:43:41 +0000
Message-ID: <5075DDF8.5070200@alum.mit.edu>
Date: Wed, 10 Oct 2012 16:43:36 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: mmusic@ietf.org
References: <50728B01.5060405@ericsson.com>
In-Reply-To: <50728B01.5060405@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [MMUSIC] updating draft-ietf-mmusic-sctp-sdp
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Oct 2012 20:48:38 -0000

Salvatore,

Comment/question inline

On 10/8/12 4:12 AM, Salvatore Loreto wrote:
> Hi there,
>
> there has been a quite large discussion within the rtcweb mailing list and
> especially the w3c webrtc mailing list.
>
> Some of the points discussed are specific of how to negotiate the
> 'datachannel' protocol over SDP,
> and I lean on putting those in a separate draft and not in this one.
>
> However there are things that are general enough to is worth to insert
> in this draft
> as they can be used in other protocols that eventually will be specified
> in the future
> running on top of SCTP, or STCP over DTLS.
>
>   'streams' is some of those attributes,
>   so I am proposing to insert in the new version of the draft the
> following text
>
>   xxx.  Streams Attribute
>
>     The 'streams' attribute indicates time the number of streams to be supported by the association.
>     If this attribute is not present, the implementation should provide a default, with a suggested value
>     of 16.
>
>
>           streams-attr           =  "a=streams:" streamsnumbers
>           streamsnumbers         =1*DIGIT
>
>
> As I said, all the other attributes that has been discussed are tied to
> the 'datachannel'  protocol identifier ( to be registered?),
> which is describing the format of the media... so they should go in a
> different draft.

I'm confused by the above. The m-line syntax is:

     m=<media> <port> <proto> <fmt> ...

and this draft is defining SCTP, SCTP/DTLS and DTLS/SCTP values for 
<proto>. Are you suggesting that "datachannel" be defined (in a 
different draft) as an alternative to *these* values? I would think it 
would make more sense to define "datachannel" as a <fmt> value.

That brings up another issue:

According to 4566, the values of the <fmt> field are protocol specific. 
That means that *this* draft needs to specify how <fmt> values are to be 
understood for sctp. That is actually a problem, one might want 
different fmt semantics for each channel.

I have more to say, but I'll start another thread for that.

	Thanks,
	Paul