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

Roman Danyliw <rdd@cert.org> Thu, 16 May 2019 19:05 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 EBD9B12024F for <tools-development@ietfa.amsl.com>; Thu, 16 May 2019 12:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, URIBL_BLOCKED=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 iN1WsSpHnYdN for <tools-development@ietfa.amsl.com>; Thu, 16 May 2019 12:05:20 -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 56E0012021B for <tools-development@ietf.org>; Thu, 16 May 2019 12:05:19 -0700 (PDT)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x4GJ5IFC018653; Thu, 16 May 2019 15:05:18 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu x4GJ5IFC018653
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1558033518; bh=VLRMxo3iE582CTzKLN+wfGaBZRHl0f0MFA9PIz9EuQU=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=tVNRnPBzVFkTwMfZewdtZmxLr4MYyolUS+/DIk2PvCqb48TQCNpWZ9WE6JUhJHwhv l2/SXrsQKcxhFl7QAHCR21uiHrM805RJvhRWty+kDiOleK4DRNjlvJcquFabG428m/ gxB3IhQU7Ju2pYlL/v2OTfqAhi2W7lxSEjw3bwNw=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x4GJ5BiQ020235; Thu, 16 May 2019 15:05:11 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0439.000; Thu, 16 May 2019 15:05:10 -0400
From: Roman Danyliw <rdd@cert.org>
To: Robert Sparks <rjsparks@nostrum.com>, Greg Wood <wood@isoc.org>
CC: "tools-development@ietf.org" <tools-development@ietf.org>, Roman Danyliw <rdd@cert.org>
Thread-Topic: [TOOLS-DEVELOPMENT] Getting a list of recently adopted document
Thread-Index: AdTv+exbqVZk8X+lSBOvVuGeujdpPQAlAYiABCEs/pACyXUCgAAHm+/w
Date: Thu, 16 May 2019 19:05:10 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B3369673@marathon>
References: <359EC4B99E040048A7131E0F4E113AFC01B33272D6@marchand> <64836652-8818-3aed-e807-f20c92e85e83@nostrum.com> <359EC4B99E040048A7131E0F4E113AFC01B33530E1@marathon> <0a18ded2-8839-a8b2-dc84-b732beed1d61@nostrum.com>
In-Reply-To: <0a18ded2-8839-a8b2-dc84-b732beed1d61@nostrum.com>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/-RGqDUtkY27BusfwnIXIwU4tZYU>
Subject: Re: [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, 16 May 2019 19:05:24 -0000

Hi Robert!

Greg has the vision here.  I thought it was more of a report that would be cherry-picked into other channels like Twitter, the web-site.  I didn't think it was another mailing list.

Greg: right?  I don't think we discussed how this information would be delivered.

Roman

> -----Original Message-----
> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> Sent: Thursday, May 16, 2019 2:41 PM
> To: Roman Danyliw <rdd@cert.org>
> Cc: tools-development@ietf.org
> Subject: Re: [TOOLS-DEVELOPMENT] Getting a list of recently adopted
> document
> 
> Another thread to pick up -
> 
> Have you decided on the "channels" below? What I'd heard from Spencer
> was that we'd have a new list and other things could feed off that list.
> Do we need more? If not, has the IESG chosen a list name?
> 
> RjS
> 
> 
> On 5/2/19 1:14 PM, Roman Danyliw wrote:
> > Hi Rob!
> >
> > Sorry for the long delay.  I missed you response.
> >
> > You have it right.  The interest would be for the IETF WG stream only.
> >
> > Roman
> >
> >> -----Original Message-----
> >> From: TOOLS-DEVELOPMENT [mailto:tools-development-
> bounces@ietf.org]
> >> On Behalf Of Robert Sparks
> >> Sent: Thursday, April 11, 2019 9:43 AM
> >> To: tools-development@ietf.org
> >> Subject: Re: [TOOLS-DEVELOPMENT] Getting a list of recently adopted
> >> document
> >>
> >> It would not be hard to build, and Spencer gave us very early warning
> >> on the idea, so it's mostly thought through already.
> >>
> >> But we need to be sure we build what's really wanted, and advertise
> >> it correctly.
> >>
> >> As stated, you want this list to be only _IETF_ WG adoptions, correct?
> >> We would not include IRTF RG adoptions (or IAB or any other stream),
> >> correct?
> >>
> >> RjS
> >>
> >> On 4/11/19 6:29 AM, Roman Danyliw wrote:
> >>> 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
> >>>
> >>> _______________________________________________
> >>> TOOLS-DEVELOPMENT mailing list
> >>> TOOLS-DEVELOPMENT@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/tools-development
> >> _______________________________________________
> >> TOOLS-DEVELOPMENT mailing list
> >> TOOLS-DEVELOPMENT@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tools-development