Re: 2hr sessions and agendas

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 25 January 2022 15:39 UTC

Return-Path: <spencerdawkins.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 704B93A0BCB; Tue, 25 Jan 2022 07:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eRpI_8STaUBD; Tue, 25 Jan 2022 07:39:17 -0800 (PST)
Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 749533A0BC8; Tue, 25 Jan 2022 07:39:16 -0800 (PST)
Received: by mail-ua1-x92a.google.com with SMTP id u6so38172458uaq.0; Tue, 25 Jan 2022 07:39:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AnD4ji1QOLBxARZ2i5YD4G45sDM270QtIXpBnveGz0Y=; b=qCU673zdTMqXFjU0gHZNgtfW6BDn6QBIta/1sxWstpJ65wCFUZA55oE3A9bFp4eCBC 5ciPVaJ26cWzyDcQdV/1roT8K2Ttsbv78/kKqV0Q9H3iy1FuGv5/6TTvYZx4FJ3gxmho X2qZd0qpWbWSpzRxd8qWDbZ/COeWE0qHBruh8fz7SPZ0kT1ogzxvvFMlnRQJ9FQcLpB/ vA1e/J+496AEsyDS89kwNy17dKu/rlOnY8Qony2G2evqa5gCq+3tBbrV9FY9enMVMXIH gMU6FXJrAtKQP2cb7D/XbSon/UzWjJWGrpX239id4vv0mtH2mJW92QE6fI1YMdEyLTNb Q8TA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AnD4ji1QOLBxARZ2i5YD4G45sDM270QtIXpBnveGz0Y=; b=a+OwxpGm2/4DDgMCCx6N66uNHFdSdSHLXmecG7Nz7b49rvOWdiNysWTiNoZL6dqGcK OCb3EVhbi1hZPFcDo069Y5GTj6sWKAltIBkTF+Mbo7f+iaFpl72aRpUyXXZjks5fKylS I8ALS4GK6lBa6Uh9kNaqisPFnAI5rUC88Ke61NBum0jG3/s7r8sFoZIZ51uWRKjT4NzU PCqI3qAACAuJ6vHr4fY5gDrwG3+pzXjRwGr6R/GSmU6Jlz9tO064s0HHuLp9e6pH2Zjv a64vpLwAm+2/6NyVa5EJrwJKARL7s7j18DKUm5oSF3oU7EIoH8pbT9EeUEul0641q6Cc SYXA==
X-Gm-Message-State: AOAM530jJSFTdYR2KCKCXerNTclxMdq/aSCisCNcU8980gqQydUvLgC7 6exAha3vcPJt05BQ9Sq9CYFxNMFk7L0c2roX+zea0CkX
X-Google-Smtp-Source: ABdhPJzER5w4QB+iUsiis0Akwfr1ABdMGddSe+6VEyApipmec8YkjWlhirIIwWYp2BqMFqNdx0o5EoJnEObrm/U0szI=
X-Received: by 2002:a67:c98d:: with SMTP id y13mr1779214vsk.43.1643125154337; Tue, 25 Jan 2022 07:39:14 -0800 (PST)
MIME-Version: 1.0
References: <164218658755.25340.17984418230968972509@ietfa.amsl.com> <7812.1642287951@localhost>
In-Reply-To: <7812.1642287951@localhost>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 25 Jan 2022 09:38:48 -0600
Message-ID: <CAKKJt-dgm15AD0QsFQMAqmWa4yUcrkDMxkNC9gGg4hLLEBQ9dQ@mail.gmail.com>
Subject: Re: 2hr sessions and agendas
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Working Group Chairs <wgchairs@ietf.org>, IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000025569f05d669e362"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/HrxzX48GTo2SnhxSh-CP4sfKYk0>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 Jan 2022 15:39:22 -0000

Michael,

I'm backing up to your original suggestion.

On Sat, Jan 15, 2022 at 5:06 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> IETF Agenda <agenda@ietf.org> wrote:
>     > Requests for more than two hours of total meeting time are unlikely
> to
>     > succeed. In special cases, you may request more than two hours of
>     > meeting time, but the IESG will likely request a rationale, and
>     > scheduling pressure may still make it impossible to grant any
>     > additional meeting slots. Please see this email from the IESG [2] for
>     > more detailed guidance on how to structure your session requests.
>
> I want to start by thanking the IESG for being more rigorous here.
>
>
> * I would like the IESG to encourage any WG asking for 2hr (or more)
> present a clear agenda for the time usage*, and that no more than 50%
> that time be for
> presentations and/or status updates.
>

At a minimum, I'd suggest that the IESG (and, of course, Colin for the IRTF
- research groups also ask for slots out of the same pool of slots) ask for
a fairly firm agenda for at least one hour of a two-hour request.

Susan described her working group as using just about every tool a working
group has to move work items forward (discussion slots, side meetings, and
interim meetings) if virtually face to face discussion time is required for
that work item. I'd encourage chairs to consider interims if they need two
or more hours and aren't holding interims now.

*I note that Michael's suggestion was " encourage", not "require". *If your
group falls into this category, your AD/Colin  likely knows that, and it's
unlikely that an AD/Colin would tie a group down in a procrustean bed(*)
because of a rule that only applies 80 percent of the time.

(*) https://en.wikipedia.org/wiki/Procrustes


> The bulk of the time should be for discussion, ideally relating to
> identified
> issues.  I don't think that this is a new request, I just think it's worth
> repeating.
>
> I'd like to suggest that we have no 2hr slots (like we did on Thursday at
> IETF112), and that all requests for 2hrs be turned into two requests for
> 1hr.
>

It's worth noting that all chairs can do this now, with no IESG/secretariat
action required, if that's the right thing to do for your working
group/research group. If it's not the right thing to do, you probably know
that, and your AD (or Colin) probably knows that as well as you do.

My experience (and Gorry has already chimed in on this thread) is that the
secretariat will work diligently to satisfy "special requests" - TSVWG has
been requesting two slots, with at least one day in between, for years - so
I'd expect that if requesting two one-hour slots back to back for your
group is the right thing to do, that will happen if it's at all possible.

So I would encourage all chairs to Do The Right Thing for their groups,
with maybe a little more awareness of the impact of our decisions on other
groups that also need slots taken from a single and limited pool.

Make good choices, of course.

Best,

Spencer


> Even if I don't get to travel in the end, I'm excited for 113.
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        |    IoT
> architect   [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on
> rails    [
>
>