Re: [iola-conversion-tool] Incorrect time stamps in the History trail for recently-published RFCs

Ole Laursen <> Thu, 01 March 2012 20:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9EF6A21E8036 for <>; Thu, 1 Mar 2012 12:45:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.801
X-Spam-Status: No, score=-2.801 tagged_above=-999 required=5 tests=[AWL=0.176, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gciLZcuP3tlz for <>; Thu, 1 Mar 2012 12:45:22 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id F2B6E21E801E for <>; Thu, 1 Mar 2012 12:45:21 -0800 (PST)
Received: by vbbez10 with SMTP id ez10so990998vbb.31 for <>; Thu, 01 Mar 2012 12:45:21 -0800 (PST)
Received-SPF: pass ( domain of designates as permitted sender) client-ip=;
Authentication-Results:; spf=pass ( domain of designates as permitted sender)
Received: from ([]) by with SMTP id r10mr11167336vds.39.1330634721581 (num_hops = 1); Thu, 01 Mar 2012 12:45:21 -0800 (PST)
Received: by with SMTP id r10mr9484547vds.39.1330634721430; Thu, 01 Mar 2012 12:45:21 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Thu, 1 Mar 2012 12:45:01 -0800 (PST)
In-Reply-To: <>
References: <>
From: Ole Laursen <>
Date: Thu, 01 Mar 2012 21:45:01 +0100
Message-ID: <>
To: Cindy Morgan <>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmc653BLCq3Paxk/vPZg1eCEgI79FdYeebhnEcW/sDFYatfvrb0Y28PzTggUzAIIxo8+6z4
Subject: Re: [iola-conversion-tool] Incorrect time stamps in the History trail for recently-published RFCs
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the IOLA / DB Schema Conversion Tool Project <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 01 Mar 2012 20:45:22 -0000

2012/3/1 Cindy Morgan <>:
> Question: It looks like the datatracker now magically gets the information when a new RFC is published.  Previously, the Secretariat had to do part of that manually, including changing the IESG state to "RFC Published."  Does this now happen automatically, or does the datatacker sync with the RFC Editor database at set times?  In either case, it looks like the Secretariat no longer needs to take action here?

Yes, it gets the information from the RFC Editor. It did that before
too, but saved the information on the side instead of merging it in. I
couldn't do that with the new schema, had to merge, so in the end it's
now automatic I think. It will set it to be in the RFC state and add
the comment you've noticed. I hope that's okay?

There's a slight problem with the IESG state, it doesn't set that to
published, we need to get that fixed although I don't think you can
actually see it on the document pages.

> Bug: In the history trails of the RFCs that were published in the last two days, it shows the RFC as being published on 2012-02-01, rather than 2012-02-29 or 2012-03-01:
> And strangely, for draft-ietf-6man-3627-historic, the history trail does not include an "RFC Published" message from the system at all (although the doc page itself does have a link to the RFC):
> [And if you look at draft-ietf-sieve-notify-sip-message, the history trail has the correct time stamp because Amy changed the state manually to RFC Published yesterday.  At some later point the datatracker got the correct RFC number information from somewhere else.]

Odd, it's supposed to put in the publication date it gets from the RFC
Editor, but it's possible there's a bug somewhere. I'll take a look at
the above tomorrow.