Re: [TOOLS-DEVELOPMENT] How do counters reset in the datatracker

Robert Sparks <> Thu, 16 May 2019 14:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 89EFC120094 for <>; Thu, 16 May 2019 07:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)"
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 46_ci-tM9P2n for <>; Thu, 16 May 2019 07:23:33 -0700 (PDT)
Received: from ( [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D4E0B120033 for <>; Thu, 16 May 2019 07:23:33 -0700 (PDT)
Received: from unescapeable.local ([]) (authenticated bits=0) by (8.15.2/8.15.2) with ESMTPSA id x4GENRa0061692 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 16 May 2019 09:23:28 -0500 (CDT) (envelope-from
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=default; t=1558016608; bh=R3vXalIvH9BcQQwmI7njjj4HUHGWqXcQ9OE6FwNHUYQ=; h=Subject:To:References:From:Date:In-Reply-To; b=ajfHA/4EdfFpMandK3ZpAFjxcMYsbw7hoGvlBL+WPi3D0caGpCBrGl4LfCVLfBITT BfsbQV2onyuOy7kFNNyO/49l61gVi6VScV6zPRthVs0ABIcQpavWFK+PUapzwZjJPB POXTr7i2EkdeD5MTWYz2vluCl3m+XeRCNwgPAXgk=
X-Authentication-Warning: Host [] claimed to be unescapeable.local
To: Roman Danyliw <>, "" <>
References: <359EC4B99E040048A7131E0F4E113AFC01B3367E08@marathon>
From: Robert Sparks <>
Message-ID: <>
Date: Thu, 16 May 2019 09:23:27 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFC01B3367E08@marathon>
Content-Type: multipart/alternative; boundary="------------72040EB5A374518055F20C71"
Content-Language: en-US
Archived-At: <>
Subject: Re: [TOOLS-DEVELOPMENT] How do counters reset in the datatracker
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 16 May 2019 14:23:36 -0000

Hi Roman -

Like Russ, I will have to look at the code to give you the exact answer 
you are looking for, and I hope to do that today or tomorrow. I fear the 
answer will be "it's complicated".

For the moment, I can point to some history. Different ADs over time 
have had different opinions about what these "since" values should 
represent. Should it show time since last action, or accrued time in the 
where it is in the queue? Who is the metric there to help push along? 
I've occasionally been of the opinion that perhaps we should show state 
and sub-state staleness separately (as suggested by Adrian in one of the 
tickets below), but the display does get cluttered...


<> and



On 5/16/19 8:31 AM, Roman Danyliw wrote:
> Hi!
> At the IESG retreat, there was a confusion in the IESG about how the timer listed next to the draft  (e.g., "for xxx days") in the datatracker is reset when a state or sub-state changes (see screenshot).  I was asked get clarity on the following:
> ** Which sub-state changes will trigger a reset to 0?
> ** Which state changes will trigger a reset to 0?
> Thanks,
> Roman
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list