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

Greg Wood <wood@isoc.org> Thu, 16 May 2019 19:48 UTC

Return-Path: <wood@isoc.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 324BD1200B7 for <tools-development@ietfa.amsl.com>; Thu, 16 May 2019 12:48:10 -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=isoc.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 8yCyBDmBMpFF for <tools-development@ietfa.amsl.com>; Thu, 16 May 2019 12:48:04 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-eopbgr750084.outbound.protection.outlook.com [40.107.75.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1847120046 for <tools-development@ietf.org>; Thu, 16 May 2019 12:48:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6T/DVCjxRWY5IZJYc9pxdWo03sXq48QiHryEgcLFPP0=; b=z0PvOqyewhEmRwcXEm1StIdUKTPybjr/Kp/RVsw2EL7sHkdvU2JJlAmxGgQLCjtlF+mrPfQMWyg8SIU3ifjWzZzmmk0sb/vGY2Z47WZej9iFYdwzFJCdaofGjRN+DZCj9LBkdXO8yOzzhOBf1Rimk/uqQmYSq3vnBTBflQaTDEU=
Received: from DM6PR06MB4635.namprd06.prod.outlook.com (20.176.112.80) by DM6PR06MB4394.namprd06.prod.outlook.com (20.176.108.91) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1900.16; Thu, 16 May 2019 19:47:59 +0000
Received: from DM6PR06MB4635.namprd06.prod.outlook.com ([fe80::b4e4:45fe:15bd:fd71]) by DM6PR06MB4635.namprd06.prod.outlook.com ([fe80::b4e4:45fe:15bd:fd71%4]) with mapi id 15.20.1900.010; Thu, 16 May 2019 19:47:59 +0000
From: Greg Wood <wood@isoc.org>
To: Robert Sparks <rjsparks@nostrum.com>
CC: Roman Danyliw <rdd@cert.org>, "tools-development@ietf.org" <tools-development@ietf.org>
Thread-Topic: [TOOLS-DEVELOPMENT] Getting a list of recently adopted document
Thread-Index: AdTv+exbqVZk8X+lSBOvVuGeujdpPQAcn8SABCmcAQACwQX/gAAA1TwAAAE0KAAAAEkqgA==
Date: Thu, 16 May 2019 19:47:58 +0000
Message-ID: <F57BD013-AB10-40E2-9E39-D62263AD1ADA@isoc.org>
References: <359EC4B99E040048A7131E0F4E113AFC01B33272D6@marchand> <64836652-8818-3aed-e807-f20c92e85e83@nostrum.com> <359EC4B99E040048A7131E0F4E113AFC01B33530E1@marathon> <0a18ded2-8839-a8b2-dc84-b732beed1d61@nostrum.com> <359EC4B99E040048A7131E0F4E113AFC01B3369673@marathon> <540975e1-681a-4039-cec9-a6fdfc9df55d@nostrum.com>
In-Reply-To: <540975e1-681a-4039-cec9-a6fdfc9df55d@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: BN6PR1301CA0030.namprd13.prod.outlook.com (2603:10b6:405:29::43) To DM6PR06MB4635.namprd06.prod.outlook.com (2603:10b6:5:fd::16)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=wood@isoc.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Apple Mail (2.3445.104.8)
x-originating-ip: [74.96.146.156]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ec333f60-3f51-4878-8cb6-08d6da3765b9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:DM6PR06MB4394;
x-ms-traffictypediagnostic: DM6PR06MB4394:
x-ms-exchange-purlcount: 5
x-microsoft-antispam-prvs: <DM6PR06MB43946817C5EB7E5D388203E7AB0A0@DM6PR06MB4394.namprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0039C6E5C5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(366004)(396003)(39850400004)(376002)(136003)(189003)(13464003)(199004)(83716004)(36756003)(68736007)(66066001)(71190400001)(66446008)(66946007)(71200400001)(26005)(66476007)(57306001)(5660300002)(6512007)(966005)(25786009)(446003)(73956011)(53936002)(4326008)(486006)(11346002)(14454004)(186003)(6246003)(478600001)(476003)(2616005)(86362001)(6306002)(54906003)(316002)(102836004)(52116002)(7736002)(305945005)(76176011)(53546011)(6506007)(8676002)(66556008)(64756008)(14444005)(256004)(6486002)(6436002)(82746002)(386003)(8936002)(81156014)(50226002)(33656002)(6116002)(81166006)(3846002)(99286004)(2906002)(6916009)(229853002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR06MB4394; H:DM6PR06MB4635.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: isoc.org does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: u3juXzwy6ezV5ohGU3ypdQFGVNqbLNlpiJ2NAGaALYot4F0+cTePXqGdjCB49Rqgi9jvRbgYe/k3Wj367KARFIiHSgWTqig/xWvzKU5Cl3ktyOA03JUk97vmckz1v6z8UUNGGBLtKILX9kKhfeZ5V3Gr8nyoVemF8B0GNV2uqc6B4C4wHsOUNdAR7t2YGaqPKStaQXN0+bQOxBQUp7vlODb8VHw1r35RNJ8Ahs4GRguuFirXXtY00M7lv83WxQqwZkh9qSKjY9sKLxrjTOp7d7lXtVntWzb9sMLfJd7Kf8x0awse83F3H50mNt+cSJifpl9ROuh5qY/Cuta6RdJm+avpXBGEE3SQGTG439/LTO/Yjfv6uZ3a7DiQH8nXRmSPPS6br15US/dZxali1n3Qgi0ADoeoeng1JBx9gPN7e4s=
Content-Type: text/plain; charset="utf-8"
Content-ID: <07064CF45B9B4A438CB5BFA1FD1AC6F1@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-Network-Message-Id: ec333f60-3f51-4878-8cb6-08d6da3765b9
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 May 2019 19:47:58.8956 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR06MB4394
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/dftX2Mr7uIZpMIa6gXV5_IviCjY>
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:48:10 -0000


> On May 16, 2019, at 3:39 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> 
> 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.

Specific delivery modes discussed by the IESG Comms review group included an email list called something like ietf-new@ietf.org. I don’t know whether the list name has been confirmed.

A Twitter feed similar to https://twitter.com/rfcbot (https://github.com/bradleyfalzon/rfc-bot) and https://twitter.com/rfcdujour (https://github.com/exponential-decay/rfc-du-jour) called something like @ietf-new was also discussed.

-Greg

>> 
>> 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