Re: [rtcweb] *MUST* DCEP?

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 04 March 2014 15:00 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 145771A017B for <rtcweb@ietfa.amsl.com>; Tue, 4 Mar 2014 07:00:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level:
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_17=0.6, 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 R6jyA_YjZyy4 for <rtcweb@ietfa.amsl.com>; Tue, 4 Mar 2014 07:00:49 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5551A00F1 for <rtcweb@ietf.org>; Tue, 4 Mar 2014 07:00:49 -0800 (PST)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta12.westchester.pa.mail.comcast.net with comcast id ZRVr1n00427AodY5CT0m0t; Tue, 04 Mar 2014 15:00:46 +0000
Received: from dhcp-a663.meeting.ietf.org ([31.133.166.99]) by omta19.westchester.pa.mail.comcast.net with comcast id ZSyZ1n00A2904qf3fSybQH; Tue, 04 Mar 2014 14:58:44 +0000
Message-ID: <5315EA19.90401@alum.mit.edu>
Date: Tue, 04 Mar 2014 14:58:33 +0000
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.3.0
MIME-Version: 1.0
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>, Ted Hardie <ted.ietf@gmail.com>
References: <5315B2E8.7010703@alum.mit.edu> <CA+9kkMAstUJHgMNRHE1EokqnNhyX0W+YPKvq7_=Miq4+Tbi5aw@mail.gmail.com> <E1FE4C082A89A246A11D7F32A95A17826E0069CB@US70UWXCHMBA02.zam.alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17826E0069CB@US70UWXCHMBA02.zam.alcatel-lucent.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=q20121106; t=1393945246; bh=A0QlVw6glIfMvbHbNtU2YkIie7DChjJbxrG8sWWPv2o=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=NYbhazXg78lpMvEChEafbvV+nc0N0jOY3ZwnvuLivCHqmPgGCpPfjbBgUo1zW9as5 B0CvsLfc9SYMf23/gycQ3NbD2omGI6GZvDOOhlo4k8yIxGpsJQuMRRkeUbcFzAA950 qIL4WKPldNaOB1fvobyf0oS+nFuRINV8X/f5w7U1QwSQq/Ta9bM+Pehhr+hDWpKfma KyQDkew9emX8dnLn5tdBNW3OpTWkUp8ix+h+NNeq/wDh66EljsBJISmHl6vp6pvade 16iD0JnZJ7FyVFoWmM0YuM8kTu5J1oMwlujwlGwjGbwf+d3A6Kl3Ts0IILqzakO9zp +0WJTkELt2SYw==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/rqBtxjHV51JcPn-c__L35is-gpQ
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] *MUST* DCEP?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Mar 2014 15:00:51 -0000

On 3/4/14 12:08 PM, Makaraju, Maridi Raju (Raju) wrote:
> While a=sctpmap assumes use of DCEP, indication of external negotiation
> (instead of DCEP) also requires subprotocol and it’s parameters to be
> conveyed. This has to be done per data channel stream.
>
> Are you looking at more than what is documented in
> [I-D.ejzak-mmusic-data-channel-sdpneg]?
>
> Or are you looking for an indication of this (for all streams) directly
> in a=sctpmap?

I'm ok as things currently stand, though the documents are confusing.
The 'a=sctpmap:nnn websocket-datachannel' means that DCEP is supported.

My concern was a proposal I think I heard that would make support for 
DCEP to be optional. In that case, IMO it is important that the O/A 
exchange establish whether DCEP is supported or not.

	Thanks,
	Paul

> How about item 3 of the following proposal?
>
> http://www.ietf.org/mail-archive/web/mmusic/current/msg13155.html
>
> -Raju
>
> *From:*rtcweb [mailto:rtcweb-bounces@ietf.org] *On Behalf Of *Ted Hardie
> *Sent:* Tuesday, March 04, 2014 5:17 AM
> *To:* Paul Kyzivat
> *Cc:* rtcweb@ietf.org
> *Subject:* Re: [rtcweb] *MUST* DCEP?
>
> On Tue, Mar 4, 2014 at 11:03 AM, Paul Kyzivat <pkyzivat@alum.mit.edu
> <mailto:pkyzivat@alum.mit.edu>> wrote:
>
>     Ted,
>
>     (I think this was open issue #8)
>
>     You closed discussion on this, saying that this should be specified
>     in some rtcweb "system" document. IIUC, then I disagree.
>
>     This is important to others besides rtcweb. We want to use this
>     mechanism, both with and without components that are implementing
>     rtcweb. Certainly for non-browsers.
>
> Help me understand why it wouldn't then be in their systems documents?
>
> Ted
>
>
>
>     This ultimately comes down to what I can expect after having
>     negotiated (in SDP) the establishment of an SCTP association. When
>     doing so, I use a=sctpmap to negotiate the how the association will
>     be used. If I intend to use data channels and DCEP then I want an
>     assurance that the other end does too. (That is the purpose of the
>     SDP negotiation.)
>
>     AFAIK, current when I specify 'a=sctpmap:webrtc-datachannel' (or
>     'a=sctp-datachannel' depending on where I look), that means the
>     other side supports data channels *and* guarantees support for DCEP.
>     There is no means to indicate support for data channels *without* DCEP.
>
>     I don't see any urgent need to have data channels without DCEP, as
>     long as *use* of DCEP is optional.
>
>     IMO things would be less confusing if the two documents were merged
>     into one, that defines the *Data Channel Protocol* (that runs over
>     SCTP). This protocol runs over pairs of SCTP streams, has a small
>     number of messages (open, ack, string-payload, binary-payload,
>     close), and encodes them in SCTP using SCTP messages with particular
>     payloads and SCTP stream reset. The open and ack messages would be
>     optional.
>
>              Thanks,
>              Paul
>