From nobody Mon Jan 22 10:56:44 2018 Return-Path: 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 CE95F1289B0 for ; Mon, 22 Jan 2018 10:56:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 IUxZH9WWADbQ for ; Mon, 22 Jan 2018 10:56:40 -0800 (PST) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (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 E2F09126D73 for ; Mon, 22 Jan 2018 10:56:39 -0800 (PST) Received: by mail-lf0-x22c.google.com with SMTP id f3so11907443lfe.4 for ; Mon, 22 Jan 2018 10:56:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Rhx7KB+XajAYBRujffKLRUavtajn+4IGJAErd07Kykk=; b=XUlpeMoPzFsbI3SwraBxyLm+po9yLZjWzAfVoPEeaX4C2banoxqVAaplFQO7pcXnaN jvBIKj2QU0Nltv71hyba7VIZW/jjOJ1KvcLiRaJTZnxScLtb1eFSnkWI6k6sJXwlVxCu 9NX6LczXSJU/BB3ZXi4JndzR5Q5UYjrs9eTJ/sYt7BS/13WXm30jDTpCPomdJBVQTaVQ edqbOI7ot/T4/VvLJ/sjE/iMha9AC2obh3Ucr/wQXkYK4Yrzh2S2699t0IF8qEtnZozR 8ML9n6mi7SS/nftJ1wC2y8QOpIQnSeM4D2cxaZk4p9DhlvX0a0CgTAxd9DkQo7hzHN3v BRjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Rhx7KB+XajAYBRujffKLRUavtajn+4IGJAErd07Kykk=; b=SEO4wJTqb/Iu9S8RsTZlJja78Cbcc9+v+qpQulf/VESItlyvlP4xRXvSQL/xEnmF4v dmNee8W6niiKiOLXHEEeQJhL3aGM4KZu51FEOZY22VBzjOkVUQh6MYDl2AokXrFc3ATq TBJkTxbXul9CYmIqWhG9rXjt1rSmi2pGj/LCBYG4t8tIE3xCa2fgUfDNQAi1Ttr/FaAI A4HPYQ6Ya9NKEB/RYuj+GOqRmunOkwtRqPyH+z5PiPBia6vlnLXTb00n2UHVT3BouvDP t1LZVJx932KLXR4dDksPP+sKUkB5UHOig4b1pQDcO7aWZO0LQJxY8WsDNtbcq26gwgrt JhXA== X-Gm-Message-State: AKwxytf/fj/rrti2hKSEQdRP09wyKBE74ngIQph+aQE60TPWm1+v3/qh ttLv/UhuhD9t7JgbkEXAB46/k4632s7y2bXbbCvoug== X-Google-Smtp-Source: AH8x224sdpY+53dYv5Y/chRbO1UbC/4AJ2qiHDNJ+AcrZp3a85LpLpEOjlIzIZce+o8rhTtwqUofEMl8IY11eccmj0Y= X-Received: by 10.46.20.89 with SMTP id 25mr4145469lju.104.1516647397834; Mon, 22 Jan 2018 10:56:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.93.154 with HTTP; Mon, 22 Jan 2018 10:56:37 -0800 (PST) From: Mary Barnes Date: Mon, 22 Jan 2018 12:56:37 -0600 Message-ID: To: DISPATCH Content-Type: multipart/alternative; boundary="f403045fbd1065c349056361fd47" Archived-At: Subject: [dispatch] BoF deadline for IETF-101 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2018 18:56:43 -0000 --f403045fbd1065c349056361fd47 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, Sorry for the duplicate but I wanted to remind folks that since they moved the Bof deadline up over the past few years and we've shifted the deadlines to DISPATCH later over time, there's no longer an opportunity for us to dispatch something as a BoF for the upcoming meeting. So, if you think you have new work that has any possibility of being a BoF, you need to be working it through the BoF process. If you're not sure, it's a really good idea to get discussion going with the ADs and WG chairs *now*. As a reminder, here are the DISPATCH WG deadlines: https://trac.ietf.org/trac/dispatch - Feb 2, 2018. Cutoff date for IETF BoF submissions. - Feb 10, 2018. Cutoff date to notify the chairs/DISPATCH WG of plans to submit a proposal. - Feb 15, 2018. Cutoff for charter proposals (i.e., problem statement and proposed deliverables) for topics. - Feb 21, 2018. Announcement of topics that have been dispatched for IETF-101. - March 3, 2018. Draft submission deadline. Regards, Mary ---------- Forwarded message ---------- From: IETF Chair Date: Mon, Jan 22, 2018 at 11:25 AM Subject: New work proposals for IETF 101 due Feb 2 To: IETF Announcement List Cc: IETF I wanted to remind everyone that the deadline to submit Birds of a Feather (BoF) proposals for IETF 101 is rapidly approaching: Friday, February 2 at 23:59 UTC. Hopefully those whose have been working on ideas that seem like they need to extend an existing working group=E2=80=99s charter, need a new= working group altogether, or need some dedicated face-to-face discussion in the community have already been talking to your area directors [1] about these proposals. If not, please do so right away! And please take a look at the recommendations in RFC 5434 [2] about how to have a successful BoF. Based on community discussion the IESG kicked off last fall [3], we have updated the BoF wiki [4] to request some additional information from BoF proponents. In addition to the information we require about every BoF proposal, proponents are also encouraged to do the following in their BoF wiki entries: - List any protocols or practices that already exist in the space in which the new work is being proposed. - List any modifications to existing protocols or practices that will be required by the new work. - List any entirely new protocols or practices that will be required by the new work. - List any open source projects implementing the new work. This information will allow the IESG, with the IAB=E2=80=99s assistance, to= make more informed decisions more quickly about BoF proposals. Thanks, Alissa Cooper IETF Chair [1] https://www.ietf.org/about/groups/iesg/members/ [2] https://tools.ietf.org/html/rfc5434 [3] https://mailarchive.ietf.org/arch/msg/ietf/orzFAklApVtBSlgK8LBb4Gc-OZY [4] https://trac.tools.ietf.org/bof/trac/wiki/WikiStart --f403045fbd1065c349056361fd47 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

Sorry for the duplicate but I w= anted to remind folks that since they moved the Bof deadline up over the pa= st few years and we've shifted the deadlines to DISPATCH later over tim= e, there's no longer an opportunity for us to dispatch something as a B= oF for the upcoming meeting.=C2=A0 So, if you think you have new work that = has any possibility of being a BoF, you need to be working it through the B= oF process.=C2=A0 If you're not sure, it's a really good idea to ge= t discussion going with the ADs and WG chairs *now*.=C2=A0

As a reminder, here are the DISPATCH WG deadlines:=C2=A0
https://trac.ietf.org/trac= /dispatch

  • Feb 2, 2018. Cuto= ff date for IETF BoF submissions.
  • Feb 10, 2018. Cutoff date to notify the ch= airs/DISPATCH WG of plans to submit a proposal.
  • Feb 15, 2018. Cutoff for charter propos= als (i.e., problem statement and proposed deliverables) for topics.
    • Feb 21, 2018. Annou= ncement of topics that have been dispatched for IETF-101.
    • March 3, 2018. Draft submissi= on deadline.
Regards,
Mary


---------- Forwarded messa= ge ----------
From:=C2=A0IETF Chair=C2= =A0<chair@ietf.org>
Date: Mon, Jan 22, 2018 at 11:25 AM
Subject: New work p= roposals for IETF 101 due Feb 2
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: IE= TF <ietf@ietf.org>


I wanted to remind everyone that the= deadline to submit Birds of a Feather (BoF) proposals for IETF 101 is rapi= dly approaching: Friday, February 2 at 23:59 UTC. Hopefully those whose hav= e been working on ideas that seem like they need to extend an existing work= ing group=E2=80=99s charter, need a new working group altogether, or need s= ome dedicated face-to-face discussion in the community have already been ta= lking to your area directors [1] about these proposals. If not, please do s= o right away! And please take a look at the recommendations in RFC 5434 [2]= about how to have a successful BoF.

Based on community discussion t= he IESG kicked off last fall [3], we have updated the BoF wiki [4] to reque= st some additional information from BoF proponents. In addition to the info= rmation we require about every BoF proposal, proponents are also encouraged= to do the following in their BoF wiki entries:

- List any protocols= or practices that already exist in the space in which the new work is bein= g proposed.
- List any modifications to existing protocols or practices = that will be required by the new work.
- List any entirely new protocols= or practices that will be required by the new work.
- List any open sou= rce projects implementing the new work.

This information will allow = the IESG, with the IAB=E2=80=99s assistance, to make more informed decision= s more quickly about BoF proposals.

Thanks,
Alissa Cooper
IETF= Chair

[1]=C2=A0https://www.ietf.org/about/groups/iesg/membe= rs/
[2]=C2=A0https://tools.ietf.org/html/rfc5434
[3]=C2=A0https://mailarchive.ietf.org/arch/msg/ietf/or= zFAklApVtBSlgK8LBb4Gc-OZY=C2=A0=C2=A0
[4]=C2=A0https://trac= .tools.ietf.org/bof/trac/wiki/WikiStart

=
--f403045fbd1065c349056361fd47-- From nobody Wed Jan 24 03:28:13 2018 Return-Path: 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 20C0012DA3D for ; Wed, 24 Jan 2018 03:28:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.621 X-Spam-Level: X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 YoO-QRrUo_Vp for ; Wed, 24 Jan 2018 03:28:09 -0800 (PST) Received: from smtp002.apm-internet.net (smtp002.apm-internet.net [85.119.248.221]) (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 4FCD812DA29 for ; Wed, 24 Jan 2018 03:28:06 -0800 (PST) Received: (qmail 30499 invoked from network); 24 Jan 2018 11:28:04 -0000 X-APM-Authkey: 255286/0(159927/0) 679 Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp002.apm-internet.net with SMTP; 24 Jan 2018 11:28:04 -0000 Received: from localhost (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id 9751C18A04B3; Wed, 24 Jan 2018 11:28:04 +0000 (GMT) Received: from zimbra003.verygoodemail.com ([127.0.0.1]) by localhost (zimbra003.verygoodemail.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id DkWt6Cdyh6Cv; Wed, 24 Jan 2018 11:28:04 +0000 (GMT) Received: from [192.67.4.33] (unknown [192.67.4.33]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id 7286C18A0493; Wed, 24 Jan 2018 11:28:04 +0000 (GMT) From: T H Panton Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Message-Id: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> Date: Wed, 24 Jan 2018 11:28:03 +0000 Cc: dispatch@ietf.org To: RTCWeb IETF X-Mailer: Apple Mail (2.3445.5.20) Archived-At: Subject: [dispatch] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 11:28:11 -0000 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?=20 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. From nobody Wed Jan 24 07:24:05 2018 Return-Path: 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 D3914126C0F for ; Wed, 24 Jan 2018 07:23:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.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 QqKvk95CJXgB for ; Wed, 24 Jan 2018 07:23:57 -0800 (PST) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (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 A189A126BFD for ; Wed, 24 Jan 2018 07:23:56 -0800 (PST) Received: by mail-wm0-x231.google.com with SMTP id i186so9132257wmi.4 for ; Wed, 24 Jan 2018 07:23:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tqztPJviPH5PPwh8SnUYcN6Vz9/S7kY8/jJeSwBGWCo=; b=EQB7O/+RmkuFk3YeYwZqVxLLXr9HLexqX3G9oEzY7dRoeHHuQj+i97ZQ1ralWTm4qF 872VAQfmy1COvQ6oBvSYPCV+Z8fgrPqntJZokmI3iWgSPgX7B7OmRIGpVsmuwQmRG1Xv Z48le1tVFqoYmPIW/KscTa8rRsz7sdnLMUydUeb88dIEYnmo+bioVD2EZ/qt9n2VtMfo 28cdy2D/RpNmlZ2rHezDmwjM3nov8Bk4NfpN63aYVK8mcdjHNjUaReAMXCbqfZqo0g/W ZFSac6fk3Sz1M4QEEbB2lauQKjN0PV/L3XlRLDeerIch7wFRmnj8gHyy58o9kTpiUsyE uAWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tqztPJviPH5PPwh8SnUYcN6Vz9/S7kY8/jJeSwBGWCo=; b=f9Zw4wE/FRCMjodAcXeN4CcPG3rz3A+IRzJvDVUMA52GqPRkmbhayV+rMFxW+fm/OJ 9Ii9GzJtS9AcIhWu0vKHbnJ4RFQxu6yLU0KyX6xTbFtMQ8Y65LKsO2luWlfEsT2Ia6Tg bWi7uIHHbJTBTQ1fKAtSI2B4k/hhmrHMg5wIeEBkP2C5u/5+6BAkgXWP28TAEqtI+0cR 3KqyV4sgelad5H40BoUNcpzvEIYWHm9OGu0PrR81SnF4ZBwsOmGPRaFk2cL+QuSkscsd cKXjV7s2PVL1doHGEkqFwS5X741VSbzNHu1dNqdXRhMbTJ31OpSw/zHcmkYlPsKX24jc WzRw== X-Gm-Message-State: AKwxytckEor9GkiWiNOQfGUFM6J5Dt6Hk3hYw0VxVPlFHNQvOjtWu78O BjAzDBuXAGT/Ejw4QPz1ScZn4EUGesg7h7MXZpOZDw== X-Google-Smtp-Source: AH8x225aKhTKfHJ0ZKNfKJuwNOQgPEf4aNCvPFLActeexMXUi4G6u6KdH3Shu9+izESpIwCa3kRVWML4+MWOAADkvP0= X-Received: by 10.28.118.15 with SMTP id r15mr5701465wmc.88.1516807434967; Wed, 24 Jan 2018 07:23:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.20.66 with HTTP; Wed, 24 Jan 2018 07:23:54 -0800 (PST) In-Reply-To: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> From: Richard Barnes Date: Wed, 24 Jan 2018 10:23:54 -0500 Message-ID: To: T H Panton Cc: RTCWeb IETF , DISPATCH Content-Type: multipart/alternative; boundary="089e082f274c5ac92e0563874039" Archived-At: Subject: Re: [dispatch] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 15:23:59 -0000 --089e082f274c5ac92e0563874039 Content-Type: text/plain; charset="UTF-8" Seems worthwhile to me, if you can find some people to do it. On Wed, Jan 24, 2018 at 6:28 AM, 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 > --089e082f274c5ac92e0563874039 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Seems worthwhile to me, if you can find some people to do = it.

On W= ed, Jan 24, 2018 at 6:28 AM, T H Panton <thp@westhawk.co.uk> wrote:
There has been talk over on the = w3c list about the scarcity and unsuitability of free-standing WebRTC datac= hannel 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 imple= mentations 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

--089e082f274c5ac92e0563874039-- From nobody Wed Jan 24 07:28:55 2018 Return-Path: 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 83623126C26; Wed, 24 Jan 2018 07:28:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 m57EmtLXGGgr; Wed, 24 Jan 2018 07:28:51 -0800 (PST) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 C1FA3126C0F; Wed, 24 Jan 2018 07:28:50 -0800 (PST) Received: by mail-wm0-x22b.google.com with SMTP id b21so9358765wme.4; Wed, 24 Jan 2018 07:28:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=uIW05NAFxm6eD0Ts2fANQ5NvFVCJBI76KsFmuhUa6C8=; b=mVuHPAH6f+SriJrPhUDH0+tms6ocfqM8gc5dLWA8dfpsqnWq2D5jnb6m6BJFjayetC Om29DxtS7acIOXXdnnRQKaPCfC6NbSidvsE3CGwjVlCUds7tP/Z29tH4DItqxgUkBc1o eR+ipE5MNAb/6S/s5CV5znyH1qDR2DJBIy5NMAM0t4jTOG8A+dq9Wkdz8HpXTbFSURhT rPTxoslzjPH12kJD5DhCnS8iR+r/z6ojJOdCzIPVpfrgzwEwXs6677ejPviECwylGscg Sbi11Ij0t1o9/IWlNr2rMRm1+X8JZFDjH+uwCuYhdjexASJafIB5fYUBiSX+ctiIU+Xg bVcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=uIW05NAFxm6eD0Ts2fANQ5NvFVCJBI76KsFmuhUa6C8=; b=WXi0wPWgZQlGbXrDQ5HngHxSJOQIdpzyz8V0b6QHXo6TIx+C4lOXSGj2C5Tws29xS1 48UIrYohTn73iZ4KZEk3qb8Sj0QKAESmdkMD1yDK0XUm11y+6dbOcUlLDPNkY6JcBxMT 4fFPBXvdHnLV68OfgYKAWpcq9u/hsPy0syQdt696EWJxew0/QUhSlDrE6aKPJGbyxWrZ XP4UqSmMRMZKapAn+tVpMfU8kUlbqaummj5TGiJ0rDgrfFE2RxISFPmQHjgDV/EBQzjJ cCUKJdUZztEi2GG/P7H42BUxYl8eE3qL/f/QPuNPx756p1SLXSKwDkBA0K+52drQSe93 vVWQ== X-Gm-Message-State: AKwxytf6vNZoNpUXO+lIQwhfT41IYXk4R13tQweYT4TTbpqgOhnD5GmH p1wua7mrARUdcuzhM/vxMUQgFN0k X-Google-Smtp-Source: AH8x226UfAFIeZYb9DIVLyME7KDTwmt47wv8BYG79O+aVBdFeQWbnOEAnCL75qcDYn1CnCD7qqCv6Q== X-Received: by 10.80.145.79 with SMTP id f15mr25296226eda.283.1516807728695; Wed, 24 Jan 2018 07:28:48 -0800 (PST) Received: from [192.168.1.48] (37.red-80-28-109.staticip.rima-tde.net. [80.28.109.37]) by smtp.googlemail.com with ESMTPSA id r15sm352900edi.23.2018.01.24.07.28.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Jan 2018 07:28:47 -0800 (PST) To: T H Panton , RTCWeb IETF Cc: dispatch@ietf.org References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> From: Sergio Garcia Murillo Message-ID: <30e70fe8-abee-44da-59ec-bdd3ec82dde4@gmail.com> Date: Wed, 24 Jan 2018 16:28:46 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [dispatch] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 15:28:53 -0000 I will not be attending this IETF meeting physically, but I would be interested in collaborating (either helping to implement the datachannel libraries or integrating them on my media server for testing) Best regards Sergio On 24/01/2018 12:28, 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 From nobody Thu Jan 25 09:46:48 2018 Return-Path: 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 E689A127010; Thu, 25 Jan 2018 09:46:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.609 X-Spam-Level: X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 aApH7W8KJ7bo; Thu, 25 Jan 2018 09:46:44 -0800 (PST) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 190FB124D68; Thu, 25 Jan 2018 09:46:44 -0800 (PST) Received: from [IPv6:2a02:c6a0:4015:12:4da4:4a7d:8bb3:d066] (unknown [IPv6:2a02:c6a0:4015:12:4da4:4a7d:8bb3:d066]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 5DFE3721E280C; Thu, 25 Jan 2018 18:46:41 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) From: Michael Tuexen In-Reply-To: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> Date: Thu, 25 Jan 2018 18:46:39 +0100 Cc: RTCWeb IETF , dispatch@ietf.org, Felix Weinrank Content-Transfer-Encoding: quoted-printable Message-Id: References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> To: T H Panton X-Mailer: Apple Mail (2.3445.5.20) Archived-At: Subject: Re: [dispatch] [rtcweb] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 17:46:47 -0000 > On 24. Jan 2018, at 12:28, T H Panton wrote: >=20 > There has been talk over on the w3c list about the scarcity and = unsuitability of free-standing WebRTC datachannel implementations. >=20 > I wonder if this is a suitable target for the IETF 101 hackathon?=20 >=20 > 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. >=20 > Comments? Thoughts? We are participating and could use the Firefox WebRTC implementation. We = would be able to debug SCTP issues and possibly some issues in the WebRTC implementation = of Firefox. Best regards Michael >=20 > T. >=20 > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb From nobody Thu Jan 25 10:14:52 2018 Return-Path: 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 8235D1270B4; Thu, 25 Jan 2018 10:14:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 DKXQfN0Rqr_K; Thu, 25 Jan 2018 10:14:44 -0800 (PST) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 3D39D126D0C; Thu, 25 Jan 2018 10:14:44 -0800 (PST) X-AuditID: c1b4fb3a-335ff700000037f2-59-5a6a1e92dc94 Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id DF.1F.14322.29E1A6A5; Thu, 25 Jan 2018 19:14:42 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0352.000; Thu, 25 Jan 2018 19:14:41 +0100 From: Christer Holmberg To: Michael Tuexen , T H Panton CC: Felix Weinrank , "dispatch@ietf.org" , RTCWeb IETF Thread-Topic: [dispatch] [rtcweb] Datachannel Hackathon at IETF 101 ? Thread-Index: AQHTlgR7q7S26JKvSkKDGt0Xw0pNE6OE47Vw Date: Thu, 25 Jan 2018 18:14:41 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B6C13F489@ESESSMB109.ericsson.se> References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.150] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCIsWRmVeSWpSXmKPExsUyM2K7ve4kuawog1nvlCyWTlrAanGxaQmj xdp/7ewW694fY7GY2rqC3YHVo2fKaVaPJUt+MnlsaNnB5HFx2n6mAJYoLpuU1JzMstQifbsE roxLTy6yFlzjrZi/qYGpgXEZdxcjJ4eEgInE+m0TWboYuTiEBA4zSpxraGCGcJYwSmx8Px3I 4eBgE7CQ6P6nDdIgIhAhseNhMyNImFmgTOLScheQsLCAi8Te9Y9YIUpcJZ79XsgOYRtJvJ18 GMxmEVCVuHR+A5jNK+Ar8b9tIhOILSRQIzH/WzsjiM0J1Hv00AI2EJtRQEzi+6k1YDXMAuIS t57MZ4K4WUBiyZ7zzBC2qMTLx/9YIWwliRXbLzFC1OtILNj9iQ3C1pZYtvA1M8ReQYmTM5+w TGAUnYVk7CwkLbOQtMxC0rKAkWUVo2hxanFxbrqRkV5qUWZycXF+nl5easkmRmBcHdzy22oH 48HnjocYBTgYlXh4pR9nRgmxJpYVV+YeYpTgYFYS4d0plhUlxJuSWFmVWpQfX1Sak1p8iFGa g0VJnNcpzSJKSCA9sSQ1OzW1ILUIJsvEwSnVwBjYw2e/wnTRn40T90jee2DEw7qg1WOeYHOm +o6QKM7n7kficx5p/Hfi4Su+tXyd7qvU9ldGb4yPHs44sq7q2KOaVq8zajaZb/k2SP1JWnLf 6GLK9KBFYe5Bfp4FPF+ezPz48anT7xj3a3EaB01EDl3fv7JDKTjG9nLlCeVS7v3VQfOqVI2/ n1ZiKc5INNRiLipOBAB/BIYgpwIAAA== Archived-At: Subject: Re: [dispatch] [rtcweb] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 18:14:46 -0000 Hi, If the purpose is to test different data channel stacks (in addition to jus= t establishing the SCTP-over-DTLS association), I assume there needs to be = some applications that use the data channels? It would be nice to have webpage where people could add links to their appl= ications using data channels, so that people can then click :) Regards, Christer -----Original Message----- From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Michael Tuex= en Sent: 25 January 2018 19:47 To: T H Panton Cc: Felix Weinrank ; dispatch@ietf.org; RTCWeb IET= F Subject: Re: [dispatch] [rtcweb] Datachannel Hackathon at IETF 101 ? > On 24. Jan 2018, at 12:28, T H Panton wrote: >=20 > There has been talk over on the w3c list about the scarcity and unsuitabi= lity of free-standing WebRTC datachannel implementations. >=20 > I wonder if this is a suitable target for the IETF 101 hackathon?=20 >=20 > The challenge would be to throw up one or 2 free standing datachannel=20 > implementations based on existing open source with APIs that might suit a= uthors of networked games or SFUs. >=20 > Comments? Thoughts? We are participating and could use the Firefox WebRTC implementation. We wo= uld be able to debug SCTP issues and possibly some issues in the WebRTC imp= lementation of Firefox. Best regards Michael >=20 > T. >=20 > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb _______________________________________________ dispatch mailing list dispatch@ietf.org https://www.ietf.org/mailman/listinfo/dispatch From nobody Thu Jan 25 12:27:30 2018 Return-Path: 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 3EECA12EAA4; Thu, 25 Jan 2018 12:27:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.609 X-Spam-Level: X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 Oh9mOiDZFgXn; Thu, 25 Jan 2018 12:27:27 -0800 (PST) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06FE812EA9F; Thu, 25 Jan 2018 12:27:27 -0800 (PST) Received: from [IPv6:2003:cd:6bf1:8000:4db0:9cb0:d29e:37e] (p200300CD6BF180004DB09CB0D29E037E.dip0.t-ipconnect.de [IPv6:2003:cd:6bf1:8000:4db0:9cb0:d29e:37e]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 959B8721E280C; Thu, 25 Jan 2018 21:27:24 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) From: Michael Tuexen In-Reply-To: <7594FB04B1934943A5C02806D1A2204B6C13F489@ESESSMB109.ericsson.se> Date: Thu, 25 Jan 2018 21:27:05 +0100 Cc: T H Panton , Felix Weinrank , "dispatch@ietf.org" , RTCWeb IETF Content-Transfer-Encoding: quoted-printable Message-Id: References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> <7594FB04B1934943A5C02806D1A2204B6C13F489@ESESSMB109.ericsson.se> To: Christer Holmberg X-Mailer: Apple Mail (2.3445.5.20) Archived-At: Subject: Re: [dispatch] [rtcweb] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 20:27:29 -0000 > On 25. Jan 2018, at 19:14, Christer Holmberg = wrote: >=20 > Hi, >=20 > If the purpose is to test different data channel stacks (in addition = to just establishing the SCTP-over-DTLS association), I assume there = needs to be some applications that use the data channels? >=20 > It would be nice to have webpage where people could add links to their = applications using data channels, so that people can then click :) Some examples can be found at: https://github.com/nplab/WebRTC-Data-Channel-Playground Best regards Michael >=20 > Regards, >=20 > Christer >=20 >=20 > -----Original Message----- > From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Michael = Tuexen > Sent: 25 January 2018 19:47 > To: T H Panton > Cc: Felix Weinrank ; dispatch@ietf.org; = RTCWeb IETF > Subject: Re: [dispatch] [rtcweb] Datachannel Hackathon at IETF 101 ? >=20 >> On 24. Jan 2018, at 12:28, T H Panton wrote: >>=20 >> There has been talk over on the w3c list about the scarcity and = unsuitability of free-standing WebRTC datachannel implementations. >>=20 >> I wonder if this is a suitable target for the IETF 101 hackathon?=20 >>=20 >> The challenge would be to throw up one or 2 free standing datachannel=20= >> implementations based on existing open source with APIs that might = suit authors of networked games or SFUs. >>=20 >> Comments? Thoughts? > We are participating and could use the Firefox WebRTC implementation. = We would be able to debug SCTP issues and possibly some issues in the = WebRTC implementation of Firefox. >=20 > Best regards > Michael >>=20 >> T. >>=20 >> _______________________________________________ >> rtcweb mailing list >> rtcweb@ietf.org >> https://www.ietf.org/mailman/listinfo/rtcweb >=20 > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch From nobody Thu Jan 25 13:22:38 2018 Return-Path: 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 6289212946D; Thu, 25 Jan 2018 13:22:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 m6LfmxN0FinF; Thu, 25 Jan 2018 13:22:31 -0800 (PST) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 BB6E012EABC; Thu, 25 Jan 2018 13:22:25 -0800 (PST) X-AuditID: c1b4fb3a-34dff700000037f2-18-5a6a4a8f3918 Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 59.04.14322.F8A4A6A5; Thu, 25 Jan 2018 22:22:24 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0352.000; Thu, 25 Jan 2018 22:22:23 +0100 From: Christer Holmberg To: Michael Tuexen CC: T H Panton , Felix Weinrank , "dispatch@ietf.org" , RTCWeb IETF Thread-Topic: [dispatch] [rtcweb] Datachannel Hackathon at IETF 101 ? Thread-Index: AQHTlgR7q7S26JKvSkKDGt0Xw0pNE6OE47VwgAAVOYCAAB+c0A== Date: Thu, 25 Jan 2018 21:22:22 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B6C13FAB1@ESESSMB109.ericsson.se> References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> <7594FB04B1934943A5C02806D1A2204B6C13F489@ESESSMB109.ericsson.se> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.150] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKIsWRmVeSWpSXmKPExsUyM2K7t+4Er6wog89L2C2WTlrAanGxaQmj xdp/7ewW694fY7GY2rqC3YHVo2fKaVaPJUt+MnlsaNnB5HFx2n6mAJYoLpuU1JzMstQifbsE rozZfd+ZChaLVMw49Z25gfGNQBcjJ4eEgInE6nWzmbsYuTiEBA4zSlxuOsEIkhASWMIo8XtW chcjBwebgIVE9z9tkLCIgKnEweXzWEDqmQWmM0qcWfKcCSQhLOAisXf9I1aIIleJZ78XskPY ThKfzi4Gs1kEVCVONExgA5nJK+ArsfhsKMTe34wSnxq+sIHUcAL1rn7ZAHYDo4CYxPdTa8Dm MwuIS9x6Mp8J4mgBiSV7zjND2KISLx//Y4WwlSRWbL/ECFGvI7Fg9yc2CFtbYtnC12D1vAKC EidnPmGZwCg6C8nYWUhaZiFpmYWkZQEjyypG0eLU4uLcdCMjvdSizOTi4vw8vbzUkk2MwMg6 uOW31Q7Gg88dDzEKcDAq8fBeM8qKEmJNLCuuzD3EKMHBrCTCK6gLFOJNSaysSi3Kjy8qzUkt PsQozcGiJM7rlGYRJSSQnliSmp2aWpBaBJNl4uCUamCc+7xk46alHDt1d59+vDhw4e78tbwW vGp89beWJx3+9TrD288inONfmM7OsyvFn2vNOn48OmTP5v0s615lrns9yaiIi+llxLQD28St 3N5w/WSbbGYgylEjm7fT96NZe8Di+wFBS5MeTlbKX8xi62is3ftASMxj4wau1bdu3ntau+SH 8vGwpyyCSizFGYmGWsxFxYkATNjcbqgCAAA= Archived-At: Subject: Re: [dispatch] [rtcweb] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 21:22:33 -0000 Thanks! It would also be interesting to see some cool killer apps (other than file = transfers) using data channels :) Regards, Christer -----Original Message----- From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]=20 Sent: 25 January 2018 22:27 To: Christer Holmberg Cc: T H Panton ; Felix Weinrank ; dispatch@ietf.org; RTCWeb IETF Subject: Re: [dispatch] [rtcweb] Datachannel Hackathon at IETF 101 ? > On 25. Jan 2018, at 19:14, Christer Holmberg wrote: >=20 > Hi, >=20 > If the purpose is to test different data channel stacks (in addition to j= ust establishing the SCTP-over-DTLS association), I assume there needs to b= e some applications that use the data channels? >=20 > It would be nice to have webpage where people could add links to their=20 > applications using data channels, so that people can then click :) Some examples can be found at: https://github.com/nplab/WebRTC-Data-Channel-Playground Best regards Michael >=20 > Regards, >=20 > Christer >=20 >=20 > -----Original Message----- > From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Michael=20 > Tuexen > Sent: 25 January 2018 19:47 > To: T H Panton > Cc: Felix Weinrank ; dispatch@ietf.org;=20 > RTCWeb IETF > Subject: Re: [dispatch] [rtcweb] Datachannel Hackathon at IETF 101 ? >=20 >> On 24. Jan 2018, at 12:28, T H Panton wrote: >>=20 >> There has been talk over on the w3c list about the scarcity and unsuitab= ility of free-standing WebRTC datachannel implementations. >>=20 >> I wonder if this is a suitable target for the IETF 101 hackathon?=20 >>=20 >> The challenge would be to throw up one or 2 free standing datachannel=20 >> implementations based on existing open source with APIs that might suit = authors of networked games or SFUs. >>=20 >> Comments? Thoughts? > We are participating and could use the Firefox WebRTC implementation. We = would be able to debug SCTP issues and possibly some issues in the WebRTC i= mplementation of Firefox. >=20 > Best regards > Michael >>=20 >> T. >>=20 >> _______________________________________________ >> rtcweb mailing list >> rtcweb@ietf.org >> https://www.ietf.org/mailman/listinfo/rtcweb >=20 > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch From nobody Thu Jan 25 14:29:49 2018 Return-Path: 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 2529712EACF for ; Thu, 25 Jan 2018 14:29:47 -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=ham 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 t2GEqhqEEMCY for ; Thu, 25 Jan 2018 14:29:44 -0800 (PST) Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::22c]) (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 B727112EAD7 for ; Thu, 25 Jan 2018 14:29:30 -0800 (PST) Received: by mail-pg0-x22c.google.com with SMTP id y27so5982711pgc.5 for ; Thu, 25 Jan 2018 14:29:30 -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=RVVK1hRSaCILlMzG//20Ia6jRnKeQCxJ8gZKwshLHdg=; b=WYXas088cxUrvs4JPrDcrkNmjd+NHcK1VC7ukv7QqRxnBbQ9TiLu6yAl78LFRK7tDm 6JWhpFdQpm+MkI435uRoR5ISTeZGETFDjppViu0lnWYD35FH2ABAv9uSBO/kfbAIjnct SMgZS3TELYP0f9ylJ5ju/ST8NXWAZqXCI+G1o= 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=RVVK1hRSaCILlMzG//20Ia6jRnKeQCxJ8gZKwshLHdg=; b=mw2xlGrr46OcTddEnLw2thA8boW+TILC7NnzmiqyMr07YDL4b2xUb6s9d227/fkY5T R1Hkbp3wd+zjJ/fwNpBfN9SVApygUA4cU1164IcrmZ0Qia0GvhO5G8nyYC2Q4OV1TC4v X6jlIqnpFm3BYCFcVWm+U69xJQ3/975Nzvd6T2Cc7QiG0xCY0THDdCBSYQm3vSWr/S+x beAAxNDafAC9xZ3sY8MlzzPcocCAKvovNow19oSilC6BOcZvzJ6NTLe2F8cjhFbkdC+n IWgK40pwVFZGcZFZT2KAxqmIkkdEgfw958+GGA93c92sgLdvLhPaYP+wiLWcVFlRQoxh X9aw== X-Gm-Message-State: AKwxytcej3i0Bpl7bJ9JUWcK8ao6jAMzDeBZh6jpsn5P2gSiGSkXveU5 FlnSyPKP1Y50YIIbaMJ5mPBYcg== X-Google-Smtp-Source: AH8x224SfF+TYZtcOkf0sSVtTP1a6Ks6OjdJTXVK1B+mzEH9Q8BjazGz1q5OylhWCRTzUdhO6RSH2w== X-Received: by 10.99.150.25 with SMTP id c25mr11572556pge.136.1516919370027; Thu, 25 Jan 2018 14:29:30 -0800 (PST) Received: from ?IPv6:2601:647:4600:3f31:f9a6:ac1f:1113:381d? ([2601:647:4600:3f31:f9a6:ac1f:1113:381d]) by smtp.gmail.com with ESMTPSA id f78sm15718374pfk.144.2018.01.25.14.29.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Jan 2018 14:29:28 -0800 (PST) From: Nils Ohlmeier Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_83CA49CC-27E2-4B01-B8FB-940C94F36D9E"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Date: Thu, 25 Jan 2018 14:29:26 -0800 In-Reply-To: <7594FB04B1934943A5C02806D1A2204B6C13FAB1@ESESSMB109.ericsson.se> Cc: Michael Tuexen , Felix Weinrank , "dispatch@ietf.org" , RTCWeb IETF To: Christer Holmberg References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> <7594FB04B1934943A5C02806D1A2204B6C13F489@ESESSMB109.ericsson.se> <7594FB04B1934943A5C02806D1A2204B6C13FAB1@ESESSMB109.ericsson.se> X-Mailer: Apple Mail (2.3445.5.20) Archived-At: Subject: Re: [dispatch] [rtcweb] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 22:29:47 -0000 --Apple-Mail=_83CA49CC-27E2-4B01-B8FB-940C94F36D9E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Christer, While I totally agree that it would be awesome to find killer apps for = data channels I don=E2=80=99t think an IETF Hackathon is a) the place to = find new killer aps and b) creating something at an IETF Hackathon = requires an app idea to exist already. It was my understanding that Mr. Panton was proposing to solve the = chicken and egg problem of people complaining that creating data channel = apps (outside of browsers) is too complicated by hacking together an = easily integratabtle data channel lib. I would totally be up to = participate in that. Once we have such a lib we and other then can start playing around and = maybe until the next IETF we will have =E2=80=9Csome cool killer = apps=E2=80=9D. Best Nils Ohlmeier > On Jan 25, 2018, at 13:22, Christer Holmberg = wrote: >=20 > Thanks! >=20 > It would also be interesting to see some cool killer apps (other than = file transfers) using data channels :) >=20 > Regards, >=20 > Christer >=20 > -----Original Message----- > From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de] > Sent: 25 January 2018 22:27 > To: Christer Holmberg > Cc: T H Panton ; Felix Weinrank = ; dispatch@ietf.org; RTCWeb IETF = > Subject: Re: [dispatch] [rtcweb] Datachannel Hackathon at IETF 101 ? >=20 >> On 25. Jan 2018, at 19:14, Christer Holmberg = wrote: >>=20 >> Hi, >>=20 >> If the purpose is to test different data channel stacks (in addition = to just establishing the SCTP-over-DTLS association), I assume there = needs to be some applications that use the data channels? >>=20 >> It would be nice to have webpage where people could add links to = their >> applications using data channels, so that people can then click :) > Some examples can be found at: > https://github.com/nplab/WebRTC-Data-Channel-Playground >=20 > Best regards > Michael >>=20 >> Regards, >>=20 >> Christer >>=20 >>=20 >> -----Original Message----- >> From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of = Michael >> Tuexen >> Sent: 25 January 2018 19:47 >> To: T H Panton >> Cc: Felix Weinrank ; dispatch@ietf.org; >> RTCWeb IETF >> Subject: Re: [dispatch] [rtcweb] Datachannel Hackathon at IETF 101 ? >>=20 >>> On 24. Jan 2018, at 12:28, T H Panton wrote: >>>=20 >>> There has been talk over on the w3c list about the scarcity and = unsuitability of free-standing WebRTC datachannel implementations. >>>=20 >>> I wonder if this is a suitable target for the IETF 101 hackathon? >>>=20 >>> 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. >>>=20 >>> Comments? Thoughts? >> We are participating and could use the Firefox WebRTC implementation. = We would be able to debug SCTP issues and possibly some issues in the = WebRTC implementation of Firefox. >>=20 >> Best regards >> Michael >>>=20 >>> T. >>>=20 >>> _______________________________________________ >>> rtcweb mailing list >>> rtcweb@ietf.org >>> https://www.ietf.org/mailman/listinfo/rtcweb >>=20 >> _______________________________________________ >> dispatch mailing list >> dispatch@ietf.org >> https://www.ietf.org/mailman/listinfo/dispatch >=20 > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb --Apple-Mail=_83CA49CC-27E2-4B01-B8FB-940C94F36D9E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEQ5rmmyEsAeItlZquY2o/VmzJ+KEFAlpqWkYACgkQY2o/VmzJ +KFlpQ//VTOX3SH2trAjB3wgitKkCU5pmXOko7lOfNMV18T79gKDpSJtKmkDTsYn gxqNAfuActu2DlgL1RlheizOHmGkhrcnrLzYZb0xd2eoJ2Q4SnfH8ugwSCVcrcXl 6SZgfaoCMtrptXWaENbabx/VT+OPuvRCxI2cXwz1alD4gYw9myl8hBBBnyl/kV+r LvDm7x/eI7CqhKAFsBcpLHzl4EDTdW6S7VC0d36V6Qm+v5URQEDtblOuQ/h4/U4b cGCd1x3NLoLLP24NR1pdI3OSc0vWZ9QvJ+I3GF4vv62hue8RYLUJJOTaBVSxTSB8 CSQY4PjIKQUcfJTDJFDZ8d8aCtOZ2ppGax8v1l9Y9a036uTnKbY1huviqSvbiu1F sjCTp2w/lwXRSi3j7qZ06SUnbet10fPCyeGrV/5XRLv1gA/8Jc6sGr6rvoSDMiwL re7tbpIX9OuXvTlOn4fsGbbfgmk0xa/i/yfNpR0W9VsInxdLXy1za9P8aDl+pnQ5 +M0LBJe/pe+miYr2nnF8wJIpIHTmjqSJMhW5a2h0/WmaByqPf9dyKUVvSibRDTr+ k6bsY0YDRBxT/6vvHgx/YHZx+7RICyQ4SiwSg+7Uh0tuLT7bST3vYeGZcC/o0x50 KPD+mi3ZmMjPmr1t5lrCo+v5X8i7UhrPi0jrci/p/lr95+CG8A0= =2dNW -----END PGP SIGNATURE----- --Apple-Mail=_83CA49CC-27E2-4B01-B8FB-940C94F36D9E-- From nobody Tue Jan 30 06:05:03 2018 Return-Path: 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 BD22313186C; Tue, 30 Jan 2018 06:04:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.909 X-Spam-Level: X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 R-t1r_dwMaf5; Tue, 30 Jan 2018 06:04:54 -0800 (PST) Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E829112EB31; Tue, 30 Jan 2018 06:03:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 4E98D7C37BA; Tue, 30 Jan 2018 15:03:25 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at alvestrand.no Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8zMV0q3MJYFN; Tue, 30 Jan 2018 15:02:33 +0100 (CET) Received: from [IPv6:2001:470:de0a:1::f95] (unknown [IPv6:2001:470:de0a:1::f95]) by mork.alvestrand.no (Postfix) with ESMTPSA id 410F27C3237; Tue, 30 Jan 2018 14:59:23 +0100 (CET) To: T H Panton , RTCWeb IETF Cc: dispatch@ietf.org References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> From: Harald Alvestrand Message-ID: Date: Tue, 30 Jan 2018 14:59:22 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: [dispatch] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 14:04:57 -0000 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. From nobody Tue Jan 30 15:37:22 2018 Return-Path: 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 ; 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 ; 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 ; Tue, 30 Jan 2018 15:37:13 -0800 (PST) Received: by mail-pf0-x242.google.com with SMTP id k19so10659752pfj.5 for ; 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 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: Cc: T H Panton , RTCWeb IETF , dispatch@ietf.org To: Harald Alvestrand References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> X-Mailer: Apple Mail (2.3445.5.20) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 23:37:19 -0000 --Apple-Mail=_2F403906-8AD4-413B-A4CB-3D3661E1413C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii 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 = wrote: >=20 > Speaking of features that have received little love from deployment = .... > would anyone be interested in hacking on the identity API? >=20 > 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. >=20 > Harald >=20 >=20 > 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. >>=20 >> I wonder if this is a suitable target for the IETF 101 hackathon? >>=20 >> 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. >>=20 >> Comments? Thoughts? >>=20 >> T. >>=20 >> _______________________________________________ >> dispatch mailing list >> dispatch@ietf.org >> https://www.ietf.org/mailman/listinfo/dispatch >=20 >=20 > -- > Surveillance is pervasive. Go Dark. >=20 > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb --Apple-Mail=_2F403906-8AD4-413B-A4CB-3D3661E1413C Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEQ5rmmyEsAeItlZquY2o/VmzJ+KEFAlpxAaIACgkQY2o/VmzJ +KEWkRAAjeDlZz15z0d5OysmCdfnM/8ygzki4mopFq5C9CPUV1kO3f8EOhXW5Q9o 6uj8MqQea0zVK8qOeV0nN1tPkRJcM6Kr+OW6QrzwmmXHZgHjN7Z6oTZ4W52auS80 MlVzS9wkLxAxvNOtZAveRUwNCemYp4LVYGOpoJ7l9A9v1VVniJbu6yHghjkBvv3/ WiUEwBoeNj7/XgAR0Skz4pNA7u5CmcFV1ul/4UvH3MuLpNpDAkG4SPoTVQKLip4i XrKwjJ/DoNre97EFLFohaVLpmz1eFvIl+olfe4qr9aDRX7uLi7k93sLaS4A1a3dx fZbJ9BVcNll8ydM8QZ/dzUvxbFWHA00UvLI7V4VFMBDrQ9jpYoVtq1Seep6hzLu/ LT7PCJYM9poeIPR1zSSUwnIUzdpS5I8ab/YYkurUOGj3VQpOVYELAFmxCdKxr2k3 Y1DtRfgZYDDlxLzH4WdEleTJTi1fEN2rUphGcDUhX4ZDPYLKUvDrIIIb80r/3p9G 4vK+cHIaYY1BfPSfa7p1I/yTI4o9THMV9cLLtHqLic406rQqJ3bpbtiFPxs/J8t1 gmOVhdDEFGdHA5/vaPNNj3laBuO1OdSAmOvnaZ9E9gc0wiiqG2sfV7BPg5+5UIR8 aaTBFxh5zJlFjTBb0OxmUL6rQf0xvzmvw4ivBPa1BDhix1KVmtE= =eBcP -----END PGP SIGNATURE----- --Apple-Mail=_2F403906-8AD4-413B-A4CB-3D3661E1413C-- From nobody Tue Jan 30 23:50:37 2018 Return-Path: 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 44CC2131981; Tue, 30 Jan 2018 23:50:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.908 X-Spam-Level: X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 GOV4TP_z1WWT; Tue, 30 Jan 2018 23:50:28 -0800 (PST) Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1709D131975; Tue, 30 Jan 2018 23:50:25 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 9E1027C3961; Wed, 31 Jan 2018 08:50:23 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at alvestrand.no Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8kKf62YekKQR; Wed, 31 Jan 2018 08:50:22 +0100 (CET) Received: from [IPv6:2001:470:de0a:1::6bb] (unknown [IPv6:2001:470:de0a:1::6bb]) by mork.alvestrand.no (Postfix) with ESMTPSA id 670277C394A; Wed, 31 Jan 2018 08:50:22 +0100 (CET) To: Nils Ohlmeier Cc: dispatch@ietf.org, RTCWeb IETF References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> <1F301D9F-B778-422C-81F7-98F4121A11D8@mozilla.com> From: Harald Alvestrand Message-ID: <76f85272-32dc-5282-bd4f-6adbded028bf@alvestrand.no> Date: Wed, 31 Jan 2018 08:50:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <1F301D9F-B778-422C-81F7-98F4121A11D8@mozilla.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lqcngquFUDlYSYCclTaKWJQ73VoCpV9WO" Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 07:50:31 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --lqcngquFUDlYSYCclTaKWJQ73VoCpV9WO Content-Type: multipart/mixed; boundary="N7cpxCIFVPDK2edDSYPG8oiuQr878FUvN"; protected-headers="v1" From: Harald Alvestrand To: Nils Ohlmeier Cc: dispatch@ietf.org, RTCWeb IETF Message-ID: <76f85272-32dc-5282-bd4f-6adbded028bf@alvestrand.no> Subject: Re: [dispatch] [rtcweb] Identity? (Re: Datachannel Hackathon at IETF 101 ?) References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk> <1F301D9F-B778-422C-81F7-98F4121A11D8@mozilla.com> In-Reply-To: <1F301D9F-B778-422C-81F7-98F4121A11D8@mozilla.com> --N7cpxCIFVPDK2edDSYPG8oiuQr878FUvN Content-Type: multipart/alternative; boundary="------------A39A8567CA1E6CDB67124B38" Content-Language: en-US This is a multi-part message in MIME format. --------------A39A8567CA1E6CDB67124B38 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 01/31/2018 12:37 AM, Nils Ohlmeier wrote: > Yes I would love to test it against the Firefox Identity implementation= =2E > > Were you thinking about adding it to JS code of an open source bridge/S= FU, or standing up an identity service, or both? Whatever can be shown to work. The point would be to show by demonstration that it's (relatively) easy to provide and use identity service and that Firefox browsers can use it with different backends / services. (I don't see any chance to get identity into Chrome by London - if we can build a convincing story in London, the next IETF might be more hopeful.) > > Best > Nils > >> On Jan 30, 2018, at 05:59, Harald Alvestrand wr= ote: >> >> Speaking of features that have received little love from deployment ..= =2E. >> 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 i= t >> or something like it to satisfy the security requirements we set out t= o >> 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 unsui= tability 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 > > > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch --=20 Surveillance is pervasive. Go Dark. --------------A39A8567CA1E6CDB67124B38 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
On 01/31/2018 12:37 AM, Nils Ohlmeier wrote:
Yes I would love to test it against the Firefox Iden=
tity implementation.

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

Whatever can be shown to work. The point would be to show by demonstration that it's (relatively) easy to provide and use identity service and that Firefox browsers can use it with different backends / services.

(I don't see any chance to get identity into Chrome by London - if we can build a convincing story in London, the next IETF might be more hopeful.)


Best
  Nils


On Jan 30, 2018, at 05:59, Harald Alvestrand <ha=
rald@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 t=
he scarcity and unsuitability of free-standing WebRTC datachannel impleme=
ntations.

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 imp=
lementations based on existing open
source with APIs that might suit authors of networked games or SFUs.

Comments? Thoughts?

T.

_______________________________________________
dispatch mailing list
d=
ispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch


--
Surveillance is pervasive. Go Dark.

_______________________________________________
rtcweb mailing list
rtc=
web@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb


      

      

      

      
_______________________________________________
dispatch mailing list
d=
ispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch


    

    


    

    
--=20
Surveillance is pervasive. Go Dark.


  


--------------A39A8567CA1E6CDB67124B38--

--N7cpxCIFVPDK2edDSYPG8oiuQr878FUvN--

--lqcngquFUDlYSYCclTaKWJQ73VoCpV9WO
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEb4QYyvC+S5akmU3BawFW3omifDQFAlpxdT0ACgkQawFW3omi
fDSXwBAAgfV1Fm9PoDqiBrWfdwMVCYhj4s288jJayPuToyHfyCS44v5WysIZV/27
B1oUmNNmigk9FptfRQcJkucAT+vecQjcHuB0XlxRKlkCGkS9Odgnif7D8W5Ohpj5
yX0Vef+QZaFsGIw94BDKMpCDYp1PL5KLKesIYTOg/XcrZX0aFEdtycZzKQfU0F7H
v/+Psse9TK6RStEFnomQ1SYoOLjbYCvNaljGnqOsYLOFKEr0vVzF9ATrVEPojsTJ
hYO1oCABNxhsS2CeoDomT2lsdoFtZh0srl/GFCUPKX2Ixt6LEPfVJYANSxL/cmUp
+mi7/mrSBfh6sKeKLHyScbYsJOMN0lohqt+0R2UKDzEeXWvkqZmQKi3o56jDVR3K
4lh55tKqdA7ac3Meh3SdzSkiPZdjpYRuggGmL90nqsl5bgVSUT1bVTgt2IVoFDaQ
c16ndZDd7DuJwrOnS7/cJZflU2lU6+G276gzf4BzIy9ycJGr1otYlqss/wNatwG9
CMDt9KXdA0Bku9sZ6xL6gnEIbiQcOJgkquS+Mzxi5lc8KqkhLwnt7mKit8T4qC7R
nbPuXSAc7JCbfzvE7dCEh6cpTDI2Zk/spgp8+VGWmqyuKOwhsdgYW7gVQdKJhrdj
E1mZbb6G/rwOCIHX6JQUIHLZgGqzdhePqzmqVZt8itOIyww4/x4=
=oQMx
-----END PGP SIGNATURE-----

--lqcngquFUDlYSYCclTaKWJQ73VoCpV9WO--


From nobody Wed Jan 31 08:34:39 2018
Return-Path: 
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 058E312EC6B; Wed, 31 Jan 2018 08:34:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 xP77JG94mWZF; Wed, 31 Jan 2018 08:34:34 -0800 (PST)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (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 899E2131622; Wed, 31 Jan 2018 08:34:17 -0800 (PST)
Received: by mail-lf0-x232.google.com with SMTP id o89so21632499lfg.10; Wed, 31 Jan 2018 08:34:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cnasQpj3KBexmylcmUmgomNKclWu+8s2W6rRL+m2R9c=; b=suO+2HlaGU55iTXur0+aCdieqp0rrcjeSBSCh4t0vSDfaqfxDIA2SZwPqsqZVVqZOQ gsnR0mjmcf1eSAUsSWGvrkoGeNZmamd3HQ0sTwH5W1m7IFHT62pw867vk4HHhkeB/Po0 Q2MkLU857tpofLOtGhj7f8okg/uidYDQo//kO0cXWDhEa7TmcPmsGnoJFg9G/Js3ExU7 SL4i/fXJLXpdNCKeASoc0416EsmYz8uvCGEZfld5/Lc6geydpfko6cZOJvr6jBcAdF2I y4+dHZoBZvQ014mwfBivs84CNnphsOVVeGe9GmLKvReP1Ket88ARDHa9ccfPnP2+Far6 E02A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cnasQpj3KBexmylcmUmgomNKclWu+8s2W6rRL+m2R9c=; b=KI85SiDiL/DEzlC0T/Q+qHX1NENOH5OlcvdrgJMzIiO5O62xtAxDdyMOcTZQNmoiN1 9kxIM01WkHyLsBOJbbIDLWIogtx4Is0V28sUs7d40lPwfst97xonLBeye6mqXh/Wi69I 2L4SYqi1ich0Cmt2OJe109V+HQIjxYFkzSchR8i1mznzsWy7RpoIOZmWQUCRyMDxtKrt SqdZAh7NLYzC6wInBJvXJoXCVwAPOoxtCWk28k3xlLOkYsEPmHH78ES4abtlZD97b1ik 2e1Sr7yEsSoZGzAqlQ6c5lhuWkm3XYBjZ/6e4x6cRwpKTT3TYoOsAGc45k3XmnzSpvMY TAXg==
X-Gm-Message-State: AKwxytdv0Mkmut3HPDI704V9zVLBzRN+V+M8SoA4kwRSmuN0+s155K0b UcGW4uogGizLpMyDoBnU2s4kYirAnrm0/wB0rVE=
X-Google-Smtp-Source: AH8x226DloAJTPAFI+Rwgjs5B4ieRZcclunCZCj2US+RbBYDgw92dF+gVwNWNEVTXotpiyabp4Aq3FsXRcVa6TJLN6w=
X-Received: by 10.25.80.13 with SMTP id e13mr3405065lfb.72.1517416455870; Wed, 31 Jan 2018 08:34:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.160.81 with HTTP; Wed, 31 Jan 2018 08:34:15 -0800 (PST)
In-Reply-To: 
References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk>  <7594FB04B1934943A5C02806D1A2204B6C13F489@ESESSMB109.ericsson.se>  <7594FB04B1934943A5C02806D1A2204B6C13FAB1@ESESSMB109.ericsson.se> 
From: Alexandre GOUAILLARD 
Date: Wed, 31 Jan 2018 08:34:15 -0800
Message-ID: 
To: Nils Ohlmeier 
Cc: Christer Holmberg , "dispatch@ietf.org" ,  RTCWeb IETF , Felix Weinrank 
Content-Type: multipart/alternative; boundary="94eb2c1cb0ded41d930564150c95"
Archived-At: 
Subject: Re: [dispatch] [rtcweb]  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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 31 Jan 2018 16:34:38 -0000

--94eb2c1cb0ded41d930564150c95
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

depending on which day this happens, I would join.

On Thu, Jan 25, 2018 at 2:29 PM, Nils Ohlmeier 
wrote:

> Hi Christer,
>
> While I totally agree that it would be awesome to find killer apps for
> data channels I don=E2=80=99t think an IETF Hackathon is a) the place to =
find new
> killer aps and b) creating something at an IETF Hackathon requires an app
> idea to exist already.
>
> It was my understanding that Mr. Panton was proposing to solve the chicke=
n
> and egg problem of people complaining that creating data channel apps
> (outside of browsers) is too complicated by hacking together an easily
> integratabtle data channel lib. I would totally be up to participate in
> that.
>
> Once we have such a lib we and other then can start playing around and
> maybe until the next IETF we will have =E2=80=9Csome cool killer apps=E2=
=80=9D.
>
> Best
>   Nils Ohlmeier
>
> > On Jan 25, 2018, at 13:22, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
> >
> > Thanks!
> >
> > It would also be interesting to see some cool killer apps (other than
> file transfers) using data channels :)
> >
> > Regards,
> >
> > Christer
> >
> > -----Original Message-----
> > From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
> > Sent: 25 January 2018 22:27
> > To: Christer Holmberg 
> > Cc: T H Panton ; Felix Weinrank <
> weinrank@fh-muenster.de>; dispatch@ietf.org; RTCWeb IETF 
> > Subject: Re: [dispatch] [rtcweb] Datachannel Hackathon at IETF 101 ?
> >
> >> On 25. Jan 2018, at 19:14, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
> >>
> >> Hi,
> >>
> >> If the purpose is to test different data channel stacks (in addition t=
o
> just establishing the SCTP-over-DTLS association), I assume there needs t=
o
> be some applications that use the data channels?
> >>
> >> It would be nice to have webpage where people could add links to their
> >> applications using data channels, so that people can then click :)
> > Some examples can be found at:
> > https://github.com/nplab/WebRTC-Data-Channel-Playground
> >
> > Best regards
> > Michael
> >>
> >> Regards,
> >>
> >> Christer
> >>
> >>
> >> -----Original Message-----
> >> From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Michael
> >> Tuexen
> >> Sent: 25 January 2018 19:47
> >> To: T H Panton 
> >> Cc: Felix Weinrank ; dispatch@ietf.org;
> >> RTCWeb IETF 
> >> Subject: Re: [dispatch] [rtcweb] Datachannel Hackathon at IETF 101 ?
> >>
> >>> On 24. Jan 2018, at 12:28, 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?
> >> We are participating and could use the Firefox WebRTC implementation.
> We would be able to debug SCTP issues and possibly some issues in the
> WebRTC implementation of Firefox.
> >>
> >> Best regards
> >> Michael
> >>>
> >>> T.
> >>>
> >>> _______________________________________________
> >>> rtcweb mailing list
> >>> rtcweb@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/rtcweb
> >>
> >> _______________________________________________
> >> dispatch mailing list
> >> dispatch@ietf.org
> >> https://www.ietf.org/mailman/listinfo/dispatch
> >
> > _______________________________________________
> > 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
>
>


--=20
Alex. Gouaillard, PhD, PhD, MBA
---------------------------------------------------------------------------=
---------
President - CoSMo Software Consulting, Singapore
---------------------------------------------------------------------------=
---------
sg.linkedin.com/agouaillard

   -

--94eb2c1cb0ded41d930564150c95
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


depending on which day this happens, I would join.

On Thu, Jan 25, 201=
8 at 2:29 PM, Nils Ohlmeier <nohlmeier@mozilla.com> wrot=
e:
Hi Christer,



While I totally agree that it would be awesome to find killer apps for data=
 channels I don=E2=80=99t think an IETF Hackathon is a) the place to find n=
ew killer aps and b) creating something at an IETF Hackathon requires an ap=
p idea to exist already.



