[TOOLS-DEVELOPMENT] Tools Team Report -- 26 May 2019

Russ Housley <housley@vigilsec.com> Sun, 26 May 2019 17:39 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F3F21200A4 for <tools-development@ietfa.amsl.com>; Sun, 26 May 2019 10:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 Ji2BFvx_x7Ky for <tools-development@ietfa.amsl.com>; Sun, 26 May 2019 10:39:12 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53D9A12009E for <tools-development@ietf.org>; Sun, 26 May 2019 10:39:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 7DB42300AAB for <tools-development@ietf.org>; Sun, 26 May 2019 13:11:23 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id u3h8bJwjHGk7 for <tools-development@ietf.org>; Sun, 26 May 2019 13:11:21 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id 4EA95300415; Sun, 26 May 2019 13:11:21 -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.11\))
Message-Id: <CD4DC6BD-37C4-42F2-86A4-3A9651B6E8C4@vigilsec.com>
Date: Sun, 26 May 2019 13:30:38 -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.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/4Ky4fs_f7WaG3aOObpsNlMftOXE>
Subject: [TOOLS-DEVELOPMENT] Tools Team Report -- 26 May 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: Sun, 26 May 2019 17:39:16 -0000

Tools Team Report -- 26 May 2019

1. Datatracker Projects
   - The plan was recently updated.
     -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN
     -- 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.
   - A contract for Meeting Application Improvements was awarded to
     IOLA.  Work will begin shortly.
   - An RFP for IRSG balloting was released and then the period to bid
     was extended to 4 June 2019.  We expect work to begin in June 2019.

2. Community & Other Projects
   - The latest website deliverable from Torchbox is complete, including
     the cleanup of messy redirects between Wagtail and Apache.
   - Handling of 404 on the Wagtail website was improved, avoiding some
     problems that could occur with dynamic links.
   - The Tools Team and the Secretariat are working on a plan for the
     best way to handle static plaintext pages, such as appeals, appeal
     responses, and implementation reports.  Current thinking is to
     manage these outside Wagtail, but the discussion is still ongoing.

3. RFC Services Projects
   - Support for the v3 schema has been enabled for I-D submission, and
     now the IESG needs to make a policy decision about when I-Ds in the
     new format can be submitted to the IESG for publication on the IETF
     stream.
   - The RFC Production Center continues to test the new format tools.
   - The Tools Team has a Statement of Work for the security of the
     tools used by the RFC Production Center.  The new format tools will
     be reviewed once the tools related to the old format are put in
     mothballs.
   - A contract for rendering errata in a more useful was awarded to
     Soaring Hawk Consulting; work began in May 2019.

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.
   - The guides.ietf.org has been deployed in its own container.  In a
     few weeks we expect to move it to hardware controlled by the
     Secretariat.  This experiment is allowing the Tools Team to
     determine whether other services can be containerized and put
     "in the cloud".

5. YANG Catalog
   - Operation of the yangcatalog.org was to transferred to the IETF
     Secretariat.  A few significant things to highlight:
     -- The yangcatalog.org service is running on different hardware
        than ietf.org; it is on a server in Canada.  This placement is
        allowing the Tools Team to determine whether other services can
        be containerized and put "in the cloud".