Re: [Gendispatch] Fwd: New Version Notification for draft-nottingham-iesg-review-workload-00.txt

Joel Halpern <jmh@joelhalpern.com> Fri, 31 March 2023 00:43 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8A9C14CE24 for <gendispatch@ietfa.amsl.com>; Thu, 30 Mar 2023 17:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 Z3j6QQ_9VfKu for <gendispatch@ietfa.amsl.com>; Thu, 30 Mar 2023 17:43:22 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 9E23FC14CE4A for <gendispatch@ietf.org>; Thu, 30 Mar 2023 17:43:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4PnhNV2tpsz6GKJw; Thu, 30 Mar 2023 17:43:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1680223402; bh=cOoex2G5dV3LAIGBVxuKIVaNRH6Gx0Z62ctqbq/1mzk=; h=Date:Subject:To:References:From:In-Reply-To:From; b=TnYVYR6vfIN4u2NUpPVf5lL08Qr9dZZc0amNjb9J2pydYQe87+mKNzHgypO6Q+hOy 8WHPjLqQZIUexrltixvZT9y58Vm+GuH90GHf5s2ofNAvHflpKPx4HBxrNblIQSE8aX 5SdpS7lFppNH++JnVvZGP3aO41/J4JPyXI+3NcYA=
X-Quarantine-ID: <pQUyJUWMgnKh>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [IPV6:2001:67c:370:128:d856:e053:f7d6:5e5c] (unknown [IPv6:2001:67c:370:128:d856:e053:f7d6:5e5c]) (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 maila2.tigertech.net (Postfix) with ESMTPSA id 4PnhNT5VKQz6GJbs; Thu, 30 Mar 2023 17:43:21 -0700 (PDT)
Message-ID: <5371cba4-caba-3ed4-b04d-9d4474db02aa@joelhalpern.com>
Date: Thu, 30 Mar 2023 20:43:20 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0
Content-Language: en-US
To: Martin Thomson <mt@lowentropy.net>, gendispatch@ietf.org
References: <168016566375.62790.7482502869993780606@ietfa.amsl.com> <180F04B6-DD6F-4034-9318-E5975570229A@mnot.net> <89babe8e-1022-e6bd-22f2-137b4189e678@joelhalpern.com> <fec8ee0c-e252-41d7-b27c-dd4891f639f3@app.fastmail.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <fec8ee0c-e252-41d7-b27c-dd4891f639f3@app.fastmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/PNnovP9QzPvKiYf1uX85unse1Fo>
Subject: Re: [Gendispatch] Fwd: New Version Notification for draft-nottingham-iesg-review-workload-00.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Mar 2023 00:43:26 -0000

Apparently, you and I read the draft somewhat differently.  I am sure 
Mark can say what he means :-)

Under the assumption that I understood it, the draft seems to suggest a 
direction that may help, and is unlikely to work.

Having said that, clarity on the question of who is responsible for 
holding the discuss and the discussion is quite important in my view.  
If the AD does not help the discussion then we are making a far more 
fundamental change to the IESG than I read the draft as asking for.

Yours,

Joel

On 3/30/2023 7:21 PM, Martin Thomson wrote:
> It seems to me like Mark is challenging that mode of operation also.  That is, he is suggesting that when that delegation occurs, it is more complete than it is today.
>
> I do somewhat like the idea that maybe the discussion could be conducted outside of the ivory tower somewhat more than it is today.  As a document author, I often find myself frustrated by the game of telephone that occurs during IESG review.
>
> On Thu, Mar 30, 2023, at 20:39, Joel Halpern wrote:
>> There are some aspects of the AD review that I assume, and would like
>> to see referenced.
>>
>> One aspect is that when an AD has (or accepts from a reviewer) a
>> concern, the AD needs to do enough work themselves to be able to engage
>> effectively in discussion of that concern with fellow ADs and then (if
>> there is still a concern) with the document shepherd / editors / WG.
>>
>> The other aspect is somewhat more nuanced and subtle.  If ADs from
>> other areas see an issue in the area for which an AD is responsible,
>> one of the ADs for that area ought, I think, be prepared to engage in
>> enough review to determine whether they share or disagree with the
>> concern.  Maybe part of this could be delegated, but it seems that it
>> is the AD who needs to engage in the discussion.
>>
>> Yours,
>>
>> Joel
>>
>> On 3/30/2023 4:41 AM, Mark Nottingham wrote:
>>> FYI -- based on discussions this week, food for thought / bike shedding / discussion.
>>>
>>> Cheers,
>>>
>>>
>>>> Begin forwarded message:
>>>>
>>>> *From: *internet-drafts@ietf.org
>>>> *Subject: **New Version Notification for draft-nottingham-iesg-review-workload-00.txt*
>>>> *Date: *30 March 2023 at 5:41:03 pm GMT+9
>>>> *To: *"Mark Nottingham" <mnot@mnot.net>
>>>>
>>>>
>>>> A new version of I-D, draft-nottingham-iesg-review-workload-00.txt
>>>> has been successfully submitted by Mark Nottingham and posted to the
>>>> IETF repository.
>>>>
>>>> Name: draft-nottingham-iesg-review-workload
>>>> Revision: 00
>>>> Title: IESG Document Review Expectations: Impact on AD Workload
>>>> Document date: 2023-03-30
>>>> Group: Individual Submission
>>>> Pages: 7
>>>> URL:            https://www.ietf.org/archive/id/draft-nottingham-iesg-review-workload-00.txt
>>>> Status:         https://datatracker.ietf.org/doc/draft-nottingham-iesg-review-workload/
>>>> Html:           https://www.ietf.org/archive/id/draft-nottingham-iesg-review-workload-00.html
>>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-nottingham-iesg-review-workload
>>>>
>>>>
>>>> Abstract:
>>>>    Arguably, IETF Area Directors are overloaded with document review
>>>>    duties.  This document surveys the relevant background, discusses the
>>>>    implications, and makes a proposal for improvements.
>>>>
>>>>
>>>>
>>>>
>>>> The IETF Secretariat
>>>>
>>>>
>>> --
>>> Mark Nottingham   https://www.mnot.net/
>>>
>>>
>> -- 
>> Gendispatch mailing list
>> Gendispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/gendispatch