It was my understanding that Mr. Panton was proposing to solve the chicken =
and egg problem of people complaining that creating data channel apps (outs=
ide of browsers) is too complicated by hacking together an easily integrata=
btle data channel lib. I would totally be up to participate in that.



Once we have such a lib we and other then can start playing around and mayb=
e until the next IETF we will have =E2=80=9Csome cool killer apps=E2=80=9D.=




Best

=C2=A0 Nils Ohlmeier




> On Jan 25, 2018, at 13:22, Christer Holmberg <christer.holmberg@ericsson.com> wr=
ote:

>

> Thanks!

>

> It would also be interesting to see some cool killer apps (other than =
file transfers) using data channels :)

>

> Regards,

>

> Christer

>

> -----Original Message-----

> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]

> Sent: 25 January 2018 22:27

> To: Christer Holmberg <christer.holmberg@ericsson.com>

> Cc: T H Panton <thp@westhawk.=
co.uk>; Felix Weinrank <weinrank@fh-muenster.de>; dis=
patch@ietf.org; RTCWeb IETF <rtcw=
eb@ietf.org>

> Subject: Re: [dispatch] [rtcweb] Datachannel Hackathon at IETF 101 ?
>

>> On 25. Jan 2018, at 19:14, Christer Holmberg <christer.holmberg@ericsson.com>=
; wrote:

