IETF Logo Mail Archive

Re: [admin-discuss] Next steps towards a net zero IETF

Bob Hinden <bob.hinden@gmail.com> Wed, 05 April 2023 00:22 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABDB3C14CEFC; Tue, 4 Apr 2023 17:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jrU7EY0vVjuS; Tue, 4 Apr 2023 17:22:02 -0700 (PDT)
Received: from mail-oa1-x2c.google.com (mail-oa1-x2c.google.com [IPv6:2001:4860:4864:20::2c]) (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 68913C1524C8; Tue, 4 Apr 2023 17:22:02 -0700 (PDT)
Received: by mail-oa1-x2c.google.com with SMTP id 586e51a60fabf-17aeb49429eso36621508fac.6; Tue, 04 Apr 2023 17:22:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680654121; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=u1e6ND8VSabh/Q872vXUuxr93FnF6D5KXSbzDcL219Q=; b=MePUGp0aofmQOocK3skohTs1V3bzlg2whW76x/odBebO8tCPqL4kFiTldfawRQiIVV ys6ZKMnjqMy7YyqKHHNsbzITtBy0eD7bBpfcLLXUNMlSJUdg3osF6x1H/kbRahrwLU6Z cbKQU6xBPkRu2B0hbfzEWbTP2cgZuzohGVcUxmB3un6KkRqj9LMSqBXYYCz71tSUEwbt VCVCKPzsImPTXIxzFdRXJVDWU0/APxKJpQfbj7vWRVIHLAQpl15Nk7an2UnZJYJ6B/9R dLSG1ZMIcVcU+ipHNl9jUmDiRQP+mZLZmC/3Lsl2VjHIqkSNlyYA7yKScufHzMeZ1zKu 9S7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680654121; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=u1e6ND8VSabh/Q872vXUuxr93FnF6D5KXSbzDcL219Q=; b=XMFkz5TG9hsd1H5wtbvAJA78sE9E5u36ix3o30YqcXgfsy4O1m4MBl2GL4YaYMxXrA +oF6GK3JfybfLYZCBR64pBF5F6xgCZUmO+FXcM5fFfH6hPNBkyB/9FrtQCnPPRlcRyrY VU1GzC1AalYmVZOGUTh4y1lER/7UGz++BNlQiJUFs/JYqaSqwj41Q9SfAy2uLh02SH8b onXdh09xUg3G4s1AVZ7rEQS2m/G84eiX2izlu1ECqVtzwTWHZ8Fou2ZR1D2qSktNxkmx 4TXtcLSyWcqqBpeVxwQFLDtu1FF/9RYkzJ91VS35pFyei//Sy8mg3QrwCHoZ39toAswb N7Ug==
X-Gm-Message-State: AAQBX9cRp+ZFX4K68WnDyjlvvhhcWrHu1ftXBLfRhUBe8GlpOI7Ih2y2 ZtLj3zQv+RMIGEeegDQweoos4//303jNHQ==
X-Google-Smtp-Source: AKy350Yt9VkgNNS6bebPd3ZpNHChmSnkafKglsUB2Thp7/UkxuuGOWkNvrhDiN2bsKfgRKX/yV4BRg==
X-Received: by 2002:a05:6870:461a:b0:177:809e:ead3 with SMTP id z26-20020a056870461a00b00177809eead3mr2553085oao.41.1680654121562; Tue, 04 Apr 2023 17:22:01 -0700 (PDT)
Received: from smtpclient.apple (S0106b88d1258a660.vn.shawcable.net. [50.64.54.6]) by smtp.gmail.com with ESMTPSA id tw16-20020a056871491000b0017ae909afe8sm5393018oab.34.2023.04.04.17.22.00 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Apr 2023 17:22:01 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_CE9FBC97-8D8F-41A7-BC6A-7A9D148CB8FF"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.2\))
Subject: Re: [admin-discuss] Next steps towards a net zero IETF
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <04338206-4a7e-818f-1e33-7fb9a88233f3@gmail.com>
Date: Tue, 04 Apr 2023 17:21:59 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>, Lars Eggert <lars@eggert.org>, Michael Richardson <mcr+ietf@sandelman.ca>, admin-discuss@ietf.org, IETF <ietf@ietf.org>
Message-Id: <F24890BC-3EC1-49F4-88E8-7762192DB9FD@gmail.com>
References: <13153.1680560012@localhost> <2658CD52-2D36-43E5-973B-39EB713E6A27@eggert.org> <04338206-4a7e-818f-1e33-7fb9a88233f3@gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3696.120.41.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/srmRw3124i3z1NZq6evLx-RLjgE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2023 00:22:06 -0000

Brian,

> On Apr 4, 2023, at 2:42 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> 
> In the ideal world there'd be no presentation because everybody read the draft, one slide with open issues and then the discussion.

I don’t agree that there should be no presentations.

Slides can be useful to focus the discussion, even if people have read and understand the drafts.   For example, a short overview and then a slide for each open issues.

Slides are also good for non-native english speakers, where reading the material helps their comprehension of what is being discussed.

Slides can be useful, but not surprisingly can be abused.   We all seen slides that attempt to put the whole document into a single slide,  but this doesn’t mean they can’t be useful.

What is needed is for w.g. chairs to review slides and work with the presenters to make useful presentations.

Bob


> 
>    Brian
> 
>> Additional tracks and/or longer days and/or full-length Fridays will likely be needed and the community should weigh those against their downsides for in-person and remote attendees.
>> Lars
>> .
>

v2.23.0 | Report a Bug | By Email