Re: [rfc-i] getting heads up on RFC-editor state for a draft
Jean Mahoney <jmahoney@amsl.com> Tue, 22 March 2022 21:44 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 1FA7E3A0D76 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 22 Mar 2022 14:44:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1647985485; bh=s3xmxtpipeDtLq6MCWsmKb1rHtHoqIxY/NeOdIP2nZo=; h=Date:To:References:From:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=lhW+dXjnO38EY2fWhUhTnxGxbnmcVEqhne1zvxn6B/zC6ktkTlGi82ubMKtFx6U8X MVsZD6FEYDjVa7muK1/g6RhID2qNuY2OxyRmFuq2KrJkxdFAqsIxb2zAm0iS8+QXTB xntwAN+Ymng+gnV7ar1+RTcksfflocUfWPIWPGBQ=
X-Mailbox-Line: From rfc-interest-bounces@rfc-editor.org Tue Mar 22 14:44:43 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AEFC3A0CF2; Tue, 22 Mar 2022 14:44:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1647985483; bh=s3xmxtpipeDtLq6MCWsmKb1rHtHoqIxY/NeOdIP2nZo=; h=Date:To:References:From:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=acTUuP/4zOM4Fp20gMNUyoQSBoq/jKGTrDoljS4cMmfAJRVDUZMSfgzmait+e2eQ9 zMfyyVjvJCUW+4DT50P6Oh2c80VsZXhVx4iE2qw/a/XsaQCSGFB20dZQxY9Jd0Rj+r 4dlTWXi13/WawaJXOZTJxVPrCbKGA8M/bHv9rdjY=
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 E62D53A0CF2 for <rfc-interest@ietfa.amsl.com>; Tue, 22 Mar 2022 14:44:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 JmiTLgeDef2y for <rfc-interest@ietfa.amsl.com>; Tue, 22 Mar 2022 14:44:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB8CA3A0CC5 for <rfc-interest@ietfa.amsl.com>; Tue, 22 Mar 2022 14:44:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix) id 0A36122666CE; Tue, 22 Mar 2022 14:44:34 -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 09710226646A for <rfc-interest@rfc-editor.org>; Tue, 22 Mar 2022 14:44:34 -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 fHuy8GHKm9S0 for <rfc-interest@rfc-editor.org>; Tue, 22 Mar 2022 14:44:31 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id 2950722663AC for <rfc-interest@rfc-editor.org>; Tue, 22 Mar 2022 14:44:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 1F2EC427C642; Tue, 22 Mar 2022 14:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QA0AUOGjWKkC; Tue, 22 Mar 2022 14:44:31 -0700 (PDT)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id E42FF427C640; Tue, 22 Mar 2022 14:44:30 -0700 (PDT)
Message-ID: <5ece0f3f-4271-227c-34b9-54cc1b7802c6@amsl.com>
Date: Tue, 22 Mar 2022 16:44:29 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: en-US
To: Michael Richardson <mcr+ietf@sandelman.ca>, rfc-interest@rfc-editor.org
References: <738138.1647941180@dooku>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <738138.1647941180@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/1Mc534Vx5GJUiQ-AFpMRRZp10WI>
Subject: Re: [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-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
Hi Michael, On 3/22/22 4:26 AM, Michael Richardson wrote: > 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. [JM] This is not quite a "maybe next week" notification, but when a document enters RFC-EDITOR state, an email is sent to the authors. The RPC tries to move a document from RFC-EDITOR state to AUTH48 within 3 weeks (some documents may take longer, others can be processed more quickly. It just depends on document complexity, any cluster dependencies, and editor availability [1]). The RPC is discussing providing more information in these email notifications so authors will have an general idea of when AUTH48 will occur. > > 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. [JM] The default sort order for the Current Queue page is by the common sequence of the states (EDIT -> RFC-EDITOR -> AUTH48) then by weeks in queue. Even if the sort order was reversed, it would be hard to determine a "top" of the Current Queue page because the queue is served by several editors. > > 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. [JM] You can take a look at the CurrQstats page [1] to get a feel for how long documents are in a given state. This may allow you to estimate when your document will enter AUTH48. You should check back for more current queue info when your document enters RFC-EDITOR state. Best regards, Jean [1] Things are moving fairly quickly at the moment -- the average number of weeks in EDIT and RFC-EDITOR states is 1.7 and 1.2, respectively: https://www.rfc-editor.org/reports/CurrQstats.txt > > -- > 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 _______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] getting heads up on RFC-editor state for … Michael Richardson
- Re: [rfc-i] getting heads up on RFC-editor state … Jean Mahoney
- Re: [rfc-i] getting heads up on RFC-editor state … Carsten Bormann
- Re: [rfc-i] getting heads up on RFC-editor state … Jean Mahoney