>>

>> Hi,

>>

>> If the purpose is to test different data channel stacks (in additi=
on to just establishing the SCTP-over-DTLS association), I assume there nee=
ds to be some applications that use the data channels?

>>

>> It would be nice to have webpage where people could add links to t=
heir

>> applications using data channels, so that people can then click :)=


> Some examples can be found at:

> https://github.com/nplab/WebRTC-Dat=
a-Channel-Playground

>

> Best regards

> Michael

>>

>> Regards,

>>

>> Christer

>>

>>

>> -----Original Message-----

>> From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Michael

>> Tuexen

>> Sent: 25 January 2018 19:47

>> To: T H Panton <thp@westh=
awk.co.uk>

>> Cc: Felix Weinrank <=
weinrank@fh-muenster.de>; dispa=
tch@ietf.org;

>> RTCWeb IETF <rtcweb@ietf.org=
>

>> Subject: Re: [dispatch] [rtcweb] Datachannel Hackathon at IETF 101=
 ?

>>

>>> On 24. Jan 2018, at 12:28, T H Panton <thp@westhawk.co.uk> wrote:

>>>

>>> There has been talk over on the w3c list about the scarcity an=
d unsuitability of free-standing WebRTC datachannel implementations.

>>>

>>> I wonder if this is a suitable target for the IETF 101 hackath=
on?

