[TOOLS-DEVELOPMENT] Tools Team Report -- 29 April 2019

Russ Housley <housley@vigilsec.com> Mon, 29 April 2019 17:32 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 21F651205EB for <tools-development@ietfa.amsl.com>; Mon, 29 Apr 2019 10:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id p8LpOVSOjHjt for <tools-development@ietfa.amsl.com>; Mon, 29 Apr 2019 10:32:24 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6D401204AE for <tools-development@ietf.org>; Mon, 29 Apr 2019 10:32:23 -0700 (PDT)
Received: from localhost (localhost []) by mail.smeinc.net (Postfix) with ESMTP id 9CEC0300AE8 for <tools-development@ietf.org>; Mon, 29 Apr 2019 13:14:05 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([]) by localhost (mail.smeinc.net []) (amavisd-new, port 10026) with ESMTP id dsUzss_eEwws for <tools-development@ietf.org>; Mon, 29 Apr 2019 13:14:03 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown []) by mail.smeinc.net (Postfix) with ESMTPSA id CC5EB300A11; Mon, 29 Apr 2019 13:14:03 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Message-Id: <FF8A2C65-783D-4B6C-8FF5-EDA2FF6FF931@vigilsec.com>
Date: Mon, 29 Apr 2019 13:32:20 -0400
Cc: IESG <iesg@ietf.org>, IETF Tools Development <tools-development@ietf.org>
To: IETF Chair <chair@ietf.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/1b1YPzj974gPux-f9Ntk9GnII8g>
Subject: [TOOLS-DEVELOPMENT] Tools Team Report -- 29 April 2019
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: Mon, 29 Apr 2019 17:32:27 -0000

Tools Team Report -- 29 April 2019

1. Datatracker Projects
   - The plan was recently updated.
     -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN
     -- Bids for Meeting Application Improvements were received and
        evaluated, and then the Interim LLC Executive Director
        negotiated a contract.  Work will begin shortly.
     -- An RFP for IRSG balloting was just released.  Proposals are
        due on 16 May 2019, and we expect work to begin in June.   
     -- One thing to highlight is the increased the priority of the
        transition from Python 2 to Python 3.  This increased priority
        is because Python 2 is being officially deprecated, and it 
        will not receive maintenance starting January 2020.

2. Community & Other Projects
   - The Secretariat deployed the latest website deliverable from
     Torchbox.   This uncovered a mess with redirects between Wagtail
     and Apache.  Glen Barney from the Secretariat IT staff will begin
     a significant clean up effort today; it should finish tomorrow.
3. RFC Services Projects
   - Support for the v3 schema was enabled for I-D submission during
     IETF 104.  The IESG needs to make a policy decision about when I-Ds
     in this new format can be submitted to the IESG for publication on
     the IETF stream.
   - The RFC Production Center is testing the tools related to the new
   - The Tools Team is working on a Statement of Work for the security
     review of tools used by the RFC Production Center.  The tools used
     for the new format will be reviewed since the ones related to the
     old format are about to be put in mothballs.
   - Bids for tools for rendering errata in a more useful way were
     received last week, and they are being evaluated right now.  We
     expect a contract to be negotiated in May 2019, and then work to
     begin the same month.

4. Server Infrastructure
   - The custom DMARC-handling software was deployed for all mail lists
     in June 2018, but there is a desire to move away from the custom
     software to ARC.  The ARC software cannot be configured to handle
     just a few of our mail lists.  Requirements were provided to the
     ARC developers, but so far, they have not offered a release date.
     Alexey continues to try to get a response from the ARC developers,
     but so far we are only getting silence.  This has not changed in
     many months; maybe we will be using our custom code forever.

5. YANG Catalog
   - Operation of the yangcatalog.org was to transferred to the IETF
     Secretariat.  A few significant things to highlight:
     -- A YANG Catalog support contractor is under contract.
     -- The yangcatalog.org service is running on different hardware
        than ietf.org.  It will be "in the cloud."  This will allow the
        Tools Team to determine whether this is a useful management
        model for other IETF-related services.
   - The registration for yangcatalog.com has been transferred to the
     IETF Trust.