IETF Logo Mail Archive

Re: IETF Slack workspace

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 28 August 2020 19:12 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE1833A08EC for <ietf@ietfa.amsl.com>; Fri, 28 Aug 2020 12:12:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 YTjFvK-CX0WR for <ietf@ietfa.amsl.com>; Fri, 28 Aug 2020 12:12:58 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 429163A08E1 for <ietf@ietf.org>; Fri, 28 Aug 2020 12:12:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 91CB0389C4; Fri, 28 Aug 2020 14:51:56 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mnrRDaXbc9tQ; Fri, 28 Aug 2020 14:51:56 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9F36B389C2; Fri, 28 Aug 2020 14:51:55 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 99F7AB3; Fri, 28 Aug 2020 15:12:55 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>, Yoav Nir <ynir.ietf@gmail.com>, Keith Moore <moore@network-heretics.com>, ietf@ietf.org
Subject: Re: IETF Slack workspace
In-Reply-To: <D8AC7992-D2A8-454E-9B7E-AF22C8E11FD5@tzi.org>
References: <3064c634-3958-f5e3-26c2-cdd148a86605@tenghardt.net> <CAL02cgTcdFm6y2PtfznAQz2fVNiNNgx3c-ah2WMmTk82KvL_HA@mail.gmail.com> <CAL02cgR0=c2KXhWpqcNRggQmGVT7Z2k6sApi9PV-8ASWec2H-A@mail.gmail.com> <EB92BDC3-3AC1-45EE-B071-0755D2056632@live555.com> <20200827185555.GA18167@gsp.org> <b1de3da1-2f3d-0f6f-cbe8-fb927e637493@network-heretics.com> <CABN_Fg9y3sRRhYmH21=419kKMQCQZdHqdYnWo-XmtVEL7gBs6Q@mail.gmail.com> <D2A98A88-2B68-46F3-97AC-CCA52313B4CB@gmail.com> <D8AC7992-D2A8-454E-9B7E-AF22C8E11FD5@tzi.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 28 Aug 2020 15:12:55 -0400
Message-ID: <8432.1598641975@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JilqYoPICB3S3vlj6HYGHprfa_w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Aug 2020 19:13:00 -0000

It feels like a major argument for slack is that offers reliable sign up for
people who don't know how to find a jabber server, and/or who are unable to
run an XMPP client.  I use pidgin/libpurple, and I know that there were times
when there were significant security issues with it.  I've heard that on
Mac that there is not really a (thick) client that has reasonable support.

So it seems to me that:
1) the IETF should run a jabber server to which we can register to using
   our DT login. (through OpenID Connect, I guess)

2) that the IETF should host one or more web based XMPP clients, possibly
   paying a license fee/support.

Slack supported XMPP in/out when it first launched, but then stopped.
I've been told that this is actually configurable on a per-workspace basis.
I don't know the truth of this.

It would ideal if Slack could XMPP s2s out to IETF jabber servers, but
I would not be surprised if this is not supported.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email