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

Yoav Nir <ynir.ietf@gmail.com> Fri, 22 March 2024 08:03 UTC

Return-Path: <ynir.ietf@gmail.com>
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 323BFC14F6B7; Fri, 22 Mar 2024 01:03:52 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 lNyX97Tp14z8; Fri, 22 Mar 2024 01:03:50 -0700 (PDT)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 4E76FC14F5FE; Fri, 22 Mar 2024 01:03:50 -0700 (PDT)
Received: by mail-wm1-x331.google.com with SMTP id 5b1f17b1804b1-4146a1ac117so10881685e9.0; Fri, 22 Mar 2024 01:03:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711094629; x=1711699429; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=SEPMdnlO3C5g4f764Qmk3NhI6u0egqCGeNM8wQEr0JI=; b=Lyp46CSbesXZ0T8OOiTuJIr378TJrLQyc6U1cW3+oiQxkvw+P8I/wuck9XIGZlhzc/ QbBp2Pmhgc5Nuc/2Ugli1bU/EKWicLpVbBkIuctL0VIRSM9ScM7QB7lf27tuXQn9gHEg Nkd9fI04gA3JghlMZvuTH780GE2uQDpwifV8BASPqlbUcT5+Etcc7Xm3FtDihdn1NzGf gqfWlhuZuSYsiuMo6YnbxEmSZYBvfb48RK/pVGqw91PHiznuiVI/QwNmNr++Uum2xki2 rfBr6ym8OShRSKmU84m5XHnBmltH96vXMhMo3rKGgOXdLthsho19jNG7Gq+73aBMzkdj 0CHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711094629; x=1711699429; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=SEPMdnlO3C5g4f764Qmk3NhI6u0egqCGeNM8wQEr0JI=; b=ElZ6lN98k9GjccQLO9nvslqr9FYhkDv+ByKIf5EZ24LIYTL5A+5lsFOvVwQxXcuPsY DP/tWJPVMt2swg7pQhYsMURn2IRLh7lnTpZxgAVfVrmAARbpnjgsy6Lnuk86X+nJvmRa v3QTfQZTgsQCzugCb5h7gfmi3TlSvQModIwqVyAVk7xU3zrUUjYO3H2Aj7quc2l04w6T M2xLIRQ1Rnn1+nwSsHbTQRGOZz0tJ7NE/uy1+MX23UO6PBMOvO0wuIyVmY3w41QCd7fh ROde1ygp5HZz0+Mkcm0Enj3XSWwRzU2fLnVsrkjgygZD874mq8USwgrJP0aEitXEu0EF ldBw==
X-Forwarded-Encrypted: i=1; AJvYcCWjoUVBBVefFyE+LhOd4MH32yzHB/tJT4Q+WtEoJtEc2MaFvJglQMGQpc1S1JSCqO4GxX/sUDUUvZSoIsnD3JqNrZ05RweCDDR1mMgCEicXuQ==
X-Gm-Message-State: AOJu0YzKGb8t37IpU3UGivTqvvXfYPoVbQQWec3CzkHfai4yu1BsVlwd 04DTQe8Q8n3gkwj4hj+67uqUPiEdyP5BvyhlB3QvIQBtPyEu2QMQ5UtKPQQiE3k=
X-Google-Smtp-Source: AGHT+IHv5L5Xvhh0le4wmBSy4uzmbJLEIRcBP1668bngW+Hldx9FkQl2vt9Gq0/A1DojPUbSDVJOoQ==
X-Received: by 2002:a05:600c:1c27:b0:413:fdc2:d9da with SMTP id j39-20020a05600c1c2700b00413fdc2d9damr976552wms.12.1711094628407; Fri, 22 Mar 2024 01:03:48 -0700 (PDT)
Received: from smtpclient.apple (84.94.37.215.cable.012.net.il. [84.94.37.215]) by smtp.gmail.com with ESMTPSA id n21-20020a05600c4f9500b0041468961233sm8072488wmq.35.2024.03.22.01.03.47 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Mar 2024 01:03:47 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <E90FA935-A9E6-4C28-B369-AB7FEED624CC@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0EDE07B1-C60E-4D03-973E-836670115A1A"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Re: [irsg] Follow up on disruptive person during IETF 119
Date: Fri, 22 Mar 2024 10:03:36 +0200
In-Reply-To: <54788c60-0612-40f1-8e5c-cec3bb80b826@cs.tcd.ie>
Cc: Jay Daley <exec-director@ietf.org>, IETF WG Chairs <wgchairs@ietf.org>, The IESG <iesg@ietf.org>, Robert Sparks <rjsparks@nostrum.com>, Laura Nugent <lnugent@amsl.com>, team@meetecho.com
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <5F30A325-7A57-49C5-8FD9-B23ADE8D155B@ietf.org> <54788c60-0612-40f1-8e5c-cec3bb80b826@cs.tcd.ie>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/o4Kqp0jBRRTehyAS6tmrBuRomns>
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: Fri, 22 Mar 2024 08:03:52 -0000


> On 22 Mar 2024, at 7:39, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> 
> Hiya,
> 
> On 22/03/2024 01:03, Jay Daley wrote:
>> IESG / WG Chairs
>> The background here is that we had one individual disrupt a number of
>> sessions, including the plenary, and we were required to first
>> temporarily ban them and then permanently ban them.
> 
> I support the various ideas as to session chairs being able to
> handle situations like this better and am fine if those evolve a bit
> over time.
> 
> But, I have a question: what does "permanently" mean in the above, for
> this person? My impression was of an individual who was confused about
> how to interact with the IETF and perhaps additionally confused as well.
> I'm not sure that their behaviour from this week warrants a lifetime
> ban from the IETF, in fact, I'm pretty sure it ought not.

I think for a session chair (WG or BOF), “permanent” should mean for the remainder of that particular session. If it happens once, then that’s all there is to it, unless the chair wants to take it further through ombudsteam, the IESG, or whatever.

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 times, there may be further steps taken by the ombudsteam even without any of the particular chairs requesting it.

Just my 2 cents

Yoav