**Session Date/Time:** 14 Mar 2023 18:00

# [TOOLS](../wg/tools.html)

## Summary

The TOOLS working group meeting covered critical updates on infrastructure migrations and tooling development. Key discussions included performance issues with www.ietf.org and plans for migration to nginx, a proposal to discontinue large data dumps in favor of API access, and the ongoing migration of DNS services to Cloudflare and the Data Tracker to a new PostgreSQL/Django 4 platform. Updates were also provided on the RFC tools refresh, the new GitHub projects page for planning, and various auto tools and wiki migrations. Decisions were made regarding the direction of infrastructure upgrades and communication of project plans.

## Key Discussion Points

*   **www.ietf.org Performance Issues:**
    *   Recent slowness around the draft submission deadline was observed due to Apache/Cloudflare configuration changes.
    *   Temporary Apache configuration changes by Glenn have been implemented as a stop-gap.
    *   Cloudflare caching configurations are being adjusted to improve origin shielding.
    *   The long-term solution proposed is to migrate www.ietf.org from Apache to nginx, as mod_proxy is hypothesized to be a bottleneck given the site's architecture. A plan team will be formed to assess if this can occur before IETF 116 or post-116.
*   **Large Data Artifacts/Dumps:**
    *   A discussion was initiated on the continued utility of producing very large, monolithic data dumps (e.g., text, XML, JSON files of all working group charters, RFC metadata).
    *   **Proposal:** Stop generating these large dumps and instead encourage users to leverage modern APIs for incremental data access, with initial full sync and subsequent API updates.
    *   A sense of those present indicated support for exploring this.
*   **Primary DNS Services Migration to Cloudflare:**
    *   Progress is being made on transferring domains away from current registrars to enable full utilization of Cloudflare's DNSSEC capabilities.
    *   One active domain is in the process of transfer.
    *   Further domain transfers are planned to resume after IETF 116 to avoid disruption.
    *   Nick has developed GitHub Actions tooling using Cloudflare APIs for traceable, change-controlled zone configuration.
*   **PostgreSQL Database and Data Tracker Migration:**
    *   A new PostgreSQL cluster was successfully built on ietfa with modern configuration and defaults (checksums, replication readiness).
    *   Testing of the Data Tracker migration to this new Postgres cluster and Django 4 is scheduled for later this week.
    *   The estimated downtime for the production move on April 11th is still in the "large tens of minutes" range, with a conservative estimate of up to 1.5 hours, hoping for a quicker actual time.
    *   Action items include investigating Wagtail websites' Cloudflare integration for better caching and pre-populating edge caches.
*   **RFC Tools Refresh Project:**
    *   Jay has sent a note to the tools-discuss list outlining the implementation plan.
    *   User stories are being developed, and discussions with community members and the RPC will take place during IETF 116 to ensure shared understanding and proper implementation.
    *   Implementation will begin after the PostgreSQL and Django 4 Data Tracker migration, leveraging the new platform capabilities.
    *   **Discussion:** The location of Errata data was raised; initial thought is that it should live with RFC data in the Data Tracker, pending further conversations.
*   **Tools Team GitHub Projects Page:**
    *   A draft GitHub projects page was presented as a high-level communication tool for the TOOLS team's plans over several IETF cycles.
    *   Feedback was positive, noting its utility for conveying large tasks, but suggested adding descriptions for unfamiliar items and a README.
    *   The chair will present this at the Working Group Chairs lunch.
*   **RFI for Infrastructure Strategy:** Responses have been received, and a team has been formed to digest them and plan next steps.
*   **Tools Help Alias:** The number of support addresses has been simplified, with `tools-help` as the primary alias now in place. Footers in Data Tracker are being updated.
*   **IETF 116 Transcription Trial:** IETF 116 will trial transcription. Feedback will be gathered post-meeting for potential future development. Consideration for integrating transcripts into meeting minutes was noted.
*   **Wiki Migration:** The Track Wiki migration to wiki.js is winding down, with the final archiving of old Track wikis planned. One working group still requires assistance with content transition.
*   **Data Tracker Updates:** Ongoing rapid development, with another release expected this week. The major April 11th release will be the next significant deployment.
*   **Auto Tools (ID Nits, RFC Diff, XML2RFC):**
    *   Bug fixes for GitHub workflows, ID Nits, and RFC Diff.
    *   Timeouts (20 seconds) implemented for ID Nits to fall back to RFC Diff if slow.
    *   XML2RFC has seen a new release, with the next planned post-IETF 116.
    *   **Font Update:** A new font (Noto Math symbols) will be added to XML2RFC, requiring a separate repository for IETF-maintained fonts due to upstream archiving.
    *   **Concern:** If the Noto Math font release post-116 would block publication, this needs to be addressed urgently with the RPC.
*   **IAB Website:** Multi-site setup for migrating the IAB website to wiki.js is currently under testing.
*   **Mail Archive:** Recent release includes new pages displaying statistics (subscribers, posts per list) to replace parts of the historical IMR reports, integrating with Data Tracker.
*   **Yang Catalog:** Recent focus has been on user interface improvements, particularly search functionality and accurately indicating the official status of YANG modules.
*   **IMAP User Remapping/Authentication:** Progress on an API-based authentication system for the IMAP server, moving away from direct database interaction. This will eventually support user remapping.

## Decisions and Action Items

*   **Decision:** Form a plan team for migrating www.ietf.org from Apache to nginx.
*   **Decision (Proposed):** Explore stopping the generation of large, monolithic data dumps in favor of API-centric access. This proposal will be sent to the tools-discuss list for broader feedback.
*   **Decision (Tentative):** The Errata data should live with the RFC data within the Data Tracker. Further discussions with relevant parties will continue at IETF 116.
*   **Action Item:** Chair to send the proposal regarding large data artifacts to the tools-discuss mailing list.
*   **Action Item:** Chair to present the GitHub Projects page at the Working Group Chairs lunch.
*   **Action Item:** Kasar to coordinate with the RPC to determine if the XML2RFC Noto Math font release schedule (post-IETF 116) will block any publications and adjust as needed.
*   **Action Item:** Chair to disseminate the GitHub Projects page link more widely for additional feedback.

## Next Steps

*   Further development and implementation of www.ietf.org migration to nginx (post-IETF 116).
*   Complete the transfer of remaining DNS domains to Cloudflare (post-IETF 116).
*   Perform the production migration of Data Tracker to PostgreSQL and Django 4 on April 11th.
*   Begin implementation of RFC tools refresh project components (post-IETF 116 and Data Tracker migration).
*   Gather feedback on the IETF 116 transcription trial to inform future development.
*   Continue work on the IMAP server authentication API, leading to user remapping.
*   Address any outstanding content migration issues for wikis.