IETF Logo Mail Archive

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

Christian Groves <Christian.Groves@nteczone.com> Wed, 26 November 2014 00:20 UTC

Return-Path: <Christian.Groves@nteczone.com>
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 D18701A89B3 for <clue@ietfa.amsl.com>; Tue, 25 Nov 2014 16:20:41 -0800 (PST)
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 HWOyFSUuAtBy for <clue@ietfa.amsl.com>; Tue, 25 Nov 2014 16:20:39 -0800 (PST)
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 5A5A81A89A6 for <clue@ietf.org>; Tue, 25 Nov 2014 16:20:39 -0800 (PST)
Received: from ppp118-209-10-178.lns20.mel4.internode.on.net ([118.209.10.178]:52590 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <Christian.Groves@nteczone.com>) id 1XtQKL-0000BR-M6 for clue@ietf.org; Wed, 26 Nov 2014 11:19:25 +1100
Message-ID: <54751CD0.2070805@nteczone.com>
Date: Wed, 26 Nov 2014 11:20:32 +1100
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: 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>, <5474CDA8.8030004@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D5366AB@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D5366AB@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="UTF-8"; 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/clue/6SpXSdaVmIr873RDlLwdaVEB1kg
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: Wed, 26 Nov 2014 00:20:42 -0000

I'm OK with dropping DCEP. It could be worth keeping the DCEP code point 
as you say for non-O/A environment.

Regards, Christian

On 26/11/2014 6:17 AM, Christer Holmberg wrote:
> Hi,
>
> I agree with Paul.
>
> But, the question is still whether the CLUE data channel spec ahould 
> still define the DCEP code point for the CLUE data channel, IF someone 
> e.g. want to specify usage of CLUE in a non-O/A environment.
>
> Regards,
>
> Christer
>
> Sent from my Windows Phone
> ------------------------------------------------------------------------
> From: Paul Kyzivat <mailto:pkyzivat@alum.mit.edu>
> Sent: ‎25/‎11/‎2014 20:43
> To: clue@ietf.org <mailto:clue@ietf.org>
> Subject: Re: [clue] FW: draft-ejzak-mmusic-data-channel-sdpneg and DCEP
>
> 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
> >
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue

v2.23.0 | Report a Bug | By Email