IETF Logo Mail Archive

Re: Telechat reviews [Re: Tooling glitch in Last Call announcements and records]

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 17 October 2024 17:04 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 018B3C14F604; Thu, 17 Oct 2024 10:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 Uq1LalArKHM9; Thu, 17 Oct 2024 10:04:11 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC2D2C14F610; Thu, 17 Oct 2024 10:04:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 520AE1800D; Thu, 17 Oct 2024 13:04:09 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id 6rZ1_DGWLcwY; Thu, 17 Oct 2024 13:04:05 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1729184645; bh=5zXi+k2U/+kn5LZ2NCvE9NJY97TGgwdi9RhAByP9W1o=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=FajvjsIPkMAfwxBw7gvCb+CRbbB9nxQtAIL3BedXQeDJsPHw0Iiq1B7oWy4sly21u codxY+n8jl9XexUAZuZRSZg1WQPpF6uEMNxl0C2oA4cbTV8+c1a9wOGOtp6ZA+7lx3 gq6RdnHm+Oc9EoHsvjYaKjaORTkmDBJNs7ZI+vtmihDH9bOerjvXWx5ZoSRna1roRb 1D92wRlnmLQUjjM4nGXybGHvSTdW+dVO4gVytkd9z3185+0wdsihqQUF8VwKZUqn7/ lb3oiYFqJY9egviqvaZrTfhn/6kn8vZ/JDfviYOyBF5Twhr0/ExLXFh+3id9UUarvS 6hDYeXddIQdvQ==
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0053D1800C; Thu, 17 Oct 2024 13:04:05 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CF3B397C; Thu, 17 Oct 2024 13:04:04 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>
Subject: Re: Telechat reviews [Re: Tooling glitch in Last Call announcements and records]
In-Reply-To: <LV8PR11MB8536614B239A214C0E9D6981B5462@LV8PR11MB8536.namprd11.prod.outlook.com>
References: <822159B0D390905C0A194997@PSB> <e8a0b44b-8ecf-4b24-94d4-9c79ddd26d41@amsl.com> <F3ACA29EAAC4DE9FE06EDA21@PSB> <CAL0qLwaKw8P7CGXXXHM5Hh6YvkMMqeN8OOgpv2v7Yrob5QsQ7A@mail.gmail.com> <CAC4RtVDqmcyjmbTZz3CU3zUXXtrQwfXZUS=PBhgtGK+NChhPtw@mail.gmail.com> <LV8PR11MB8536614B239A214C0E9D6981B5462@LV8PR11MB8536.namprd11.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
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: Thu, 17 Oct 2024 13:04:04 -0400
Message-ID: <14273.1729184644@obiwan.sandelman.ca>
Message-ID-Hash: ZO74O6EAZXUFVJM55BRXGFUSFZHEWY5T
X-Message-ID-Hash: ZO74O6EAZXUFVJM55BRXGFUSFZHEWY5T
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Barry Leiba <barryleiba@computer.org>, John C Klensin <john-ietf@jck.com>, "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-Mailman-Version: 3.3.9rc6
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>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/feO2z7-WkzlglMLmbNq5IqMKspc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

Rob Wilton \(rwilton\) <rwilton=40cisco.com@dmarc.ietf.org> wrote:
    > Another choice, that perhaps could be considered, would be to initiate
    > the directorate reviews slightly earlier in the cycle.  E.g., at the
    > point that the WG has said that is ready before publication but before
    > the AD has reviewed and agreed to publish.  In fact, input from the
    > directorate reviews might be very helpful input to decide whether the
    > document is really ready to progress, or if there are significant
    > issues outstanding.

Yes. This.
(It's also when we could use an english editing pass.)

    > Of course, this might mean that a second follow up lighter directorate
    > review is needed to cover any changes that occurred between the initial
    > review and the version going before the IESG ballot, but if that second
    > review was focussed on the differences and issues raised previously
    > then I would have thought that the increase in workload on the
    > directorate would probably be fairly small, and hopefully manageable.
    > I.e., I am assuming that the second review would be assigned back to
    > the originate directorate reviewer.

Yes.  Sometimes getting that acknowledgement is rather difficult.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.28.0 | Report a Bug | By Email | System Status