IETF Logo Mail Archive

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

Peter Thatcher <pthatcher@google.com> Tue, 28 January 2014 21:39 UTC

Return-Path: <pthatcher@google.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 EA3E71A034E for <rtcweb@ietfa.amsl.com>; Tue, 28 Jan 2014 13:39:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.914
X-Spam-Level:
X-Spam-Status: No, score=-1.914 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, RP_MATCHES_RCVD=-0.535, 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 sq6CWxnQGkoS for <rtcweb@ietfa.amsl.com>; Tue, 28 Jan 2014 13:39:43 -0800 (PST)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id C3F451A03AA for <rtcweb@ietf.org>; Tue, 28 Jan 2014 13:39:43 -0800 (PST)
Received: by mail-pa0-f45.google.com with SMTP id lf10so891482pab.18 for <rtcweb@ietf.org>; Tue, 28 Jan 2014 13:39:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=U4mx6ikrtYm2qyMU3ta0R3MWpdaFQQMcY/vtDKP/E1Q=; b=gxcXiln+X6L4r2cPvkE9Flhtg1U4dRhZLkJkb/lmJK7maAdx/iPltBI1m2CXYqVR28 ZErCd7BJmswfDB4aWzpIK0Z9zoS2IdqA/PWKFuOlejsBO5ta+8puBUslTWr87CacydCH BmT60jST0IVqh9ceS0V24uBthj2X1+JVIuUp8xwF4gk9GcZCnTj7TAe04XwGNraVkm+S vyzxuuFnOi4bubEWUq6U+ewYJ9OJLDhlu1M6mmMtsuXa19j7FPM3bELDjOpxSURJEPW7 lRRJkVJ0mrcfq5hX9U3XSkNUailTt69jfEuxRnZ81mFSwXtAJchsMDlZdmGMY0xPK9Sz Crew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=U4mx6ikrtYm2qyMU3ta0R3MWpdaFQQMcY/vtDKP/E1Q=; b=Oj1kVJvOUyHUDKrvlxMT095UGaYHk+4PTlgFBNda4ymz6hyc7Ux64G4VbpGtrkN7f+ WgzjrJoxlggd2VY1BuW3UuvE3pzxNay4jyVBNS7k7IB2wO78Dt+OL/uWDcBHLVEP4hLa RzwRgW6eo8BAivOzW8fRKjlb1YvRZKOiEocFCSIvX9ya5uz2m//+N/h+8y74/Dvf+9f6 P8f4n1IGpiIZJv+HJXAQnuQS3ZK2a48GQ1akek0JEx8QG55K2ToVZZWG8c38B5IQQjwQ FnK+69d11yS9kit6qAV7cXPCP+vhYiPiyVImD7UN/wxgUYRhSMYKY5Pke1V4Gr1OnDp/ /EmQ==
X-Gm-Message-State: ALoCoQlqKv4MqU/aNlgIipkpgW21l8WHVAFmBvt2uLFs+rrw12eYCdnTAkpI1/qMYxif4rGqAnkYn4JQCc1a1Q6uPyZRQCmyIAZexBIaw2ZXMU7MBt+PnzSTg3mvneBOzu8r33QmfpcRy0auCF8IeP/xOHIZZEu0eMWMHLGUD8XHuWCuUBlm8toMgxi2FnUqaBiemyfLh0lb
X-Received: by 10.68.226.200 with SMTP id ru8mr3924876pbc.77.1390945181165; Tue, 28 Jan 2014 13:39:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.66.163.234 with HTTP; Tue, 28 Jan 2014 13:39:01 -0800 (PST)
In-Reply-To: <52E7D15A.4090805@alvestrand.no>
References: <7594FB04B1934943A5C02806D1A2204B1D143FB4@ESESSMB209.ericsson.se> <52E7D15A.4090805@alvestrand.no>
From: Peter Thatcher <pthatcher@google.com>
Date: Tue, 28 Jan 2014 13:39:01 -0800
Message-ID: <CAJrXDUFGv3oRJxK31afrm-8tieyh=sKYU_KTn=jeFvY06_QA8A@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset="UTF-8"
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: Tue, 28 Jan 2014 21:39:46 -0000

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
>

v2.23.0 | Report a Bug | By Email