IETF Logo Mail Archive

[rfc-i] getting heads up on RFC-editor state for a draft

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 22 March 2022 09:27 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AC23F3A0E6A for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 22 Mar 2022 02:27:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1647941232; bh=voV/p6vx0+cd4GLOZChc6KS2tH2gFiW8uBc/CADx/jE=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=sCx3nnKRzoUQ47P9x1wsqUe3T9CUD1V0tVAS4yxlFMMRdkUIzqsPZRBG6+042rqpM na4StX9duhFVxeqtVc40vSf/XhVQx1kiV45diO3vK1hIdpWgzdBAYyBDpOF8bSXD4y IhBO3MNN2yUFE4xIjxVHWuID1dcv6oCV8CLRmK/M=
X-Mailbox-Line: From rfc-interest-bounces@rfc-editor.org Tue Mar 22 02:27:11 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C6D613A0E04; Tue, 22 Mar 2022 02:27:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1647941230; bh=voV/p6vx0+cd4GLOZChc6KS2tH2gFiW8uBc/CADx/jE=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=BsfDUMQBcnMfNfiRLgjfZ3TT+2HfehfI7stkBlkir1EmwElUL0kck7BFSkQNbE2UA uIV+ZKmP7x7pMxlZTIi+lnaYW8lx8KOtJC+IcFE+AgVboM06g9C7pNKbcNBCWosuXb UCLXYjyabSim1G7ZxkTPOSlhfIx39iJnuAV67hyk=
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1DF83A10BE for <rfc-interest@ietfa.amsl.com>; Tue, 22 Mar 2022 02:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.243
X-Spam-Level:
X-Spam-Status: No, score=-1.243 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 9OOi18thvpBv for <rfc-interest@ietfa.amsl.com>; Tue, 22 Mar 2022 02:26:59 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF0873A1028 for <rfc-interest@ietfa.amsl.com>; Tue, 22 Mar 2022 02:26:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix) id 2CF1A10D78; Tue, 22 Mar 2022 02:26:28 -0700 (PDT)
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 2AA7C221C85 for <rfc-interest@rfc-editor.org>; Tue, 22 Mar 2022 02:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7DwwXnOIgtEa for <rfc-interest@rfc-editor.org>; Tue, 22 Mar 2022 02:26:24 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) by rfc-editor.org (Postfix) with ESMTPS id 6A33210D78 for <rfc-interest@rfc-editor.org>; Tue, 22 Mar 2022 02:26:23 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:128:8273:5eb7:1d0c:7402]) by relay.sandelman.ca (Postfix) with ESMTPS id 3BE0D1F458 for <rfc-interest@rfc-editor.org>; Tue, 22 Mar 2022 09:26:21 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 1D0591A01C2; Tue, 22 Mar 2022 05:26:20 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: rfc-interest@rfc-editor.org
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 26.3
MIME-Version: 1.0
Date: Tue, 22 Mar 2022 10:26:20 +0100
Message-ID: <738138.1647941180@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/5HuHb8VClCa062r1NdZLNSCEgQc>
Subject: [rfc-i] getting heads up on RFC-editor state for a draft
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============3673861642745574227=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

In some other fora we discussed how entry into AUTH48 state is
non-deterministic, and if authors could have a "maybe next week" heads up so
that they could set aside some time, that would probably help.

I suffer from enough narcism that I use followthatpage on my DT profile page
to learn about changes.  I'd really like to poll some RFC-editor Q state on a
single document.  We have, for instance:
  https://www.rfc-editor.org/current_queue.php#draft-richardson-mud-qrcode

But, it is really the entire queue presented.  I thought I could judge how
soon the document would reach the top by... how far it was from the top.

If I poll:
  https://datatracker.ietf.org/doc/draft-richardson-mud-qrcode/history/

I think that I get some useful information, but no prediction.
Maybe I'm missing something.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email