>>>

>>> The challenge would be to throw up one or 2 free standing data=
channel

>>> implementations based on existing open source with APIs that m=
ight suit authors of networked games or SFUs.

>>>

>>> Comments? Thoughts?

>> We are participating and could use the Firefox WebRTC implementati=
on. We would be able to debug SCTP issues and possibly some issues in the W=
ebRTC implementation of Firefox.

>>

>> Best regards

>> Michael

>>>

>>> T.

>>>

>>> _______________________________________________

>>> rtcweb mailing list

>>> rtcweb@ietf.org

>>> https://www.ietf.org/mailman/listinf=
o/rtcweb

>>

>> _______________________________________________

>> dispatch mailing list

>> dispatch@ietf.org

>> https://www.ietf.org/mailman/listinfo/di=
spatch

>

> _______________________________________________

> 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




-- 
=

Alex. Gouaillard, P=
hD, PhD, MBA
----------------------------------------------------------=
--------------------------
President - CoSMo Software Consulting,=
 Singapore
------------------------------------------------------=
------------------------------

    • 


--94eb2c1cb0ded41d930564150c95--


From nobody Wed Jan 31 08:37:00 2018
Return-Path: 
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 626A81252BA; Wed, 31 Jan 2018 08:36:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 civGmAFKRjzZ; Wed, 31 Jan 2018 08:36:53 -0800 (PST)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 776D812EB0F; Wed, 31 Jan 2018 08:36:36 -0800 (PST)
Received: by mail-lf0-x22d.google.com with SMTP id q17so21644577lfa.9; Wed, 31 Jan 2018 08:36:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Y7K0EEWLLWqN+J9J9SiyjRed94GPJupNWBCg5Xr2MwU=; b=Rvn5sdasKpvAd+SoXY6EAnsc208OXxYudxE/D2VfHlmpri0LEfyJzzRSWsb2PF6JHW 8X9F0zKcEqLfBynsNxr+29ipzJ7H4QcVz+O4C0YQTYtlQEeVAgg+MoCe+G4bRSXR9MTi N9XQxrYG5EFcTJofDK9nQuv10YepjQr+5RBwrcsWTfftxuGha9fj0ydgk6OcbiTbCTAs 5SkMEovEJ/rMKxK3SPI6zOXRVvUowbsKHRaOwVjecoLmpFGrnIvgj+g6bH6EEPnI4Axx OEWe8nHJKZqbL8d2rGl5zOeSyDDZLGMhQotMgvGilNx+/TuumxIvXkn3dObq/LXGpXbQ wuxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Y7K0EEWLLWqN+J9J9SiyjRed94GPJupNWBCg5Xr2MwU=; b=msoHaRN2EXkNSYzbibuKP//DlYee6XtvhUwLa4I0rv6DVdvYcrcv74WxAtLuCPh1yY tff1IaODMAnLmMIB7MgR/OfMnye+BWPNHsl+BBzyLoZTwhHBjoH/oRY/mJ/abC6XxSVC vtEQtcBEOe2e+563DdlFo8Vc+KnXNjgJuhetDFgEQU6Ma5LFHt6W9fVV24dQ6IBoAiMr ORPd6pjhNOGwjcMbskwQgpy8WDhHWGxyQk9PZFsyveO8kxrxxIGwAn9gWaOu3/ImGNao 3B752Ij6zp2KjLrwMOmGk1y6cmsVIWHGt0jlFpHtv3QvPv49ULRRFRVqfwrA5MAEvOlK 8F+w==
X-Gm-Message-State: AKwxyteUUqMpnFGcmRHX9tcy1lkB5GiZ2+C4dCtlQ1oFtJGb0x3mg8HH xfsFPDgeZVksH1yL0s3YLUKYeYKcKxRruBN1UwA=
X-Google-Smtp-Source: AH8x227PIyykTDx5NEiqPfYGFw5H9WV3lPP4JObTPeVkLL3QNRLyeYvatbwStw78oQp3pbSbTQns1I4Osaw2Zb+6XDg=
X-Received: by 10.46.80.88 with SMTP id v24mr3312605ljd.86.1517416594789; Wed, 31 Jan 2018 08:36:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.160.81 with HTTP; Wed, 31 Jan 2018 08:36:34 -0800 (PST)
In-Reply-To: <1F301D9F-B778-422C-81F7-98F4121A11D8@mozilla.com>
References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk>  <1F301D9F-B778-422C-81F7-98F4121A11D8@mozilla.com>
From: Alexandre GOUAILLARD 
Date: Wed, 31 Jan 2018 08:36:34 -0800
Message-ID: 
To: Nils Ohlmeier 
Cc: Harald Alvestrand , dispatch@ietf.org, RTCWeb IETF 
Content-Type: multipart/alternative; boundary="f403045fb74e1bec320564151502"
Archived-At: 
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 31 Jan 2018 16:36:55 -0000

