[saag] FWIW: Useful little script

Alan DeKok <aland@deployingradius.com> Tue, 07 August 2012 04:55 UTC

Return-Path: <aland@deployingradius.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6137021F85A8 for <saag@ietfa.amsl.com>; Mon, 6 Aug 2012 21:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level:
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFGrnq2IfH50 for <saag@ietfa.amsl.com>; Mon, 6 Aug 2012 21:55:43 -0700 (PDT)
Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by ietfa.amsl.com (Postfix) with ESMTP id 3CCA721F85A3 for <saag@ietf.org>; Mon, 6 Aug 2012 21:55:43 -0700 (PDT)
Message-ID: <50209FB2.6040805@deployingradius.com>
Date: Tue, 07 Aug 2012 06:55:14 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "saag@ietf.org" <saag@ietf.org>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [saag] FWIW: Useful little script
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 04:55:45 -0000

  The aaa-doctors have historically tracked and reviewd AAA related
documents.  The tracking can be difficult, as many working groups define
RADIUS or Diameter changes without talking to the RADEXT or DIME working
groups.

  In order to help, I've written a hacky little script.  The goal is to
search WG drafts for references to certain RFCs.  e.g. 2865 (RADIUS).
Ones matching that criteria are selected.  BUT drafts in the RADEXT and
DIME working groups are ignored, as we presume the RADIUS people already
monitor RADIUS drafts.

  The script is available on github:

https://github.com/alandekok/ietf-tech-report

  There's a README with documentation.  Feedback is appreciated.

  Some example output:

$ ./ietf-tech-report -r radius
draft-ietf-dhc-dhcpv6-radius-opt-01               Active	
draft-ietf-softwire-6rd-radius-attrib-05          Active	
draft-ietf-abfab-arch-03                          Active	
draft-ietf-abfab-aaa-saml-03                      Active	
draft-ietf-netmod-system-mgmt-02                  Active	
draft-ietf-abfab-gss-eap-08                       In IESG processing -
ID Tracker state <Approved-announcement to be sent::Point Raised -
writeup needed>	


$ ./ietf-tech-report -r yang
draft-ietf-netmod-routing-cfg-04                  Active	
draft-ietf-netmod-iana-if-type-04                 Active	
draft-ietf-netmod-system-mgmt-02                  Active	
draft-ietf-netmod-interfaces-cfg-05               Active	
draft-ietf-ipfix-configuration-model-11           In IESG processing -
ID Tracker state <RFC Ed Queue>	
draft-ietf-netmod-iana-timezones-00               Active	
draft-ietf-netmod-snmp-cfg-00                     Active	
draft-ietf-netmod-ip-cfg-05                       Active