Re: [irsg] Closing the queue

Spencer Dawkins at IETF <> Fri, 30 July 2021 20:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EF4163A0E1A for <>; Fri, 30 Jul 2021 13:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qvlcCRCLbNy4 for <>; Fri, 30 Jul 2021 13:15:57 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::e2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 53B203A0E17 for <>; Fri, 30 Jul 2021 13:15:57 -0700 (PDT)
Received: by with SMTP id u11so3644135vst.12 for <>; Fri, 30 Jul 2021 13:15:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BSGoC40WFNEDlys5W/F0GF8pzNjiTx/ebZlGMi6Yjd4=; b=n9CMQRAznHX6Tl5How4MH+xSGh0BYxptR17GI3rNIOkqPziXgrs2qGp0v3ii0AmDNG uW6nq/P4LMxm5CuDGDC3EXE0HoS3XZCx+ZjG7df+/YG/YSE/h3jJAycDLv/x0BwJkfOA NBcNx3l4iYnM12Br2dyP+v52636hI7CoRty0oMUpOe2Na/8xYrhkyvFWpucmgd96zM/R NpdJRdHZmU8rlReILKfzGBqFOyX7PpCkxD/PxIE0xNiXdWAVqFxFU0WUmIXxcoYwW9Ob tdlVtqmtoESbOH9p819WWSzrI3K9l1/5cwePUTV8Lb8QlrCvpq3sW0njxyOfMN+RrX3k 0ftA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BSGoC40WFNEDlys5W/F0GF8pzNjiTx/ebZlGMi6Yjd4=; b=n6lxwRjcTX9oiCgYgKRLV6KLb2l+mSCvaPc7RDvTTpAiphQ5fKGHBRMDMiO7uhz7II CNJ3Q3hV/udD8HPE56v8IoxuScOOewcE49COvTWRJfg7Cb/o5rooWN4qt/G4X5fLXbOn 3/2eaax5H/ASyXZti2NY8DNMZBWl0vxbw4k/MvuALe0IMnyAmafe5LBQH0q+O3VsNIvD b21keZrfnmdPK6i5vxfCBjKyHmGcu6OgONKqOe95Lyz/go3Ici3MQ6o0WixCqZhbR0oU knU56iKG1j6sIrd5zLIB9xI4r9WD5dvsuXHNiThRpPpwfg+5Z+PTrz3yW5e129jX4i4S 2Lcw==
X-Gm-Message-State: AOAM533IYyUZ2+M5p1S69MTwdQMUY46r27SzyX44GqOQJ224btfzqeDU jmQ7Vnt8oqy88sPyDzSVBlL8zpwq/Sq4ToetZKk=
X-Google-Smtp-Source: ABdhPJyo2zE6QvPnV/c5jgEoa+V9qqWFZqfgIKeu+WQEh7uts9mEKwoafSJZVvwnyxrhLheln54sBqFU2V3EPegwUsY=
X-Received: by 2002:a67:fb55:: with SMTP id e21mr3894771vsr.46.1627676155462; Fri, 30 Jul 2021 13:15:55 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <>
In-Reply-To: <>
From: Spencer Dawkins at IETF <>
Date: Fri, 30 Jul 2021 15:15:29 -0500
Message-ID: <>
Subject: Re: [irsg] Closing the queue
To: Carsten Bormann <>
Cc: Bob Hinden <>,
Content-Type: multipart/alternative; boundary="0000000000000e4a2005c85ce34a"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 30 Jul 2021 20:16:03 -0000

Just following up on these excellent suggestions ("do the right thing", of

I totally agree with Jen on having a button to "close the queue", whether
that's a "hard close", so you can't ignore the close, or a "soft close",
that (new variant) flags the people who added themselves after the line was
closed, but We All Know What You Did Last Session.

If I might make another queue-related suggestion - there are chairs who are
un-distracted enough to consistently remove people from the queue when
they're speaking, but that's asking the chairs to watch ANOTHER thing
during the session, so often, it's up to us to remove ourselves from the

For me, that means "turn off my raised hand to get out of the queue when
I'm recognized, AND turn on my audio, AND turn on my video if we seem to be
doing that", followed by "turn off my audio, AND turn off my video", or
some variation thereof.

I can't count the number of people this week who

   - turned on the video and started talking with no audio, OR
   - turned on the video and audio and started talking, and only turned off
   one of them, OR
   - my personal favorite - turned off audio and video, and left themselves
   in queue, but since no one else was in queue, the chair didn't realize that
   until the next presentation started and the chair had time to look at the
   queue, and then message *me* privately and say "can you ask that question
   during the general Q&A?" and I had literally no idea what Lars was talking
   about during the plenary (I can't count that one, but I know the number was
   at least "one") 😂

It seems that there are higher level operations that we could be looking at
here ...



On Fri, Jul 30, 2021 at 7:46 AM Carsten Bormann <> wrote:

> On 2021-07-30, at 05:16, Bob Hinden <> wrote:
> >
> > I agree this would helpful.   It will, of course, require the chair(s)
> to remember to turn the queue back on for the next presentation.
> It is probably better not to “close the queue” (i.e., make the hands-up
> button inactive), but simply to change the color of the next hands-up entry
> that is made.  Rotate through 3-4 colors (yes, lightnesses, hatchings, …),
> and we should be safe.  If these were formal meetings, we’d need
> double-hands (point of order) as well…  and same topic/other topic...
> (Ceterum censeo: And move the damn thing BELOW the current speaker.)
> Grüße, Carsten