IETF Logo Mail Archive

Re: Follow up on disruptive person during IETF 119

Yoav Nir <ynir.ietf@gmail.com> Fri, 22 March 2024 04:23 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 25395C15108B; Thu, 21 Mar 2024 21:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, 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 IgQSdiM42zh0; Thu, 21 Mar 2024 21:23:39 -0700 (PDT)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 A16A0C14F711; Thu, 21 Mar 2024 21:23:39 -0700 (PDT)
Received: by mail-wm1-x334.google.com with SMTP id 5b1f17b1804b1-414701303f7so16401895e9.2; Thu, 21 Mar 2024 21:23:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711081417; x=1711686217; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=XYyIpvHLLGVvOEKFhEg4tQqn9l2PnBEu3OWSmOtdd5M=; b=X6bp4GxolIm5B1ttzolBoQbdTLNpDyplNzDag4S+Ydo+kMEx18FiHMVsWuPSHgYhtj 5x/Py9a7j6jV6I9SnfDccg6xzNhBxzcs5RBxzW6IkgBr9T+DqfwRVAatkzDyhdKHfdeb dQvv+Z+sUBxYUs3NkCiMJmoO0ln0tJdAFFzSWg5FgWy16LqP5vKB1uzWp/Ukp0xqx0ox 8Fp54JGlVdo8DTP90O9CAmyMN7kcu8p+lokiRRcovo3Ki4na54lFECAHgXYChudZzF3A 4WigKbl+k+6t95OVmpiOT5SeS7uDJUS3fDKUfaMXhZtcSEawMrrgDlFy2oSdv6PxK39W 14Pg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711081417; x=1711686217; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=XYyIpvHLLGVvOEKFhEg4tQqn9l2PnBEu3OWSmOtdd5M=; b=el2ebrCQ6ybpZdd27kdPVBiGk1sr95k/2y9guGP3bIX0SZzvuf4euDD8o+fbzvM/MH HLanDBBdO+8qh2TuhD2QWhAdQTaOPt2y3/j58yh9ocOjrSOQ1eUBjEV/VoF+JDl6qxZo yU/aVmo+KbTYRkkYoByeNXljm0m5XnrlEpc9Zxylvq/TNmM9qiDvZkYfEmw7VcHkvRJ9 omk/7oAtPQVOiwJimulyDNPRC8maoBcVvJXMbl+G0BEphvDNursnsyS/7GigzBXy+Rwd HFm87xUVpkUahqJU8qb0u2QsKpEn7TfQqUM29Ueq6Nw+5NuiUGIa8SyLfqwDMoUf7UUV 5Zxw==
X-Forwarded-Encrypted: i=1; AJvYcCXOImRK/9upZDpRZ+XWDyv6OmF7yr6DW9BQH7ErgkijFPu/HzbjB8MhG9eMkiTz27YqGsytc30M78olgl2fm0Rttw==
X-Gm-Message-State: AOJu0YwQEnxJRFtuTamZOFdRrblKNVkmHxfhqocKYwL3JpopU/N7Az1i ivDb8Bd+xRs0tIDTF1o87zOuRLGc5K3uxI7eXgIU+YM4rLbvAuqE
X-Google-Smtp-Source: AGHT+IGWBtQnN97IAe3RuWHHPpM3SHoZyV4/dimkIQN3tNddRFU+X27iSiYEhcyJjlsey+uuLSKC1Q==
X-Received: by 2002:a5d:6949:0:b0:33e:9be0:6851 with SMTP id r9-20020a5d6949000000b0033e9be06851mr918593wrw.12.1711081416988; Thu, 21 Mar 2024 21:23:36 -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 o20-20020a5d58d4000000b0033e7503ce7esm1086835wrf.46.2024.03.21.21.23.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Mar 2024 21:23:36 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Re: Follow up on disruptive person during IETF 119
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <236634.1711081068@dyas>
Date: Fri, 22 Mar 2024 06:23:25 +0200
Cc: Jay Daley <exec-director@ietf.org>, IETF WG Chairs <wgchairs@ietf.org>, Laura Nugent <lnugent@amsl.com>, team@meetecho.com, Robert Sparks <rjsparks@nostrum.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3251BE7-CAD5-4EAF-9ED5-ADD6CC068724@gmail.com>
References: <5F30A325-7A57-49C5-8FD9-B23ADE8D155B@ietf.org> <236634.1711081068@dyas>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/3Y-NcqLrszykOqebRv_RmLomaSk>
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 04:23:40 -0000


> On 22 Mar 2024, at 6:17, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Leaving all the CCs, but not sure I should.
> 
> Jay Daley <exec-director@ietf.org> wrote:
>> 3.  For single session removal this new process can be invoked by a WG
>> chair (of the session) or an AD, contacting the Secretariat.
> 
> Does this mean an email to the secretariat?  OR is it a button?

It has to be a button. If someone is disrupting my session *now*, composing an email to the secretariat is not a timely response.

Maybe a “@meetecho: please ban so-and-so”, but better a button.

We already have buttons to turn off someone’s mic or video, but those are for the case where someone forgot to turn off their mic and now we all hear their dog barking. I have done that - youtube has evidence.  But those buttons don’t prevent them from turning their mics back on.  I think that is what is missing.

> For virtual interim meetings, we might well be in a timezone that is not 9-5 Pacific.
> (sharing the pain!)
> 
> If it's a button, it needs to be unclickable, because OOPS.

Yes, it would be an oops ot ban the next presenter.

Yoav

v2.23.0 | Report a Bug | By Email