IETF Logo Mail Archive

Re: [clue] FW: draft-ejzak-mmusic-data-channel-sdpneg and DCEP

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 25 November 2014 18:42 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B5061ACECA for <clue@ietfa.amsl.com>; Tue, 25 Nov 2014 10:42:52 -0800 (PST)
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 6rJ0p4I1BwHn for <clue@ietfa.amsl.com>; Tue, 25 Nov 2014 10:42:51 -0800 (PST)
Received: from resqmta-po-07v.sys.comcast.net (resqmta-po-07v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:166]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08C4E1A871A for <clue@ietf.org>; Tue, 25 Nov 2014 10:42:50 -0800 (PST)
Received: from resomta-po-16v.sys.comcast.net ([96.114.154.240]) by resqmta-po-07v.sys.comcast.net with comcast id KueA1p00J5BUCh401uipy0; Tue, 25 Nov 2014 18:42:49 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-16v.sys.comcast.net with comcast id Kuio1p00j3Ge9ey01uipM4; Tue, 25 Nov 2014 18:42:49 +0000
Message-ID: <5474CDA8.8030004@alum.mit.edu>
Date: Tue, 25 Nov 2014 13:42:48 -0500
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: clue@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D52ED2E@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D52ED53@ESESSMB209.ericsson.se>, <5472781B.1050209@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D5324F3@ESESSMB209.ericsson.se> <5473BE59.4070805@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D53548A@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E63B9DA@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D53577E@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E63BB87@US70UWXCHMBA02.zam.alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17828E63BB87@US70UWXCHMBA02.zam.alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1416940969; bh=SYp9l4Lry7Uu6eOvzeswYpMcDiloGyKrk6zn/aRvFWA=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=pHPUeC0bTbL/nrzfEKjKQ6QILXgtF7p1YDkAMTTEPqt+khGf6zeqsBiucyC4E6IuB 7jSWvhb/TvWQ02/62ryvzm7sA+x6rWcvbgkYcyFRmxZPm1gV1UxArSzzcUrUbd5+le 3sE5u4ns2XX8MXIQEF9oGspRVMFpisRgJMOM4Q2NkACkV5g89sikQUrtf9g31fW16Q 7NzykslaGW+TG23pYjXTOSM7lLjcOlJZiI9eyVwjhkHfyQ9I1GfCWK9gyTCZsUEbP5 2eo88uyM9InB9B8ohL6korGmhg2IdTBtOTVVgXknk2uLxRjBU45fmbjVH8AnUN5ltB ig4bfmRh7tW5Q==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/1bB1yNe-dcOIIL7YSM1A1Nxs4Qw
Subject: Re: [clue] FW: draft-ejzak-mmusic-data-channel-sdpneg and DCEP
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Nov 2014 18:42:52 -0000

On 11/25/14 7:00 AM, Makaraju, Maridi Raju (Raju) wrote:
>
>> Hi,
>>
>>>> If you provide the SCTP port in the WebRTC API, then DCEP won't be used.
>>> You meant "(stream) id" instead of "SCTP port"?
>>
>> Yes.
>>
>>> In WebRTC API createDataChannel(), use of DCEP is controlled by using
>> "negotiated" parameter. (Stream) id specification only determines the stream
>> id to be used.
>>
>> Ok. But, the point is that you can create a data channel without DCEP.
> [Raju]
> IMHO, I am in favor of not mandating DCEP for non-WebRTC device CLUE usage. Furthermore, to be consistent it may be better not to use DCEP even when CLUE is used by a WebRTC device.

If we mandate using draft-ejzak for establishing the clue channel, then 
DCEP won't be *used*. I think we simply make a requirement for support 
of draft-ietf-rtcweb-data-channel, and don't mention 
draft-ietf-rtcweb-data-protocol. If there are dependencies between those 
two, then that is not our problem. (I thought data-channel had a 
dependency on data-protocol, but I don't see it now, which is a good thing.)

	Thanks,
	Paul

> BR
> Raju
>
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>>> -----Original Message-----
>>> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christer
>>> Holmberg
>>> Sent: Tuesday, November 25, 2014 5:24 AM
>>> To: Christian Groves; clue@ietf.org
>>> Subject: Re: [clue] FW: draft-ejzak-mmusic-data-channel-sdpneg and
>>> DCEP
>>>
>>> Hi,
>>>
>>> If I understood Paul's comment, DCEP is not required for compatibility
>>> with WebRTC endpoints. If you provide the SCTP port in the WebRTC API,
>>> then DCEP won't be used.
>>>
>>> The question is really whether we want to mandate non-WebRTC CLUE
>>> devices to implement DCEP or not.
>>>
>>> Regards,
>>>
>>> Christer
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>

v2.23.0 | Report a Bug | By Email