Re: IETF Slack workspace

Carsten Bormann <cabo@tzi.org> Thu, 27 August 2020 22:03 UTC

Return-Path: <cabo@tzi.org>
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 9BF413A13B2 for <ietf@ietfa.amsl.com>; Thu, 27 Aug 2020 15:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 WBpXy4yQaU0b for <ietf@ietfa.amsl.com>; Thu, 27 Aug 2020 15:03:39 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB8843A13B5 for <ietf@ietf.org>; Thu, 27 Aug 2020 15:03:39 -0700 (PDT)
Received: from client-0051.vpn.uni-bremen.de (client-0051.vpn.uni-bremen.de [134.102.107.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4BcxZJ3XdxzySG; Fri, 28 Aug 2020 00:03:36 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: IETF Slack workspace
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20200827185555.GA18167@gsp.org>
Date: Fri, 28 Aug 2020 00:03:36 +0200
Cc: ietf@ietf.org
X-Mao-Original-Outgoing-Id: 620258616.066945-2a9f677115d701f13b11f187d4d88029
Content-Transfer-Encoding: quoted-printable
Message-Id: <6941BA3D-0F25-4992-8C23-668F07A9D55A@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>
To: Rich Kulawiec <rsk@gsp.org>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LBiM5YdDaQDWKEqVrONJg4pbi3c>
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: Thu, 27 Aug 2020 22:03:43 -0000

On 2020-08-27, at 20:55, Rich Kulawiec <rsk@gsp.org> wrote:
> 
>> What assurances do we have about what ???Slack, inc.??? will (or will not) do with these email addresses?
> 
> The answer is "none whatsoever”

Yes.

This is somewhat mitigated by the fact that active participation in the IETF already makes public the mail address you use for that (mail archive, “author’s addresses” in the draft), so I don’t see a lot of downside to giving them out directly to another entity.

In the computer science/math department of the university, we are very careful about forcing the students into handing out PII to third parties (*), so we run our own mail, seafile, IaaS, LMS, gitlab, hackmd, mattermost, rocket-chat, etc (partially departmental, partially in the computer center).  (The university as a whole seems to be less shy about this, but that is a different issue.)  In the IETF, transparency issues may make those privacy issues mostly moot, more so than we probably would like it to be.

Grüße, Carsten

(*) Note that any third party can (and quite likely will) go evil if it goes bankrupt.  I don’t think our legal department knows why you’d want to have bankruptcy clauses in any self-respecting contract, and we wouldn’t get those from the commodity services anyway.