Re: Agenda development support

"Andrew G. Malis" <agmalis@gmail.com> Tue, 03 November 2015 04:31 UTC

Return-Path: <agmalis@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FE1A1B2D11 for <wgchairs@ietfa.amsl.com>; Mon, 2 Nov 2015 20:31:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 bnAE6UdWQZlL for <wgchairs@ietfa.amsl.com>; Mon, 2 Nov 2015 20:31:00 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 B95071B2D61 for <wgchairs@ietf.org>; Mon, 2 Nov 2015 20:30:59 -0800 (PST)
Received: by wmff134 with SMTP id f134so5140696wmf.0 for <wgchairs@ietf.org>; Mon, 02 Nov 2015 20:30:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=W8LO7dYZZcoQwR1+6jb6X3w9GII3+fIVFdraIacXvow=; b=Oa0vZly3hnxCezHPnb2aNIv6srrVTNVximiT8KOAuDsCY5AHzDaATu2dWukhTJgN+j aTUkPl0y4A9hJF9OgA5csaQDhCpQfzkHRVhaQ5jYp63SPHu3A35ARVdbTLW8iUIfv6xU wkbGonO7jIkobu1jjhcqpeMYtLHUTSPgcteWIV0Slc2iLtE81iNb/e5E7+TBqcfeIrzr JTbzhpMFAiH1JIvxVFW2LPDbkyGQIx92zC3jQH2vHgoSptfOVKpfW+ehp4X1GBoX6quf nOdtNQgBQDiVLkmdooske0KI6w3wCGT0gshE1gLgyuDVo4zreOPS00iOwRK7iGI/EHdF 5Jog==
X-Received: by 10.28.18.21 with SMTP id 21mr17992511wms.34.1446525058351; Mon, 02 Nov 2015 20:30:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.195.10 with HTTP; Mon, 2 Nov 2015 20:30:38 -0800 (PST)
In-Reply-To: <B6616D7F-0518-44C3-9EF7-F4A9AE013FD4@cisco.com>
References: <B6616D7F-0518-44C3-9EF7-F4A9AE013FD4@cisco.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 03 Nov 2015 13:30:38 +0900
Message-ID: <CAA=duU3SyLNe0vwgQPe16kRjfCtOTCQox0L=5JqT80p90gJoQA@mail.gmail.com>
Subject: Re: Agenda development support
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: multipart/alternative; boundary="001a1146e6104308c105239b5cf1"
Archived-At: <http://mailarchive.ietf.org/arch/msg/wgchairs/caQ4mAITVCnngbsPdKlp4VgYJB8>
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2015 04:31:03 -0000

Fred,

That is very cool, thanks for sharing! By all means, this would be great to
run from a clickable form on either the tools page or perhaps on
http://www.ietf.org/wg/chairs-page.html .

Cheers,
Andy

On Tue, Nov 3, 2015 at 9:13 AM, Fred Baker (fred) <fred@cisco.com> wrote:

> I have developed a tool for my own amusement, and wonder whether others
> would find it useful. If appropriate I can get it filed on the tools page
> or somehow supported in the data tracker. It is based on Henrik's data
> tracker API, which is to say "not screen scraping". It's in perl.
>
> Here's the problem I'm trying to solve. I can look at
> https://datatracker.ietf.org/wg/v6ops/documents/, and figure out anything
> I need to know about my working group's drafts. The information is all
> there. However, it is somewhat inaccessible, in the sense that it is
> cluttered with information that, while relevant, isn't particularly useful
> in agenda analysis, and the sort capability (that used to be there?) isn't
> there (any more).
>
> What I'm trying to figure out, when planning an agenda, is:
>   - what working group drafts have been updated since the last meeting
>     (which I will then do a mail search to determine the latest status of)
>   - what individual submissions to the working group have come in
>     (which I will then do a mail search for supporting commentary
> regarding).
>
> I may also have other drafts I am specifically interested in; this time,
> we had an invited talk on a technology that Facebook is experimenting with,
> that is actually in discussion in nvo3 (draft-herbert-nvo3-ila).
>
> So therefore, I enter something like
> ietf-agenda-analysis.pl --date 2015-07-22 v6ops
> draft-herbert-nvo3-ila-01.txt
> or
> ietf-agenda-analysis.pl --date 2015-07-22 v6ops draft-herbert-nvo3-ila
>
> and get back the following (today). My question is whether other chairs
> would find this kind of capability useful, and whether I should bring it up
> with the tools team. If it's useful to you, you're welcome to my script
> regardless, on an open source basis.
>
> RFC Editor: EDIT
>         2015-10-26      draft-ietf-v6ops-siit-dc
>         2015-10-26      draft-ietf-v6ops-siit-dc-2xlat
>         2015-10-26      draft-ietf-v6ops-siit-eam
>         2015-10-19      draft-ietf-v6ops-pmtud-ecmp-problem
>
> WG: In WG Last Call
>         2015-11-01      draft-ietf-v6ops-ipv6-ehs-in-real-world
>
> WG: Parked WG Document
>         2015-10-14      draft-ietf-v6ops-mobile-device-profile
>
> WG: Submitted to IESG for Publication
>         2015-10-30      draft-ietf-v6ops-reducing-ra-energy-consumption
>
> WG: Unupdated WG Document
>         2015-07-06      draft-ietf-v6ops-dhcpv6-slaac-problem
>         2015-05-03      draft-ietf-v6ops-ula-usage-recommendations
>
> WG: Updated WG Document
>         2015-11-01      draft-ietf-v6ops-host-addr-availability
>         2015-11-01      draft-ietf-v6ops-unique-ipv6-prefix-per-host
>         2015-10-19      draft-ietf-v6ops-design-choices
>
> Individual Submission: Unupdated
>         2015-07-06      draft-akira-v6ops-mape-experience
>         2015-07-06      draft-xcf-v6ops-chinatelecom-deployment
>         2015-07-05      draft-hui-v6ops-ipv6trans-select-nfv
>         2015-07-05      draft-xli-v6ops-cernet-deployment
>         2015-07-05      draft-yang-v6ops-ipv6tran-select
>         2015-06-26      draft-vyncke-v6ops-ipv6-only-thin-clients
>         2015-06-25      draft-sun-v6ops-xlat-multi
>
> Individual Submission: Updated
>         2015-10-19      draft-jjmb-v6ops-unique-ipv6-prefix-per-host
>         2015-10-19      draft-xu-v6ops-dslite-redundancy
>         2015-10-15      draft-gont-v6ops-ipv6-ehs-packet-drops
>         2015-10-12      draft-herbert-nvo3-ila
>         2015-10-10      draft-bao-v6ops-rfc6145bis
>         2015-09-21      draft-ybai-v6ops-ipv6-for-openstack
>