Re: BCP 83 PR actions and new media

Joel Halpern <jmh@joelhalpern.com> Thu, 10 November 2022 10:15 UTC

Return-Path: <jmh@joelhalpern.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 89F60C14F73F for <ietf@ietfa.amsl.com>; Thu, 10 Nov 2022 02:15:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6BKWCWz5Z0ey for <ietf@ietfa.amsl.com>; Thu, 10 Nov 2022 02:15:00 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0136CC14F720 for <ietf@ietf.org>; Thu, 10 Nov 2022 02:14:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4N7Hl75BsTz6G7lG; Thu, 10 Nov 2022 02:14:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1668075299; bh=55eAA4LiWgEA3uLzsHrMA8nCum8fqmVWVvCuSkwbEmk=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=dxUxQdXRzIh6y7ISLF+HSpbyQ1Ky3HFUp+e4HXGvf979hvps6cyqQcxzKXdHoMRsj 6YMgH8ezukL2pzKJ7LugohYqXolhhNTEfrIesk15WNHJ+Sw2LYpB22O4QUoFqi5+W1 u7Ct8bY3804WOXqhgf+ZhfrBSlBD0itReILt5xRY=
X-Quarantine-ID: <8rkUgUALchXE>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [31.133.149.170] (dhcp-95aa.meeting.ietf.org [31.133.149.170]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4N7Hl65zwQz6G7gq; Thu, 10 Nov 2022 02:14:58 -0800 (PST)
Message-ID: <778eb912-30be-78b6-89d2-c019e1b403ab@joelhalpern.com>
Date: Thu, 10 Nov 2022 05:14:56 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
Subject: Re: BCP 83 PR actions and new media
Content-Language: en-US
To: Keith Moore <moore@network-heretics.com>, Lars Eggert <lars@eggert.org>
Cc: ietf@ietf.org
References: <e9c50be7-3dcf-cdf5-005b-f46a0777b04a@w3.org> <2e0392cd-6021-2d38-5d7f-ab1925ccbc16@network-heretics.com> <96420B07-AD5B-47A5-8D90-ACDDAF7F0F0F@eggert.org> <fef28c1d-4e5d-2120-7b9d-3dcfde34eb75@network-heretics.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <fef28c1d-4e5d-2120-7b9d-3dcfde34eb75@network-heretics.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L78yu0yZZhcgrkN26wmAvfjubXc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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, 10 Nov 2022 10:15:04 -0000

I do not see how the IETF can take any role or position regarding 
private communication.  One can argue that private communication may be 
relevant evidence for judging public behavior, but that is very tricky.

Yours,

Joel

On 11/10/2022 5:11 AM, Keith Moore wrote:
> On 11/10/22 03:25, Lars Eggert wrote:
>
>> PR actions per BCP 83 can only be used in response to on-list 
>> behavior. I agree this is far from ideal as our participation 
>> channels have multiplied.
> Right, I was asking about what "should" be the case, since there seems 
> to be some interest in revising BCP 83.   I'm not sure what I 
> personally believe should be the case, since I think there's some 
> utility in people being able to speak their minds freely, and private 
> communications are less likely to be disruptive than public 
> communications.   On the other hand, in recent years it has seemed 
> that sometimes people collaborate to pressure or even harass people 
> via private email, and on occasion this practice even seems to have 
> been driven by management.   If nothing else such a practice lacks 
> transparency.
>
>> If you feel you are being harassed as an IETF participant in general 
>> and/or in ways other than on mailing lists, please see the IETF 
>> Anti-Harassment Policy [1], i.e., contact the IESG or - if privacy is 
>> a concern - the ombudsteam [2].
>
> I'm aware of those mechanisms, but in my limited experience with them 
> they've worked rather poorly, and (at least at that time) were clearly 
> not operated independently of IETF management.
>
> Keith
>
>