Re: Postel's Principle and Layer 9 protocol engineering

Dean Willis <dean.willis@softarmor.com> Sun, 06 June 2021 18:48 UTC

Return-Path: <dean.willis@softarmor.com>
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 C5B383A2453 for <ietf@ietfa.amsl.com>; Sun, 6 Jun 2021 11:48:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=softarmor.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 fB1z2w8AhS2n for <ietf@ietfa.amsl.com>; Sun, 6 Jun 2021 11:48:21 -0700 (PDT)
Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (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 BBB0F3A2450 for <ietf@ietf.org>; Sun, 6 Jun 2021 11:48:20 -0700 (PDT)
Date: Sun, 06 Jun 2021 18:48:06 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=protonmail; t=1623005297; bh=ElJSZUEdlcQ+TkvV1OmrZNBxepPh6P24dvfmptwPT1Y=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=pvABqautqJtrzSgpE4H3e5qM5lfF6HkqAyw6UadaPhPfQoVs2TR1crcaBOFPgEk/0 lmMe3cy5vGlVKpandE5DZELf3Bz2ccaXAuPxRGpUo3l8cbe/gZFVB0CZs+ajxgypeO R5EniG/QRYkHGTyogRFdKzKTvFfC0wMJTG5FAMIl/vTvCuLyBCxNOcwELvtI1mt7no nO+rqEhAmxStqwT8oVERSaqaI9C0AHU1DHZBdYOwXpbgRhogLJH6msWInByc3o8C4D WhoXmOJhrLyBIHf0sLf1+uK6BWUI9THFEISiXs6EOGwmRZMjT8/n68HG6alv9/Dwom YdpYLkW6vO6Aw==
To: LMM@acm.org, emil@jitsi.org
From: Dean Willis <dean.willis@softarmor.com>
Cc: jared@puck.nether.net, ietf@ietf.org
Reply-To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: Postel's Principle and Layer 9 protocol engineering
Message-ID: <nE8J3jp6eJyTzNElmPjxf2sbHjkK4C5vC7kUfVvVOdGTBKcSBbvwFnmxrnZBm2q1mhD1BH-p567n_svVXqCSUh12EaXIxcA1apU4GAsSD00=@softarmor.com>
In-Reply-To: <001b01d75aff$b951dff0$2bf59fd0$@acm.org>
References: <001b01d75aff$b951dff0$2bf59fd0$@acm.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_2osskDTOAUTKHNGewwpnat1UpDrO0CndkjCh6BZWIk"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X_AIv1kVJFEpHBH_JNLMGUf_uEk>
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: Sun, 06 Jun 2021 18:48:27 -0000

-------- Original Message --------
On Jun 6, 2021, 1:13 PM, Larry Masinter < LMM@acm.org> wrote:
...

But banning someone is very different from delaying their posting
for a reasonable length of time. Especially if the algorithm used
is clear enough that participants who value the ability to
communicate without delay can readily choose other ways
of expressing their perspective, without resorting to hyperbole.

----

Larry, they didn't "delay my posting for a reasonable length of time. " They permanently blocked my comment, denied the appeal, and banned me from using Facebook for any purpose for 24 hours. As I understand it, they use an escalating scale, so the next time they make this mistake it's a week ban, then two, then a month...

Given that MY current employer (for better or worse) is an agency that literally runs on top of social media platforms, said 24 hour ban literally blocks my income stream and the business operations of my clients. Now, perhaps that's my problem and I have a business Facebook dependency to resolve, which I will do...

But my essential point is that given these sorts of risks the IETF MUST NOT rely on social media platforms -- in particular Facebook (because that's where we have an objective instance to analyze as a threat model) -- where said platform is likely to invoke automated censorship in such a way that users must self-censor commonly used terms of art in order to avoid being expelled from the platform.

Literally last month we were circulating a survey asking people about doing IETF work on social media platforms. And while we have had a few technical discussions on Facebook and other platforms, I don't think we've thought our way through the implications of working that way.

--
Dean