**Session Date/Time:** 04 Mar 2025 19:00 # [TOOLS](../wg/tools.html) ## Summary The TOOLS working group meeting discussed the successful, though not without immediate challenges, transition of the mail processing system and the completion of the core infrastructure transition project. Updates were provided on the DataTracker's integration with blob storage, highlighting the need for asynchronous operations and data curation challenges. Significant progress was reported on the RFC Editor.org reimplementation, including necessary URL changes for future-proofing and API documentation efforts. Other key updates included the liaison management tooling, IDnits development, a new developer hire, and the ongoing RFP process for cyber security services. ## Key Discussion Points * **Email Processing System Transition:** * The mail processing system was successfully moved to a new server, completing the core infrastructure transition project initiated last year. Outages were within the expected window, and no messages were lost. * A minor issue with TLSA records not aligning with MX record changes was identified and corrected. * The new system experienced significant mail delays due to lower IO capacity compared to the previous system, exacerbated by an underlying file system event and the Internet Draft submission deadline. Efforts to address the disk IO capacity are underway. * During the delays, communication was provided via the blog, status.ietf.org, social media, and internal email, noting that archived messages were available quickly. * **Infrastructure Transition Project Completion:** * The infrastructure transition project, started early last year, is considered complete with the mail system move. * Ongoing major infrastructure improvements include DataTracker enhancements (e.g., blob storage, other techniques) and RFC Production Center tooling (e.g., addressing the RFC 10K problem). * **DataTracker Blob Storage Integration:** * A new DataTracker version has begun writing artifacts to blob storage in addition to disk, anticipating a move away from shared file systems. * The current synchronous writes (in-line with HTTP requests) will need to become asynchronous to improve user experience. This requires careful consideration for views that rely on immediate artifact availability. * Challenges in data curation, particularly with historical Internet Drafts and their varied character encodings, are being addressed to ensure proper handling by new components. * **RFC Editor.org Reimplementation and URL Paths:** * The RFC Editor.org site is being reimplemented, including its APIs, with a focus on consistency and minimizing unnecessary changes through extensive testing. * **URL Changes:** Some URL changes are necessary for future-proofing and aligning with modern web architecture (e.g., CDN utilization). * **RFC 10K Problem:** RFC IDs will no longer have leading zeros (e.g., "rfc10000" instead of "rfc00000"). Software consuming these APIs must adapt to potentially five-digit RFC IDs. * **Trailing Slashes:** All URLs leading to HTML pages will consistently end in a trailing slash. Redirects will be established for compatibility. * A change log of all API modifications will be provided, along with sample API responses, to assist developers. * **Liaison Management Tooling:** * Updates to the specification around how the community processes liaison statements (via new bis drafts from the SES and MUIA efforts) are being digested to inform requirements for new tooling. * The IAB will be identifying a new liaison to the TOOLS WG, as the current liaison coordinator will be stepping down from the IAB. * **IDnits Development:** * Nick is leading the XML work for IDnits 3. * A contractor from Admiral Studios is assisting with the text processing part. * Casara is responsible for deploying new versions of IDnits for testing. * **New Developer Hire:** * Rudy Mats, a backend developer based in Montreal, will join the team next Monday to work on DataTracker and other projects, replacing a previous developer. * **Cyber Security Services RFP:** * The RFP for cyber security services closed, with a number of bids received. * Community volunteers, Paul Wouters and Benson Muite, will assist in evaluating the proposals alongside the IETF staff, with a decision expected after IETF 122 (Bangkok). * **April TOOLS Call Schedule:** * The April TOOLS call has been moved to April 15th to avoid conflict with the RPC and Tools Retreats. * **Code Sprint Docker Environment:** * Participants for the upcoming Code Sprint before IETF 122 were advised to tear down and rebuild their Docker development environments from scratch due to radical structural changes in the container setup. ## Decisions and Action Items * **IETF Secretariat/TOOLS Team:** * Address the underlying system's disk IO capacity to resolve email delivery delays. * Implement asynchronous writes to blob storage for the DataTracker, ensuring views are updated to gracefully handle potential artifact delays. * Proceed with RFC Editor.org reimplementation, including URL changes (RFC 10K, trailing slashes) and implementing redirects for backward compatibility. * Develop and publish a comprehensive API change log for RFC Editor.org, including sample responses. * Digest updates from the liaison statement bis drafts and integrate them into the requirements for new liaison management tooling. * Evaluate bids for the Cyber Security Services RFP by after IETF 122 (Bangkok). * **IAB:** * Identify a new liaison to the TOOLS WG. * **Code Sprint Participants:** * Reset Docker development environments by tearing down and rebuilding from scratch before the Code Sprint at IETF 122. ## Next Steps * Continue improving DataTracker functionality, including further integration with blob storage. * Ongoing development of RFC Production Center tooling, specifically to address the RFC 10K problem. * Onboarding and integration of the new backend developer, Rudy Mats. * Further development and deployment of IDnits 3. * Prepare for the upcoming Code Sprint prior to IETF 122. * Hold the next TOOLS call on April 15th.