From: Cindy Morgan <cmorgan@amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 1 Mar 2012 11:37:21 -0800
Message-Id: <93C55C1D-6DA3-4446-998F-8C5A72824938@amsl.com>
To: iola-conversion-tool@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: [iola-conversion-tool] Incorrect time stamps in the History trail for
 recently-published RFCs
Precedence: list

Hi,

I have a question and a bug.

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?

(I ask because there were RFCs published yesterday that weren't updated =
in the datatracker when I looked around noon Pacific yesterday, but are =
updated now.  There are also RFCs that were published around 0800 =
Pacific today that have already been updated in the datatracker.)

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:

=
https://datatracker.ietf.org/doc/draft-lear-iana-timezone-database/history=
/
https://datatracker.ietf.org/doc/draft-irtf-hiprg-dht/history/
https://datatracker.ietf.org/doc/draft-ietf-behave-v4v6-bih/history/
https://datatracker.ietf.org/doc/draft-kucherawy-dkim-atps/history/
https://datatracker.ietf.org/doc/draft-stone-mgcp-vbd/history/

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):

https://datatracker.ietf.org/doc/draft-ietf-6man-3627-historic/history/

[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.]

Thanks,
Cindy

Cindy Morgan / Project Manager / IETF
48377 Fremont Blvd., Suite 117 / Fremont CA 94358
T: +1.510.492.4085 / F: +1.510.492.4001 / http://www.ietf.org
----------
Managed by Association Management Solutions (AMS);
Forum Management, Meeting and Event Planning
Website: http://www.amsl.com