--f403045fb74e1bec320564151502
Content-Type: text/plain; charset="UTF-8"

I might have a use case with block chain, and bandwidth to hack something
there in march.
if I understand correctly, you need *one* implementation of the concept to
play well with the webrtc spec, correct?

On Tue, Jan 30, 2018 at 3:37 PM, Nils Ohlmeier 
wrote:

> 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 
> 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
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>


-- 
Alex. Gouaillard, PhD, PhD, MBA
------------------------------------------------------------------------------------
President - CoSMo Software Consulting, Singapore
------------------------------------------------------------------------------------
sg.linkedin.com/agouaillard

   -

--f403045fb74e1bec320564151502
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


    I might have a use case with block chain, and bandwidth to=
 hack something there in march.
    if I understand correctly, you need *on=
e* implementation of the concept to play well with the webrtc spec, correct=
?

    On T=
ue, Jan 30, 2018 at 3:37 PM, Nils Ohlmeier <nohlmeier@mozilla.com&=
gt; wrote:
    Yes I would love to tes=
t 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
    
=C2=A0 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 eith=
er it
    
> or something like it to satisfy the security requirements we set out t=
o
    
> 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 un=
suitability of free-standing WebRTC datachannel implementations.
    
>>
    
>> I wonder if this is a suitable target for the IETF 101 hackathon?<=
br>
>>
    
