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

Robert Sparks <rjsparks@nostrum.com> Thu, 16 May 2019 19:39 UTC

Return-Path: <rjsparks@nostrum.com>
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 12B8912025A for <tools-development@ietfa.amsl.com>; Thu, 16 May 2019 12:39:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level:
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 6J_RbGW5iwmx for <tools-development@ietfa.amsl.com>; Thu, 16 May 2019 12:39:44 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4F4E1200FA for <tools-development@ietf.org>; Thu, 16 May 2019 12:39:44 -0700 (PDT)
Received: from unescapeable.local ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x4GJdcA3013943 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 16 May 2019 14:39:39 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1558035580; bh=OKxQdwZkQCTY/MdAiB/A9KZa20VYhSh4Pvm4EvwgiHo=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=vTP9eKrEoX2JUhRlL2JMzs4UnxpVI4X861WrHlw8lkBswjgJ5q7yJXiw11hDyGS5R CaIGsLReAyeu7xFpUsTHGpHPft90ZPJ2BhzCFocMx8p+xaOzrzMxynL8FmZMVUPAr5 TLlpaUh9wc7FA+REnp4a02MNynxAuFPyCiaJLW+w=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be unescapeable.local
To: Roman Danyliw <rdd@cert.org>, Greg Wood <wood@isoc.org>
Cc: "tools-development@ietf.org" <tools-development@ietf.org>
References: <359EC4B99E040048A7131E0F4E113AFC01B33272D6@marchand> <64836652-8818-3aed-e807-f20c92e85e83@nostrum.com> <359EC4B99E040048A7131E0F4E113AFC01B33530E1@marathon> <0a18ded2-8839-a8b2-dc84-b732beed1d61@nostrum.com> <359EC4B99E040048A7131E0F4E113AFC01B3369673@marathon>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <540975e1-681a-4039-cec9-a6fdfc9df55d@nostrum.com>
Date: Thu, 16 May 2019 14:39:38 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFC01B3369673@marathon>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/vBr_crOCqwoqhRv5mVro8ELhbkg>
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:39:47 -0000

On 5/16/19 2:05 PM, Roman Danyliw wrote:
> 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.
Alternatives include a subscription feed or direct email to some address.
>
> 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