IETF Logo Mail Archive

2hr sessions and agendas

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 15 January 2022 23:06 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 6941C3A0EC0; Sat, 15 Jan 2022 15:06:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level:
X-Spam-Status: No, score=-7.099 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, RCVD_IN_DNSWL_HI=-5, 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=sandelman.ca
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 2lm4Wp3Bu8Mz; Sat, 15 Jan 2022 15:05:58 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD90F3A0EBF; Sat, 15 Jan 2022 15:05:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 6996A38A51; Sat, 15 Jan 2022 18:12:04 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HxlxXHmYV2TN; Sat, 15 Jan 2022 18:12:00 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5EF6138A50; Sat, 15 Jan 2022 18:12:00 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1642288320; bh=gJFCv9qcUH5U6SHubh5/ze3klFkncHT7n8N7QhNxrSc=; h=From:To:Subject:In-Reply-To:References:Date:From; b=19ZVFrvejQ2YmkQI1YwrjinIfOkG+fqxws0UBIV4wcFZhM4TG5ApSS7+gQb5swCgz MGwm5x6yD4Kn+4yK7ezK7j3JbiCaqSIdZAwS4gwPwvBKwebYXQSLmxKw9zf6ZJdEva k9evVzLRkisY29FxYgpMVHVfXYdk69CvJdiRj62BftzICPB2Bg0UfqKFgIyeffwFGm LYrhErXBfbKSl+IMGwM1RwpCNE5EwACx6nYiR0Hd9QjXHyRQC54kMOwE2t03PYfgvi stj3x/syyTQYABqH4hCMj7lx1cbLbrNSKNVvL6XEoS/43d9c7QH0f789OUGyahIL9u NSwWwA54UFktQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CA51211E4; Sat, 15 Jan 2022 18:05:51 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Working Group Chairs <wgchairs@ietf.org>, iesg@ietf.org
Subject: 2hr sessions and agendas
In-Reply-To: <164218658755.25340.17984418230968972509@ietfa.amsl.com>
References: <164218658755.25340.17984418230968972509@ietfa.amsl.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="==-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 15 Jan 2022 18:05:51 -0500
Message-ID: <7812.1642287951@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/k245BdVWxw5odFsGtR7qaS3XTzQ>
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: Sat, 15 Jan 2022 23:06:04 -0000

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.
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.

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    [

v2.23.0 | Report a Bug | By Email