IETF Logo Mail Archive

Re: [irsg] Follow up on disruptive person during IETF 119

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 23 March 2024 22:22 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02095C14F6FC for <wgchairs@ietfa.amsl.com>; Sat, 23 Mar 2024 15:22:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, 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 (2048-bit key) header.d=sandelman.ca
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 Lgces4MUZGlD for <wgchairs@ietfa.amsl.com>; Sat, 23 Mar 2024 15:21:58 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (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 CFE92C14F68E for <wgchairs@ietf.org>; Sat, 23 Mar 2024 15:21:58 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [103.73.84.14]) by relay.sandelman.ca (Postfix) with ESMTPS id A8F641F4A8; Sat, 23 Mar 2024 22:21:56 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="UinCuU1s"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id AC9ACA1913; Sun, 24 Mar 2024 08:21:53 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711232513; bh=pkk5MpyA/3QfJPuoD8bpVhWn8h20FWuSrihCXHzaK+c=; h=From:To:Subject:In-reply-to:References:Date:From; b=UinCuU1saMao5vX5q4v8GzNgTDRxJQ8D5n5vsQnLwAQ6chtTd3wPhPr9++1MFqIWc V2+5WLwGFWE4AgNnmyKLGRWa8EvDkr0o0WaQYaKdi3P1Iqmt7/vRxkwxHjXG7eOkhy uChLB9Y7OCQ44/tWH4N+RvJYmbI0NpvELlRfRbLDlHss9Ht29Q9dkWyhQbfZh9c8KS m994NLEA2uZdPX3a8QeP0DhIHWb+zJdcOqH5N/HOdy7gxcGnkvZsFhUxWgPDQ7D+X/ 5egZ+qMmrKa6sCGvUGdE1ByTPKrQkFOKPt28dna4DKxYvOuXivfBAj6AKUSrH+Wuwm 0rrk8I3hoNv9A==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id AAA46A0012; Sun, 24 Mar 2024 08:21:53 +1000 (AEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF WG Chairs <wgchairs@ietf.org>, team@meetecho.com
Subject: Re: [irsg] Follow up on disruptive person during IETF 119
In-reply-to: <E90FA935-A9E6-4C28-B369-AB7FEED624CC@gmail.com>
References: <5F30A325-7A57-49C5-8FD9-B23ADE8D155B@ietf.org> <54788c60-0612-40f1-8e5c-cec3bb80b826@cs.tcd.ie> <E90FA935-A9E6-4C28-B369-AB7FEED624CC@gmail.com>
Comments: In-reply-to Yoav Nir <ynir.ietf@gmail.com> message dated "Fri, 22 Mar 2024 10:03:36 +0200."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sun, 24 Mar 2024 08:21:53 +1000
Message-ID: <317662.1711232513@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/-3ivT5keMLI2mfU-acaZmsmr6EM>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Mar 2024 22:22:03 -0000

{I didn't keep all the individual CCs}

Yoav Nir <ynir.ietf@gmail.com> wrote:
    > Assuming this is done with a button, it should be straightforward to
    > get a list of those banned over the week.  If someone appears multiple

Perhaps the list should be posted as a form of transparency on actions by
chairs.

    > times, there may be further steps taken by the ombudsteam even without
    > any of the particular chairs requesting it.

It could also be that there is an organized effort against that person, and
it's grounds for appeal.

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

v2.23.0 | Report a Bug | By Email