IETF Logo Mail Archive

Re: [dispatch] [rtcweb] Identity? (Re: Datachannel Hackathon at IETF 101 ?)

Nils Ohlmeier <nohlmeier@mozilla.com> Tue, 30 January 2018 23:37 UTC

Return-Path: <nohlmeier@mozilla.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 010D812E878 for <dispatch@ietfa.amsl.com>; Tue, 30 Jan 2018 15:37:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.com
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 BjkrwtzwpzAX for <dispatch@ietfa.amsl.com>; Tue, 30 Jan 2018 15:37:14 -0800 (PST)
Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com [IPv6:2607:f8b0:400e:c00::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2118012E869 for <dispatch@ietf.org>; Tue, 30 Jan 2018 15:37:13 -0800 (PST)
Received: by mail-pf0-x242.google.com with SMTP id k19so10659752pfj.5 for <dispatch@ietf.org>; Tue, 30 Jan 2018 15:37:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=mWBW0kGp3iXTj3guATZgQwqHT+GATsfbkwG4TvXDEd8=; b=JXwIPxTLvEhn7ZvHw+WpUWD4JvlGvycHX8g0ZmPngN1pGk3cYohilvTvalBUR/i2EW M0l0zfv9PoduGHurh3AjwG8gaEA9uz/LNk9+KWMWU+ekIXJjdszIIfbYgNLaSR2weo+P heXV1UxADaA4mrRPlGFHHOuKyr/xZcIeEKrTU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=mWBW0kGp3iXTj3guATZgQwqHT+GATsfbkwG4TvXDEd8=; b=l0AmodB1vrCzwE492Unx3zpgHf+/lszpurzAy1a4Z/McoJ8CyddXLEuWGGrVEobraX ecgcAcm4NySpxyNButuby4mJoqZ1VU/TiE8wxN3ZxS0XtNrIsjf/NpahzbXN0NvqW6aR MW3H6D8kx2jPpFkSJjZVc70iPsDo1JfR093lzd5lb39vIu8UutMYX2pd/EbT0q3iCkdy odlyPsV7CaM2aeG2F0PAfaqTmcI+HQrB1TxSmb+2Rq4x/B1592rzHvNGCYhgkghiZAbw ddUMWgu5uGiDwWHZ0Xq7yl4BXB7dlHFzut9Mc+WHsPEffovtXqHnLNwmw18OzLeudtz0 +3Vw==
X-Gm-Message-State: AKwxytfLX3iq9izRurD18mlbn0GpNzz3WDVuIzZSkDIY48k39bheACHr qDr8Fa/HDWW7Nk3VzaE2PcIh3oVvBqA=
X-Google-Smtp-Source: AH8x225OqPftHKsEee6s/CjL/q1/rch02Vf/EdJ/AjaGs1JUwBRZu2OKJF1cdp7SwU408tXTLae3eg==
X-Received: by 10.98.130.142 with SMTP id w136mr29352109pfd.236.1517355433413; Tue, 30 Jan 2018 15:37:13 -0800 (PST)
Received: from ?IPv6:2620:101:80fc:224:34cb:53c7:da30:1ac7? ([2620:101:80fc:224:34cb:53c7:da30:1ac7]) by smtp.gmail.com with ESMTPSA id j13sm35602890pfk.112.2018.01.30.15.37.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Jan 2018 15:37:12 -0800 (PST)
From: Nils Ohlmeier <nohlmeier@mozilla.com>
Message-Id: <1F301D9F-B778-422C-81F7-98F4121A11D8@mozilla.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2F403906-8AD4-413B-A4CB-3D3661E1413C"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Tue, 30 Jan 2018 15:37:06 -0800
In-Reply-To: <a28e44d4-cd86-9347-ec0e-cf253c9bbfa6@alvestrand.no>
Cc: T H Panton <thp@westhawk.co.uk>, RTCWeb IETF <rtcweb@ietf.org>, dispatch@ietf.org
To: Harald Alvestrand <harald@alvestrand.no>
References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> <a28e44d4-cd86-9347-ec0e-cf253c9bbfa6@alvestrand.no>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/iRY41U98smLMBnF87NfFFmje5AI>
Subject: Re: [dispatch] [rtcweb] Identity? (Re: Datachannel Hackathon at IETF 101 ?)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jan 2018 23:37:19 -0000

Yes I would love to test it against the Firefox Identity implementation.

Were you thinking about adding it to JS code of an open source bridge/SFU, or standing up an identity service, or both?

Best
  Nils

> On Jan 30, 2018, at 05:59, Harald Alvestrand <harald@alvestrand.no> wrote:
> 
> Speaking of features that have received little love from deployment ....
> would anyone be interested in hacking on the identity API?
> 
> It seems to have received little love from implementors so far, but
> there's been strong pushback against removing it too. We need either it
> or something like it to satisfy the security requirements we set out to
> satisfy.
> 
> Harald
> 
> 
> On 01/24/2018 12:28 PM, T H Panton wrote:
>> There has been talk over on the w3c list about the scarcity and unsuitability of free-standing WebRTC datachannel implementations.
>> 
>> I wonder if this is a suitable target for the IETF 101 hackathon?
>> 
>> The challenge would be to throw up one or 2 free standing datachannel implementations based on existing open
>> source with APIs that might suit authors of networked games or SFUs.
>> 
>> Comments? Thoughts?
>> 
>> T.
>> 
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
> 
> 
> --
> 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