>> The challenge would be to throw up one or 2 free standing datachan=
nel implementations based on existing open
    
>> source with APIs that might suit authors of networked games or SFU=
s.
    
>>
    
>> Comments? Thoughts?
    
>>
    
>> T.
    
>>
    
>> _______________________________________________
    
>> dispatch mailing list
    
>> dispatch@ietf.org
    
>> https://www.ietf.org/mailman/listinfo/di=
spatch
    
>
    
>
    
> --
    
> 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




    -- 
    =

    Alex. Gouaillard, P=
hD, PhD, MBA
    ----------------------------------------------------------=
--------------------------
    President - CoSMo Software Consulting,=
 Singapore
    ------------------------------------------------------=
------------------------------

    • 

    

--f403045fb74e1bec320564151502--


From nobody Wed Jan 31 08:49:17 2018
Return-Path: 
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 1F24412EB23 for ; Wed, 31 Jan 2018 08:49:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level: 
X-Spam-Status: No, score=-4.32 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_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=ericsson.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 UHmwum8aoQvZ for ; Wed, 31 Jan 2018 08:49:10 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 63E9C12EBE3 for ; Wed, 31 Jan 2018 08:49:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1517417346; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=LSAc2hyLAki5be7Z+/vmLf6uTL0e8LBSlOX56Gq0CS0=; b=Tl3wZv3AQOMlq9t0PF2FjEDOdth3hwDiUOsF8+1spWKb8oa3lL3icijReEOPaIbZ PDcwOnW/6fn6uOsjgP5o1VkHSPMlwMe+TjeZ4TZDO7giiQqcHyIW0dZqx6P/bd3f xVAoBALAStO6higG3S0ZjEkuozNRuFY7zm17NmRRjfA=;
X-AuditID: c1b4fb30-d49ff70000006bc7-95-5a71f3829bb5
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 92.2E.27591.283F17A5; Wed, 31 Jan 2018 17:49:06 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0352.000; Wed, 31 Jan 2018 17:49:06 +0100
From: Christer Holmberg 
To: Nils Ohlmeier 
CC: Michael Tuexen , Felix Weinrank , "dispatch@ietf.org" , "RTCWeb IETF" 
Thread-Topic: [rtcweb] [dispatch]  Datachannel Hackathon at IETF 101 ?
Thread-Index: AQHTliv5urSBOFf32Uic+hg3oehF36OON9RQ
Date: Wed, 31 Jan 2018 16:49:05 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B6C14BE0B@ESESSMB109.ericsson.se>
References: <4B65832E-7BD6-4515-9C09-0C392BC85BC9@westhawk.co.uk>  <7594FB04B1934943A5C02806D1A2204B6C13F489@ESESSMB109.ericsson.se>  <7594FB04B1934943A5C02806D1A2204B6C13FAB1@ESESSMB109.ericsson.se> 
In-Reply-To: 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCIsWRmVeSWpSXmKPExsUyM2J7oG7T58Iog9lPjC2WTlrAanGxaQmj xfV5kxkt1v5rZ7eY2rqC3YHVo2fKaVaPJUt+MnlsaNnB5NF3oIs1gCWKyyYlNSezLLVI3y6B K2P5p6OMBYsMK1p3LWRsYGww6GLk5JAQMJFoaz/J3MXIxSEkcJhRov3kZxYIZwmjxMaGNexd jBwcbAIWEt3/tEFMEQFNiRMb+UBKmAXWMkpM2PqWDWSQsICrxPY3y5hBbBEBN4mndz+xQthG Em3bpoDVsAioSjxYfosFxOYV8JWYuXQFI8SuL0wSk69sASviFLCXOLTvITuIzSggJvH91Bom EJtZQFzi1pP5TBBXC0gs2XOeGcIWlXj5+B8rhK0ksfbwdhaQQ5mBDl2/Sx+iVVFiSjfESF4B QYmTM5+wTGAUnYVk6iyEjllIOmYh6VjAyLKKUbQ4tTgpN93ISC+1KDO5uDg/Ty8vtWQTIzCu Dm75bbCD8eVzx0OMAhyMSjy8B+8VRgmxJpYVV+YeYpTgYFYS4d1zESjEm5JYWZValB9fVJqT WnyIUZqDRUmc96Qnb5SQQHpiSWp2ampBahFMlomDU6qBccOteR9kN59q1nt55p/wV5kjDzPF ajTKTv07dvl3ceDF/9ztjgX7tK3brjBvYzS2n6HOaXcltv6TteMxb5cCzdn3boe/ffWgcufr DTWm5cHZ2ubpt/U0jXqSzp/7JZ5r95E/8NwVwUIf7u6wb45RrqXrP5ZGdzPcf/VF8lFF+z37 B+x92yJslViKMxINtZiLihMB6bjaGKcCAAA=
Archived-At: 
Subject: Re: [dispatch] [rtcweb]   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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 31 Jan 2018 16:49:12 -0000

