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

Rob Sayre <sayrer@gmail.com> Fri, 18 October 2024 21:06 UTC

Return-Path: <sayrer@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 DA3D6C1E0D86 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2024 14:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_NONE=-0.0001, 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=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 zDF4IunZcJ7I for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2024 14:06:37 -0700 (PDT)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FC99C14F70C for <ietf@ietf.org>; Fri, 18 Oct 2024 14:06:37 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-5c96b2a10e1so2953930a12.2 for <ietf@ietf.org>; Fri, 18 Oct 2024 14:06:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729285595; x=1729890395; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=MqZTP5Pj9I+7yNUaJ0dW3H3ekhh8eR1R+oEBLTI9Ndk=; b=EV7f+eV1vUpGwu5jYTfipbKaVbScmGmkivRTY95Ah2EZwDr9OTeigArMAlDxHKWly4 3RJameZx5gJeGzskbrsCQPezz8PgtX58xeHH/5xC3OMkDPrZUZeg6MwPcG9PAaglyWbb lbUGl75l8rqkHfsxZjVRnT7ZohXgOYJ0QbSN4ahaVQfzfHqBEk8H7D498DnFq7CBJOYz fX8eyqbuqVY4pcuXC6qOrv3a8pc68NC9hunD/JOZcBFgWlY01FiCsqkcwSohk1UnDwe2 M0Q+wD6AAPED3qT9iniwac+fhxD+FbqZsmcSn4gxaKGJFKe3FYKZxjID25FKP38El0vq j+fA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729285595; x=1729890395; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=MqZTP5Pj9I+7yNUaJ0dW3H3ekhh8eR1R+oEBLTI9Ndk=; b=D2TAyk92PeVafy/TcRRB7QBa/B7kbDwGkGqUSKuLckzzxKQF5AEjNix8Ql6Nk1Ke9M QWJlbFGUB+jnqER/FizVPCeUCfpBjF9kCUCJK4gzf+C85fYD6a8I/Wxc4vmmpmXdGXQl 7I8YXLRMK/UsXfI66tms7TWN9peYcGlBOdDWla4lt72vV3X/EoR174PEL5HVy5Cxr0cP 3hctqz9ro0b+2vo+jqLFN25J3/uGs3DtA2ejjnBlAvNFRIZr9pTBwjTd+zIZ7QEG/iiz utjNMJT0qA3fWkVbD8v8+nuxRK1YVyyAJaNQyiYMOfRxq9WWmeb9gPHpH7CXn3jEMaak ZRpw==
X-Gm-Message-State: AOJu0Yxrx+xgO/idzTMXBnh/5l7cfcf4aShg66DUAFA8AwngMd/K4Ui8 LCR3hYjxwdlZGzzCO6W/A6FYTOVKYSVl4vc/Vsqq9/sfEFKfT2wKhbd/t7jut8/RGH1LM1bPgGD wvplJLoOqBknrf0bkFdHIB4PNyCTFcWeo
X-Google-Smtp-Source: AGHT+IFS6KLIeXpVuZZuzyICnwCk3pupkVjSmTILLfKo0/5a2qwZ8WmAddRj4VmJIhfOJyuThYEYJD6grUitQnFetO4=
X-Received: by 2002:a05:6402:5212:b0:5ca:14e5:b685 with SMTP id 4fb4d7f45d1cf-5ca14e5b70dmr649026a12.3.1729285594536; Fri, 18 Oct 2024 14:06:34 -0700 (PDT)
MIME-Version: 1.0
From: Rob Sayre <sayrer@gmail.com>
Date: Fri, 18 Oct 2024 14:06:23 -0700
Message-ID: <CAChr6Swz5mUUxkWfWQhC5ne3yJn3MQ+jw3BEk6rsCkRWpq3Y6g@mail.gmail.com>
Subject: Re: Telechat reviews [Re: Tooling glitch in Last Call announcements and records]
To: IETF discussion list <ietf@ietf.org>, Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary="00000000000093e6340624c6add1"
Message-ID-Hash: STGQAGGLVTYQZ4JQTQLVBXSBNLEGD4P3
X-Message-ID-Hash: STGQAGGLVTYQZ4JQTQLVBXSBNLEGD4P3
X-MailFrom: sayrer@gmail.com
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
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/-Q94-ULQ9H4m36toj5x8kRuiOPQ>
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>

Barry Leiba <barryleiba@computer.org> wrote:
>
> Perhaps there should be a question added to the shepherd writeup asking if
> the document is long or complex, or otherwise might need extra time in
Last
> Call.  And then let the responsible parties go from there.

It happens here and there.
https://mailarchive.ietf.org/arch/search/?q=%22last+call+extended%22

This seems fine to me. Sorry for the sports metaphor, but one might phrase
this action as "call an audible".

It means that you issue new and/or different instructions once you see the
playing field, even after making careful plans.

thanks,
Rob