IETF Logo Mail Archive

Re: [clue] Comment on the signalling draft

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 21 March 2014 05:17 UTC

Return-Path: <christer.holmberg@ericsson.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 7C9C01A08D3 for <clue@ietfa.amsl.com>; Thu, 20 Mar 2014 22:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level:
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 Isy39siA3Q6T for <clue@ietfa.amsl.com>; Thu, 20 Mar 2014 22:17:08 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 282E11A08F9 for <clue@ietf.org>; Thu, 20 Mar 2014 22:17:07 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-15-532bcb452dd5
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 15.A0.10875.54BCB235; Fri, 21 Mar 2014 06:16:53 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.02.0387.000; Fri, 21 Mar 2014 06:16:52 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christian Groves <Christian.Groves@nteczone.com>, "clue@ietf.org" <clue@ietf.org>
Thread-Topic: [clue] Comment on the signalling draft
Thread-Index: AQHPRKcZyUqPI+G92kKOR/5zycd9aZrrADr9
Date: Fri, 21 Mar 2014 05:16:52 +0000
Message-ID: <ghkl4mb80w6x4clwqpsrigk1.1395379009787@email.android.com>
References: <532B996F.4060500@nteczone.com>
In-Reply-To: <532B996F.4060500@nteczone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM+Jvja7nae1gg4k7TSy+vG9ksdh/6jKz A5PHkiU/mTxWnJ/JEsAUxWWTkpqTWZZapG+XwJVx7rxWwQ7BisW9bxgbGDv5uhg5OSQETCSu dk5jgrDFJC7cW8/WxcjFISRwiFHiwa8fLBDOEkaJO4+bGbsYOTjYBCwkuv9pgzSICIRLdGy7 wghiCwsYSzS+msAOETeRmD+3F8o2kljydiUziM0ioCpxdMMVVhCbV8BN4vGRQ2A1QgLaEp9+ zASLcwroSKzYtARsJiPQQd9PrQE7jllAXOLWk/lQhwpILNlznhnCFpV4+fgfK0SNjsSC3Z/Y IGxtiWULXzND7BKUODnzCcsERpFZSEbNQtIyC0nLLCQtCxhZVjGy5yZm5qSXG25iBAb8wS2/ dXcwnjoncohRmoNFSZz3w1vnICGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2MjvncZpP2L91l 63d8ntYRy5fP9qar5K7hc3ugeNluWtP19eXZOZ01USulYiubXu3lP7/u/oQ8ht16aRWHDkds WTQ13pNfvsvToP6rAauceCMH9+mbiVtD/v95+fXMrOULHgesEPTzaTQSnpfuVcqZvJ0/cssS npD9B/U3CeXqbb+3OYHjipiqEktxRqKhFnNRcSIAj4A1t0YCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/iiMkwiHD-L43KBtpSqfr9Suo1Y8
Subject: Re: [clue] Comment on the signalling draft
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: Fri, 21 Mar 2014 05:17:10 -0000

Hi Christian,

I assume the signalling draft will simply reference the clue-datachannel draft in future versions.

Regards,

Christer

Sent from my Sony Ericsson Xperia arc S

Christian Groves <Christian.Groves@nteczone.com> wrote:


With respect to clause 3.4/draft-kyzivat-clue-signaling:

A CLUE-enabled device that receives an initial SDP offer from a non-
    CLUE device with no CLUE data channel "m" line SHOULD include a new
    data channel "m" line in any subsequent offers it sends, to indicate
    that it is CLUE-enabled.

I think this is incorrect. The use of a m=line with DTLS/SCTP and a
SCTPmap=WebRTC data channel only means that the device supports the data
channel protocol. It does not mean indicate that the device is
CLUE-enabled. Knowing that an endpoint wants to use CLUE only occurs
when the data channel protocol is used to open a SCTP stream.

I think this is also a problem in section 3.1. A CLUE data channel is
defined as: "CLUE Data Channel refers to a WebRTC Data Channel
    [I-D.ietf-rtcweb-data-channel], with a specific set of SCTP
    characteristics, and usage of the Data Channel Establishment Protocol
    (DCEP) [I-D.ietf-rtcweb-data-protocol] in order to open a WebRTC Data
    Channel for the purpose of transporting CLUE protocol
    [I-D.presta-clue-protocol] messages between two CLUE entities."

You cannot have the presence of the "CLUE data channel" in an SDP offer
or answer because the "CLUE data channel" is a SET of characteristics
including the DCEP (which is generic in a SCTPmap). You only know what
it is for when an endpoint tries to do a DCEP open. All that the SDP
offer/answer says with m= DTLS/SCTP and SCTPMAP=WebRTC datachannel is
that the device wants to establish a DTLS/SCTP association with DCEP. It
could use DCEP to establish protocol: "foo", "bar" or "CLUE". The
association could be used for anything.

Of course the above is not an issue if
draft-ejzak-mmusic-data-channel-sdpneg is used but my understanding this
is not in scope of the draft.

Regards, Christian




_______________________________________________
clue mailing list
clue@ietf.org
https://www.ietf.org/mailman/listinfo/clue

v2.23.0 | Report a Bug | By Email