IETF Logo Mail Archive

[TOOLS-DEVELOPMENT] Getting a list of recently adopted document

Roman Danyliw <rdd@cert.org> Thu, 11 April 2019 11:29 UTC

Return-Path: <rdd@cert.org>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93671120644 for <tools-development@ietfa.amsl.com>; Thu, 11 Apr 2019 04:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZQdS9f0yfjZl for <tools-development@ietfa.amsl.com>; Thu, 11 Apr 2019 04:29:50 -0700 (PDT)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF66E1204FC for <tools-development@ietf.org>; Thu, 11 Apr 2019 04:29:49 -0700 (PDT)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x3BBTmqR020819; Thu, 11 Apr 2019 07:29:48 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu x3BBTmqR020819
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1554982188; bh=kHpOXUPv5NLdqou8Lzlp27hOtWr937hepl8vamg3jh0=; h=From:To:CC:Subject:Date:From; b=ki4RaLD85SKohb3xh4C/n/+P9cXGOX/OQCO7f4FPQP1IyQ2CXZOCG7jAkivwaFmv7 y2ZBJqvc+v2FSnMNmBtNF6GynYQsbLU1jdFkxamZMPZZfSuaxAVsi6NZDEfz5J9fDB rfrTgIze32VP4YucJqOgxz4Q1qhI/4CvPnZF90p0=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x3BBTiau019698; Thu, 11 Apr 2019 07:29:44 -0400
Received: from MARCHAND.ad.sei.cmu.edu ([10.64.28.251]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0435.000; Thu, 11 Apr 2019 07:29:44 -0400
From: Roman Danyliw <rdd@cert.org>
To: IETF Tools Development <tools-development@ietf.org>
Thread-Topic: Getting a list of recently adopted document
Thread-Index: AdTv+exbqVZk8X+lSBOvVuGeujdpPQ==
Date: Thu, 11 Apr 2019 11:29:42 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B33272D6@marchand>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/4h5J6Sc_UW9yCNhjV-3LksII8QQ>
Subject: [TOOLS-DEVELOPMENT] Getting a list of recently adopted document
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2019 11:29:59 -0000

Hi Tools Team!

I'm helping Greg Wood launch an "IETF Notifications of Emerging Work" project.  The thinking is we'd like to have a way to easily summarize new work the IETF is starting.  To make this tractable, "new work" has been defined as all of the drafts that have been recently adopted per a given look-back period by a WG (i.e., draft-ietf-<wg name>-*-00).

The channels in which this would be summarized/announced is yet to be determined, but the raw data required per -00 draft is the draft name, WG, title, and abstract.

Doing this manually wouldn't be feasible, so we were looking for assistance with automation.  How far off is such a regular report from something that already exists?

Roman

v2.23.0 | Report a Bug | By Email