Re: [iola-conversion-tool] Protocol Action vs. Document Action Messages

Russ Housley <housley@vigilsec.com> Fri, 24 February 2012 17:24 UTC

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 1993921F8522 for <iola-conversion-tool@ietfa.amsl.com>; Fri, 24 Feb 2012 09:24:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level:
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, HS_INDEX_PARAM=0.001, 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 g5GxdoY5w2oM for <iola-conversion-tool@ietfa.amsl.com>; Fri, 24 Feb 2012 09:24:20 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 2C87B21F862D for <iola-conversion-tool@ietf.org>; Fri, 24 Feb 2012 09:24:12 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id A6803F24051 for <iola-conversion-tool@ietf.org>; Fri, 24 Feb 2012 12:24:17 -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 3fa8IOxaXIp7 for <iola-conversion-tool@ietf.org>; Fri, 24 Feb 2012 12:24:11 -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 3C50DF24049 for <iola-conversion-tool@ietf.org>; Fri, 24 Feb 2012 12:24:17 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <11ED5602-C7D7-4FD6-AAAC-4E1423DD5651@amsl.com>
Date: Fri, 24 Feb 2012 12:24:11 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <01BF001F-4981-483D-8FAA-8210FE958268@vigilsec.com>
References: <8FFE1251-A16C-49A9-93E2-32F1F6392D11@amsl.com> <CANb2OvJw7KmwcnyTEoo_S0mxjgOtvZ_8ZKe-kEjxV+M7ncuvNw@mail.gmail.com> <11ED5602-C7D7-4FD6-AAAC-4E1423DD5651@amsl.com>
To: iola-conversion-tool@ietf.org
X-Mailer: Apple Mail (2.1084)
Subject: Re: [iola-conversion-tool] Protocol Action vs. Document Action Messages
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: Fri, 24 Feb 2012 17:24:21 -0000

Ole:

Items in Section 2 of the Telechat agenda should produce Protocol Action messages.  These are BCPs, Proposed Standards, and Internet Standards.

Items in Sections 3.1 and 3.2 of the Telechat agenda should produce Document Action messages.  These are Informational, Experimental, and Historic RFCs.

Hope this helps,
  Russ


On Feb 24, 2012, at 12:15 PM, Cindy Morgan wrote:

> 
> On Feb 24, 2012, at 8:57 AM, Ole Laursen wrote:
> 
>> 012/2/23 Cindy Morgan <cmorgan@amsl.com>om>:
>>> In the approval announcements for IETF stream documents, it looks like the tracker is treating all of the messages as Protocol Actions, e.g. "Subject: Protocol Action: 'Analysis of Stateful 64 Translation' to Informational RFC (draft-ietf-behave-64-analysis-06.txt)."  However, it is only approval announcements for Standards Track and BCP documents that are Protocol Actions.  Approval announcements for Informational, Experimental and Historic* documents are Document Actions.
>> 
>> I'm not sure what exactly went wrong but the code was looking at the
>> indefinite article of the intended status which is really odd. Instead
>> I now just compare it with your list.
> 
> FWIW, whatever is being used to tell the difference between Protocol and Document Actions on the IESG agenda (https://trackerbeta.ietf.org/iesg/agenda/?private) does seem to be working as it should.  But I just checked several docs listed on the agenda as Document Actions*, and their approval announcement text is still being generated as Protocol Actions.
> 
> * draft-ietf-v6ops-v6nd-problems
>  draft-snell-atompub-tombstones
>  draft-ietf-lisp-interworking
>  draft-ietf-behave-64-analysis
> 
> Thanks,
> Cindy
> 
>> 
>> 
>> Ole
>> -- 
>> _______________________________________________
>> iola-conversion-tool mailing list
>> iola-conversion-tool@ietf.org
>> https://www.ietf.org/mailman/listinfo/iola-conversion-tool
>> 
> 
> -- 
> _______________________________________________
> iola-conversion-tool mailing list
> iola-conversion-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/iola-conversion-tool