SGksDQoNCkkgYWdyZWUgdGhhdCB0aGUgbWFpbiBwdXJwb3NlIG9mIHRoZSBoYWNrYXRob24gaXMg
bm90IHRvIG1ha2UgYXBwcy4NCg0KQnV0LCB3aGF0IHByZXZlbnRzIHBlb3BsZSBmcm9tIHNob3dp
bmcgdGhlaXIgYXBwcywgYW5kIGRpc2N1c3MgZGF0YSBjaGFubmVsIHJlbGF0ZWQgcHJvYmxlbXMg
dGhhdCB0aGV5IG1heSBoYXZlIHJhbiBpbnRvPyBBbHNvLCBoYXZpbmcgYSAic2hvdyBjYXNlIiBt
YXkgdHJpZ2dlciB3aWRlciBpbnRlcmVzdCA6KQ0KDQpGb3IgZXhhbXBsZSwgd2hlbiBJIGRpZCBh
IGZpbGUgdHJhbnNmZXIgYXBwIHNvbWUgdGltZSBhIGZldyB5ZWFycyBhZ28sIEkgbm90ZWQgdGhh
dCB0aGUgZGF0YSBjaGFubmVsIGtlcHQgZ29pbmcgZG93bi4gT24gdGhlIE1vemlsbGEoPykgZGV2
ZWxvcGVyIHNpdGUgSSBmaWd1cmVkIG91dCB0aGF0IG9uZSBoYWQgdG8gaW5jbHVkZSBhcHBsaWNh
dGlvbiBsZXZlbCBwYXVzZXMgYmV0d2VlbiBzZW5kaW5nIGZyYWdtZW50cyBmcm9tIHByZXZlbnRp
bmcgdGhhdCB0byBoYXBwZW4uIERvbid0IGtub3cgaWYgdGhhdCBpcyBzdGlsbCBhbiBpc3N1ZSwg
YnV0IGp1c3QgdG8gZ2l2ZSBhbiBleGFtcGxlLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoN
Cg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IE5pbHMgT2hsbWVpZXIgW21haWx0
bzpub2hsbWVpZXJAbW96aWxsYS5jb21dIA0KU2VudDogMjYgSmFudWFyeSAyMDE4IDAwOjI5DQpU
bzogQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4NCkNj
OiBNaWNoYWVsIFR1ZXhlbiA8TWljaGFlbC5UdWV4ZW5AbHVyY2hpLmZyYW5rZW4uZGU+OyBGZWxp
eCBXZWlucmFuayA8d2VpbnJhbmtAZmgtbXVlbnN0ZXIuZGU+OyBkaXNwYXRjaEBpZXRmLm9yZzsg
UlRDV2ViIElFVEYgPHJ0Y3dlYkBpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBbcnRjd2ViXSBbZGlz
cGF0Y2hdIERhdGFjaGFubmVsIEhhY2thdGhvbiBhdCBJRVRGIDEwMSA/DQoNCkhpIENocmlzdGVy
LA0KDQpXaGlsZSBJIHRvdGFsbHkgYWdyZWUgdGhhdCBpdCB3b3VsZCBiZSBhd2Vzb21lIHRvIGZp
bmQga2lsbGVyIGFwcHMgZm9yIGRhdGEgY2hhbm5lbHMgSSBkb27igJl0IHRoaW5rIGFuIElFVEYg
SGFja2F0aG9uIGlzIGEpIHRoZSBwbGFjZSB0byBmaW5kIG5ldyBraWxsZXIgYXBzIGFuZCBiKSBj
cmVhdGluZyBzb21ldGhpbmcgYXQgYW4gSUVURiBIYWNrYXRob24gcmVxdWlyZXMgYW4gYXBwIGlk
ZWEgdG8gZXhpc3QgYWxyZWFkeS4NCg0KSXQgd2FzIG15IHVuZGVyc3RhbmRpbmcJdGhhdCBNci4g
UGFudG9uIHdhcyBwcm9wb3NpbmcgdG8gc29sdmUgdGhlIGNoaWNrZW4gYW5kIGVnZyBwcm9ibGVt
IG9mIHBlb3BsZSBjb21wbGFpbmluZyB0aGF0IGNyZWF0aW5nIGRhdGEgY2hhbm5lbCBhcHBzIChv
dXRzaWRlIG9mIGJyb3dzZXJzKSBpcyB0b28gY29tcGxpY2F0ZWQgYnkgaGFja2luZyB0b2dldGhl
ciBhbiBlYXNpbHkgaW50ZWdyYXRhYnRsZSBkYXRhIGNoYW5uZWwgbGliLiBJIHdvdWxkIHRvdGFs
bHkgYmUgdXAgdG8gcGFydGljaXBhdGUgaW4gdGhhdC4NCg0KT25jZSB3ZSBoYXZlIHN1Y2ggYSBs
aWIgd2UgYW5kIG90aGVyIHRoZW4gY2FuIHN0YXJ0IHBsYXlpbmcgYXJvdW5kIGFuZCBtYXliZSB1
bnRpbCB0aGUgbmV4dCBJRVRGIHdlIHdpbGwgaGF2ZSDigJxzb21lIGNvb2wga2lsbGVyIGFwcHPi
gJ0uDQoNCkJlc3QNCiAgTmlscyBPaGxtZWllcg0KDQo+IE9uIEphbiAyNSwgMjAxOCwgYXQgMTM6
MjIsIENocmlzdGVyIEhvbG1iZXJnIDxjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+IHdy
b3RlOg0KPiANCj4gVGhhbmtzIQ0KPiANCj4gSXQgd291bGQgYWxzbyBiZSBpbnRlcmVzdGluZyB0
byBzZWUgc29tZSBjb29sIGtpbGxlciBhcHBzIChvdGhlciB0aGFuIA0KPiBmaWxlIHRyYW5zZmVy
cykgdXNpbmcgZGF0YSBjaGFubmVscyA6KQ0KPiANCj4gUmVnYXJkcywNCj4gDQo+IENocmlzdGVy
DQo+IA0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBNaWNoYWVsIFR1ZXhl
biBbbWFpbHRvOk1pY2hhZWwuVHVleGVuQGx1cmNoaS5mcmFua2VuLmRlXQ0KPiBTZW50OiAyNSBK
YW51YXJ5IDIwMTggMjI6MjcNCj4gVG86IENocmlzdGVyIEhvbG1iZXJnIDxjaHJpc3Rlci5ob2xt
YmVyZ0Blcmljc3Nvbi5jb20+DQo+IENjOiBUIEggUGFudG9uIDx0aHBAd2VzdGhhd2suY28udWs+
OyBGZWxpeCBXZWlucmFuayANCj4gPHdlaW5yYW5rQGZoLW11ZW5zdGVyLmRlPjsgZGlzcGF0Y2hA
aWV0Zi5vcmc7IFJUQ1dlYiBJRVRGIA0KPiA8cnRjd2ViQGlldGYub3JnPg0KPiBTdWJqZWN0OiBS
ZTogW2Rpc3BhdGNoXSBbcnRjd2ViXSBEYXRhY2hhbm5lbCBIYWNrYXRob24gYXQgSUVURiAxMDEg
Pw0KPiANCj4+IE9uIDI1LiBKYW4gMjAxOCwgYXQgMTk6MTQsIENocmlzdGVyIEhvbG1iZXJnIDxj
aHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+IHdyb3RlOg0KPj4gDQo+PiBIaSwNCj4+IA0K
Pj4gSWYgdGhlIHB1cnBvc2UgaXMgdG8gdGVzdCBkaWZmZXJlbnQgZGF0YSBjaGFubmVsIHN0YWNr
cyAoaW4gYWRkaXRpb24gdG8ganVzdCBlc3RhYmxpc2hpbmcgdGhlIFNDVFAtb3Zlci1EVExTIGFz
c29jaWF0aW9uKSwgSSBhc3N1bWUgdGhlcmUgbmVlZHMgdG8gYmUgc29tZSBhcHBsaWNhdGlvbnMg
dGhhdCB1c2UgdGhlIGRhdGEgY2hhbm5lbHM/DQo+PiANCj4+IEl0IHdvdWxkIGJlIG5pY2UgdG8g
aGF2ZSB3ZWJwYWdlIHdoZXJlIHBlb3BsZSBjb3VsZCBhZGQgbGlua3MgdG8gDQo+PiB0aGVpciBh
cHBsaWNhdGlvbnMgdXNpbmcgZGF0YSBjaGFubmVscywgc28gdGhhdCBwZW9wbGUgY2FuIHRoZW4g
Y2xpY2sgDQo+PiA6KQ0KPiBTb21lIGV4YW1wbGVzIGNhbiBiZSBmb3VuZCBhdDoNCj4gaHR0cHM6
Ly9naXRodWIuY29tL25wbGFiL1dlYlJUQy1EYXRhLUNoYW5uZWwtUGxheWdyb3VuZA0KPiANCj4g
QmVzdCByZWdhcmRzDQo+IE1pY2hhZWwNCj4+IA0KPj4gUmVnYXJkcywNCj4+IA0KPj4gQ2hyaXN0
ZXINCj4+IA0KPj4gDQo+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4gRnJvbTogZGlz
cGF0Y2ggW21haWx0bzpkaXNwYXRjaC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgDQo+
PiBNaWNoYWVsIFR1ZXhlbg0KPj4gU2VudDogMjUgSmFudWFyeSAyMDE4IDE5OjQ3DQo+PiBUbzog
VCBIIFBhbnRvbiA8dGhwQHdlc3RoYXdrLmNvLnVrPg0KPj4gQ2M6IEZlbGl4IFdlaW5yYW5rIDx3
ZWlucmFua0BmaC1tdWVuc3Rlci5kZT47IGRpc3BhdGNoQGlldGYub3JnOyANCj4+IFJUQ1dlYiBJ
RVRGIDxydGN3ZWJAaWV0Zi5vcmc+DQo+PiBTdWJqZWN0OiBSZTogW2Rpc3BhdGNoXSBbcnRjd2Vi
XSBEYXRhY2hhbm5lbCBIYWNrYXRob24gYXQgSUVURiAxMDEgPw0KPj4gDQo+Pj4gT24gMjQuIEph
biAyMDE4LCBhdCAxMjoyOCwgVCBIIFBhbnRvbiA8dGhwQHdlc3RoYXdrLmNvLnVrPiB3cm90ZToN
Cj4+PiANCj4+PiBUaGVyZSBoYXMgYmVlbiB0YWxrIG92ZXIgb24gdGhlIHczYyBsaXN0IGFib3V0
IHRoZSBzY2FyY2l0eSBhbmQgdW5zdWl0YWJpbGl0eSBvZiBmcmVlLXN0YW5kaW5nIFdlYlJUQyBk
YXRhY2hhbm5lbCBpbXBsZW1lbnRhdGlvbnMuDQo+Pj4gDQo+Pj4gSSB3b25kZXIgaWYgdGhpcyBp
cyBhIHN1aXRhYmxlIHRhcmdldCBmb3IgdGhlIElFVEYgMTAxIGhhY2thdGhvbj8NCj4+PiANCj4+
PiBUaGUgY2hhbGxlbmdlIHdvdWxkIGJlIHRvIHRocm93IHVwIG9uZSBvciAyIGZyZWUgc3RhbmRp
bmcgDQo+Pj4gZGF0YWNoYW5uZWwgaW1wbGVtZW50YXRpb25zIGJhc2VkIG9uIGV4aXN0aW5nIG9w
ZW4gc291cmNlIHdpdGggQVBJcyB0aGF0IG1pZ2h0IHN1aXQgYXV0aG9ycyBvZiBuZXR3b3JrZWQg
Z2FtZXMgb3IgU0ZVcy4NCj4+PiANCj4+PiBDb21tZW50cz8gVGhvdWdodHM/DQo+PiBXZSBhcmUg
cGFydGljaXBhdGluZyBhbmQgY291bGQgdXNlIHRoZSBGaXJlZm94IFdlYlJUQyBpbXBsZW1lbnRh
dGlvbi4gV2Ugd291bGQgYmUgYWJsZSB0byBkZWJ1ZyBTQ1RQIGlzc3VlcyBhbmQgcG9zc2libHkg
c29tZSBpc3N1ZXMgaW4gdGhlIFdlYlJUQyBpbXBsZW1lbnRhdGlvbiBvZiBGaXJlZm94Lg0KPj4g
DQo+PiBCZXN0IHJlZ2FyZHMNCj4+IE1pY2hhZWwNCj4+PiANCj4+PiBULg0KPj4+IA0KPj4+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4gcnRjd2Vi
IG1haWxpbmcgbGlzdA0KPj4+IHJ0Y3dlYkBpZXRmLm9yZw0KPj4+IGh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vcnRjd2ViDQo+PiANCj4+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiBkaXNwYXRjaCBtYWlsaW5nIGxpc3QNCj4+
IGRpc3BhdGNoQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL2Rpc3BhdGNoDQo+IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPiBydGN3ZWIgbWFpbGluZyBsaXN0DQo+IHJ0Y3dlYkBpZXRmLm9yZw0KPiBo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3J0Y3dlYg0KDQo=