IETF Logo Mail Archive

Re: [rtcweb] RTCWEB data channel protocol: Mandated to use?

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 29 January 2014 10:18 UTC

Return-Path: <christer.holmberg@ericsson.com>
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 97B1B1A0229 for <rtcweb@ietfa.amsl.com>; Wed, 29 Jan 2014 02:18:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level:
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] 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 0jAdqSc9XV-A for <rtcweb@ietfa.amsl.com>; Wed, 29 Jan 2014 02:18:55 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id AEBCB1A01BC for <rtcweb@ietf.org>; Wed, 29 Jan 2014 02:18:54 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-e5-52e8d589252d
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 4F.FD.04853.985D8E25; Wed, 29 Jan 2014 11:18:50 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.02.0387.000; Wed, 29 Jan 2014 11:18:49 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Peter Thatcher <pthatcher@google.com>, Harald Alvestrand <harald@alvestrand.no>
Thread-Topic: [rtcweb] RTCWEB data channel protocol: Mandated to use?
Thread-Index: Ac8cAngQ5gMoLtdxSK+NK5iG67ycPgANZFsAAAw8E4AAHJuukA==
Date: Wed, 29 Jan 2014 10:18:48 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D149077@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D143FB4@ESESSMB209.ericsson.se> <52E7D15A.4090805@alvestrand.no> <CAJrXDUFGv3oRJxK31afrm-8tieyh=sKYU_KTn=jeFvY06_QA8A@mail.gmail.com>
In-Reply-To: <CAJrXDUFGv3oRJxK31afrm-8tieyh=sKYU_KTn=jeFvY06_QA8A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOLMWRmVeSWpSXmKPExsUyM+JvjW7X1RdBBr8vM1kc6+tis7i2/DWr xdp/7ewOzB5XJlxh9ViwqdRjyZKfTAHMUVw2Kak5mWWpRfp2CVwZs2bfZS7oEap4v7CPuYHx Kl8XIyeHhICJxPvVi1ghbDGJC/fWs3UxcnEICZxglFjw4jk7hLOYUWLR9KcsXYwcHGwCFhLd /7RBGkQEQiUeT2sCa2YW0JSYsGwXG4gtLOAicevjFxaIGleJ378bWCFsJ4nNk/Yyg9gsAqoS W/4+AqvhFfCV2LJ3JdTi7YwSn7fPA2vgFAiUODtzGyOIzQh03fdTa5gglolL3HoynwniagGJ JXvOM0PYohIvH/9jBblTQkBJYtrWNIhyHYkFuz+xQdjaEssWvmaG2CsocXLmE5YJjGKzkEyd haRlFpKWWUhaFjCyrGKULE4tLs5NNzLQy03PLdFLLcpMLi7Oz9MrTt3ECIysg1t+G+1gPLnH /hCjNAeLkjjvddaaICGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2M/Zs/LWfannlZPYHT53/n 56Q49pYVXZ/m5X7MnLb11IWnezovt5dekK2/+qVxY8HDmc3P926+zPzm9mWR/4wn/8X9S7jJ MdFx+Ztg7jiZuw+6HZ/8/BWfdb9SiHFNltE/pw8yQWoCq03FeMIFnlTn9r9u3l0ecLZrS+eR CbqiIrKnX5XpXcjYqMRSnJFoqMVcVJwIAAaHX616AgAA
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] RTCWEB data channel protocol: Mandated to use?
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: Wed, 29 Jan 2014 10:18:56 -0000

Thanks for the clarification, Harald & Peter!

Regards,

Christer

-----Original Message-----
From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Peter Thatcher
Sent: 28. tammikuuta 2014 23:39
To: Harald Alvestrand
Cc: <rtcweb@ietf.org>
Subject: Re: [rtcweb] RTCWEB data channel protocol: Mandated to use?

Harald is correct.  If you use set "negotiated: true" in .createDataChannel, then the OPEN message won't be sent.  The JS can also specify the SID in .createDataChannel, allowing you to use whatever form of signalling you want with no in-band signalling.

On Tue, Jan 28, 2014 at 7:48 AM, Harald Alvestrand <harald@alvestrand.no> wrote:
> On 01/28/2014 09:28 AM, Christer Holmberg wrote:
>
> Hi,
>
>
>
> At the CLUE virtual interim yesterday, we discussed the usage of the 
> RTCWEB data channel also for CLUE. It would allow us to re-use what 
> RTCWEB has done, and it would provide interoperability between CLUE 
> entities and RTCWEB.
>
>
>
> Q1: One question that came up is whether RTCWEB MANDATES the usage of 
> the RTCWEB data channel protocol? OR, is it possible to simply 
> establish two SCTP streams (as defined in 
> draft-ietf-rtcweb-data-channel-06), and start using it?
>
>
> My understanding has been the latter - externally negotiated data 
> channels are explicitly permitted.
>
> draft-ietf-rtcweb-data-channel-06 section 6.5:
>
> 6.5.  Opening a Channel
>
>    Data channels can be opened by using internal or external
>    negotiation.  The details are out of scope of this document.
>
>    A simple protocol for internal negotiation is specified in
>    [I-D.ietf-rtcweb-data-protocol] and MUST be supported.
>
>
> "MUST be supported" is not the same as "MUST be used".
>
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>
> --
> Surveillance is pervasive. Go Dark.
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email