Re: BCP 83 PR actions and new media
Pete Resnick <resnick@episteme.net> Sat, 12 November 2022 19:11 UTC
Return-Path: <resnick@episteme.net>
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 E6631C14CE30; Sat, 12 Nov 2022 11:11:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=episteme.net
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 sZlel2xF2qdi; Sat, 12 Nov 2022 11:11:17 -0800 (PST)
Received: from helm.helm.episteme.net (helm.helm.episteme.net [209.51.32.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BC49C14CE2A; Sat, 12 Nov 2022 11:11:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=episteme.net; s=mail; t=1668280275; bh=EFQ404svUTz+vqXEhF8mO5nW1lM5Rp6LlxVluarGe6o=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=hy9VoZHEOFDfce3AiaYm+J0WS5216wr+otL2H4cFagbiDmLEmF+cdl0nMfQ50mJsg uRUl9Y9D9iFGfrKHYeeI9eDYxQMAehvzQxaKbugNXjLcmzE4Wm/11l4ceTVDmMsVOP cU7JAJGGdvYrvKuS5kafVdPrOe4/3cmw1ON6bJRI=
From: Pete Resnick <resnick@episteme.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Lars Eggert <lars@eggert.org>, Samuel Weiler <weiler@csail.mit.edu>, IESG <iesg@ietf.org>, ietf@ietf.org
Subject: Re: BCP 83 PR actions and new media
Date: Sat, 12 Nov 2022 19:11:07 +0000
X-Mailer: MailMate (1.14r5926)
Message-ID: <7D5F251A-A943-42E3-804B-45C38DD7F807@episteme.net>
In-Reply-To: <971a6923-4819-4b1a-6923-7d9a5cf57d1c@gmail.com>
References: <e9c50be7-3dcf-cdf5-005b-f46a0777b04a@w3.org> <6a4f347a-673e-5a2f-8864-5a26ff88e940@csail.mit.edu> <9D94F03D-2BF1-4034-B362-87063DEDA2E9@eggert.org> <971a6923-4819-4b1a-6923-7d9a5cf57d1c@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/woO6ZhlDM65QfNQYBOlaiSBDzMs>
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: Sat, 12 Nov 2022 19:11:22 -0000
On 10 Nov 2022, at 19:50, Brian E Carpenter wrote: > (Note that the anti-harassment policy is scoped: "IETF participants > must not engage in harassment while at IETF meetings, virtual > meetings, social events, or on mailing lists." Maybe that needs to be > slightly extended to cover other IETF communication media.) Note that the Anti-Harassment Procedures are part of BCP 25 and define the actions of the Ombudsteam, not BCP 83 and therefore do not necessarily apply to communications subject to a PR-Action we are talking about in this thread. However, to address the bit of ambiguity in 7776 that Brian refers to, the document says: ...[RFC7154] provides a set of guidelines for personal interaction in the IETF, and [RFC2418] and [RFC3934] give guidelines for how to deal with disruptive behavior that occurs in the context of IETF working group face-to-face meetings and on mailing lists. However, there is other problematic behavior that may be more personal and that can occur in the context of IETF activities (meetings, mailing list discussions, or social events) that does not directly disrupt working group progress but nonetheless is unacceptable behavior between IETF Participants. The phrase "in the context of" gets used further down as well: In general, disruptive behavior that occurs in the context of an IETF general or working group mailing list, or happens in a face-to-face or virtual meeting of a working group or the IETF plenary, can be dealt with by our normal procedures, whereas harassing behavior is more appropriately handled by the procedures described here. However, there are plausible reasons to address behaviors that take place during working group meetings using these procedures. When the draft of this document was discussed by the IETF list (in Last Call and prior), examples given in the discussion included things like misbehavior in the hotel bar after sessions were done for the day, or in the hall before or after a meeting, and certainly private email exchanges that came out of a public WG mailing list exchange. (References to particular email messages in that discussion can be provided upon request.) I have always understood "in the context of" to include such private email messages or after-hours in-person activities, and I believe that was the understanding of those who discussed it during Last Call. But again, this doesn't apply to the BCP 83 discussion on the table. pr -- Pete Resnick https://www.episteme.net/ All connections to the world are tenuous at best
- Re: BCP 83 PR actions and new media Keith Moore
- BCP 83 PR actions and new media Samuel Weiler
- Re: BCP 83 PR actions and new media John C Klensin
- Re: BCP 83 PR actions and new media Lars Eggert
- Re: BCP 83 PR actions and new media Abdussalam Baryun
- Re: BCP 83 PR actions and new media Keith Moore
- Re: BCP 83 PR actions and new media Joel Halpern
- Re: BCP 83 PR actions and new media Samuel Weiler
- Re: BCP 83 PR actions and new media Lars Eggert
- RE: BCP 83 PR actions and new media Rob Wilton (rwilton)
- RE: BCP 83 PR actions and new media Maisonneuve, Julien (Nokia - FR/Massy)
- RE: BCP 83 PR actions and new media Maisonneuve, Julien (Nokia - FR/Massy)
- Re: BCP 83 PR actions and new media Ofer Inbar
- RE: BCP 83 PR actions and new media Daniele Ceccarelli
- RE: BCP 83 PR actions and new media Daniele Ceccarelli
- Re: BCP 83 PR actions and new media Paul Wouters
- Re: BCP 83 PR actions and new media Keith Moore
- Re: BCP 83 PR actions and new media Brian E Carpenter
- Re: BCP 83 PR actions and new media Keith Moore
- Re: BCP 83 PR actions and new media Brian E Carpenter
- Re: BCP 83 PR actions and new media Lloyd W
- Re: BCP 83 PR actions and new media Abdussalam Baryun
- Re: BCP 83 PR actions and new media Keith Moore
- Re: BCP 83 PR actions and new media Pete Resnick
- Re: BCP 83 PR actions and new media Stephen Farrell
- Re: BCP 83 PR actions and new media Toerless Eckert