IETF Logo Mail Archive

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

"Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com> Tue, 25 November 2014 12:00 UTC

Return-Path: <Raju.Makaraju@alcatel-lucent.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 A386B1A0104 for <clue@ietfa.amsl.com>; Tue, 25 Nov 2014 04:00:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 w_4vE9AfLT07 for <clue@ietfa.amsl.com>; Tue, 25 Nov 2014 04:00:12 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F127A1A00F9 for <clue@ietf.org>; Tue, 25 Nov 2014 04:00:11 -0800 (PST)
Received: from us70uusmtp3.zam.alcatel-lucent.com (unknown [135.5.2.65]) by Websense Email Security Gateway with ESMTPS id 706C0B314400B; Tue, 25 Nov 2014 12:00:07 +0000 (GMT)
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com [135.5.2.48]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id sAPC08Gi030680 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 25 Nov 2014 07:00:08 -0500
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.56]) by US70UWXCHHUB01.zam.alcatel-lucent.com ([135.5.2.48]) with mapi id 14.03.0195.001; Tue, 25 Nov 2014 07:00:08 -0500
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Christian Groves <Christian.Groves@nteczone.com>, "clue@ietf.org" <clue@ietf.org>
Thread-Topic: [clue] FW: draft-ejzak-mmusic-data-channel-sdpneg and DCEP
Thread-Index: AdAFv0DSisjv6UE4T7mZyJHhbq+IHwBvENaOAA9cNwAAK7ZTgAAZGO8AAAoBUID//7aNAIAAUXvw
Date: Tue, 25 Nov 2014 12:00:07 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17828E63BB87@US70UWXCHMBA02.zam.alcatel-lucent.com>
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>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D53577E@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.17]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/IdKEkGXo73PnQNtIZR1draoCM3c
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 12:00:13 -0000

> 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.

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

v2.23.0 | Report a Bug | By Email