Return-Path: <housley@vigilsec.com>
X-Original-To: iola-conversion-tool@ietfa.amsl.com
Delivered-To: iola-conversion-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
 with ESMTP id 6132221F8718 for <iola-conversion-tool@ietfa.amsl.com>;
 Mon,  5 Mar 2012 06:27:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level: 
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051,
 BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K8PV6vSywk5P for
 <iola-conversion-tool@ietfa.amsl.com>; Mon,  5 Mar 2012 06:27:32 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by
 ietfa.amsl.com (Postfix) with ESMTP id 9DE7E21F8710 for
 <iola-conversion-tool@ietf.org>; Mon,  5 Mar 2012 06:27:32 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net
 (Postfix) with ESMTP id E5DD4F2401C; Mon,  5 Mar 2012 09:27:38 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost
 (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id
 crT2j1DaGR1k; Mon,  5 Mar 2012 09:27:25 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net
 [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No
 client certificate requested) by odin.smetech.net (Postfix) with ESMTP id
 0F1A7F24022; Mon,  5 Mar 2012 09:27:38 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CANb2OvL5dgcQGeJEj0=tLVQMH+qPpkjp6gG=0ZD-Lwd-eyriBQ@mail.gmail.com>
Date: Mon, 5 Mar 2012 09:27:30 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <86AF53FB-F163-4D61-AD50-34264C62CB0E@vigilsec.com>
References: <93C55C1D-6DA3-4446-998F-8C5A72824938@amsl.com>
 <CANb2OvJyCJM+0oPr8ATBuu6NWCakCyX+pficrhbS7Bk3gxyT5g@mail.gmail.com>
 <CANb2OvLguHFgVqoG_1D9gGNuVa66HqC_gHAPE8nVLiCgLQNv_A@mail.gmail.com>
 <1D6BB920-AF31-458F-8BCA-0BA50D20EEF0@vigilsec.com>
 <CANb2OvL5dgcQGeJEj0=tLVQMH+qPpkjp6gG=0ZD-Lwd-eyriBQ@mail.gmail.com>
To: Ole Laursen <olau@iola.dk>
X-Mailer: Apple Mail (2.1084)
Cc: iola-conversion-tool@ietf.org
Subject: Re: [iola-conversion-tool] Incorrect time stamps in the History trail
 for recently-published RFCs
X-BeenThere: iola-conversion-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the IOLA / DB Schema Conversion Tool Project
 <iola-conversion-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iola-conversion-tool>,
 <mailto:iola-conversion-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iola-conversion-tool>
List-Post: <mailto:iola-conversion-tool@ietf.org>
List-Help: <mailto:iola-conversion-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iola-conversion-tool>,
 <mailto:iola-conversion-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 14:27:33 -0000

Ole:

> 2012/3/2 Russ Housley <housley@vigilsec.com>:
>>> Does anyone know whether we could get the actual date out of the RFC
>>> Editor? I can imagine a couple of other hacks to improve on the
>>> first-day-of-month-assumption, but by far the most robust thing =
would
>>> if the downloaded data just told us it.
>>=20
>> This will be addressed in the future under another task order.  =
Currently, the RFC Editor send an email to the Secretariat, and the date =
comes from that email.  The goal is to have a message sent that the =
datatracker can consume in an automated fashion.
>=20
> Aha. If that date could be put into the generated XML file here:
>=20
> http://www.rfc-editor.org/rfc/rfc-index.xml
>=20
> Then it's a <1 hour job to fix it in the Datatracker end. The XML file
> already says
>=20
>        <date>
>            <month>March</month>
>            <year>2011</year>
>        </date>
>=20
> so a <day>29</day> would fit the purpose nicely. Would it be feasible
> to do this in a not too distant timeframe?

This data has never included the day.  I think we need to use the =
messages that are sent to the secretariat to get the day.

Russ

