IETF Logo Mail Archive

Follow up on disruptive person during IETF 119

Jay Daley <exec-director@ietf.org> Fri, 22 March 2024 01:03 UTC

Return-Path: <jay@staff.ietf.org>
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 74D6EC14CE31 for <wgchairs@ietfa.amsl.com>; Thu, 21 Mar 2024 18:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20230601.gappssmtp.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 n6wkEK8VTW34 for <wgchairs@ietfa.amsl.com>; Thu, 21 Mar 2024 18:03:42 -0700 (PDT)
Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (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 0AC59C1D4A60 for <wgchairs@ietf.org>; Thu, 21 Mar 2024 18:03:42 -0700 (PDT)
Received: by mail-pl1-x629.google.com with SMTP id d9443c01a7336-1e07cd7b798so8072575ad.2 for <wgchairs@ietf.org>; Thu, 21 Mar 2024 18:03:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1711069421; x=1711674221; darn=ietf.org; h=to:cc:date:message-id:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=eIRJbyiiaNvs5yiHR50X3GM+Xu5QQzbWtTl/whjmSHU=; b=GEsI5PduCgydO4e7NdUknAdrdMJIfDsIbKSVxARxrCLV2ssy8tcDYkJacLvHTtZ9bH 0quo/ovxhljG2QaE5xnntkdisdsK8qsn8EElCk/g+OCGeaCX9lMTviD61RldBAVNilSw rWagZyBMqoqpTZDkyYKGu0GCaqzD+7qRWJ+/vnUnx5GG3gg7uTkjlod+sh/qP2rkf5h5 y1hjN1z3RPSQt+Os46lQ4XkBa6LoXG9UdnqVJG6wecDfPL1lWZUVJyHEvHBNJPpENZBe jhznNpBF+Ovl0pMuRqFYDosi1u1d3yS/znoU9iYJUy1Zpl8/ZLOQC3UY/VQd3Vb67ech J14w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711069421; x=1711674221; h=to:cc:date:message-id:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=eIRJbyiiaNvs5yiHR50X3GM+Xu5QQzbWtTl/whjmSHU=; b=cMcJIukmiK6R4jeUZgPSeVXnLlQ9RMB6gJf88ck50HqKmJYLR1su1wU+G6o+zBxEGG 4iBFTGbe4oCrt5TEInWAeqTHqj7aGsxrDIQ3wOAlQ3gR+gEei5vYcygkEPmmurmIZ3xo f71LwBYYqEEK7TuPZPPZ0Yx0tGkwqwTWnXkfGxpmRE1Ry0Y0t3Mcq0Ky2NEN8c1QlLpK UDrD4JauaL0p4q5mX3IXp6DqEUaPHwB/ed8aGOrYgWX6RtJGu5OHT7a9ATXRM8Ij6rWy +dVjGNyXChWv7jyDjfzkt+eXx0Y4SsLwwlRJZWZP8ZRgApU/C5B33wnhM1vd7ZkfmNxN kNLQ==
X-Gm-Message-State: AOJu0Yxz0FVJ6Zjljh2J70FDssqPJqURlKVDWWL8glfJrvsloG2QdzaD xRgRTwT3mrHr2SSEMXcl6Ndwdvl/bcJonjht0e07PmeIvXqPByMD77EyS0aZRDYO5cf58JQ7pGU ZWjni3thG
X-Google-Smtp-Source: AGHT+IEbfMqVnR/xIQ80/AuK4La5lnNfhsRiQWdyP06MjQQyqAHlYXxuIoV7o7+wCF/YfuwkDfmMsw==
X-Received: by 2002:a17:902:d54c:b0:1e0:384:ecb9 with SMTP id z12-20020a170902d54c00b001e00384ecb9mr1342655plf.8.1711069421143; Thu, 21 Mar 2024 18:03:41 -0700 (PDT)
Received: from smtpclient.apple ([2001:67c:370:128:d196:de0:bd1f:417]) by smtp.gmail.com with ESMTPSA id f6-20020a170902ce8600b001ddb505d50asm505639plg.244.2024.03.21.18.03.39 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Mar 2024 18:03:40 -0700 (PDT)
From: Jay Daley <exec-director@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Subject: Follow up on disruptive person during IETF 119
Message-Id: <5F30A325-7A57-49C5-8FD9-B23ADE8D155B@ietf.org>
Date: Fri, 22 Mar 2024 11:03:27 +1000
Cc: Laura Nugent <lnugent@amsl.com>, Stephanie McCammon <smccammon@amsl.com>, team@meetecho.com, Robert Sparks <rjsparks@nostrum.com>
To: IETF WG Chairs <wgchairs@ietf.org>, The IESG <iesg@ietf.org>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/IM7UwtByw9eYIlro43C1lgygtF0>
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 01:03:47 -0000

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.  

The meetings team (LLC, Secretariat, NOC, Meetecho, Tools) have discussed this and we propose the following way forward to manage similar instances in the future.

1.  Maintain a trust-based approach with an exception process, rather than introduce new controls to lock/unlock a whole session.  We think approach both maintains the permissive culture of the IETF and avoids extra complexity for WG Chairs.

2.  Add a new feature in Datatracker that allows the Secretariat to remove a participant from a session and more permanently.  The technical details here are that this feature will revoke their registration permissions and call a Meetecho API to remove them. 

3.  For single session removal this new process can be invoked by a WG chair (of the session) or an AD, contacting the Secretariat.  Permanent removal can only be authorised by me or Roman, normally after rapid consultation with the IESG.

Does this work for everyone?

Jay

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org

v2.23.0 | Report a Bug | By Email