Session Date/Time: 20 Aug 2025 19:00

RPC

Summary

The RPC community call provided updates on several key initiatives aimed at streamlining document processing and enhancing author experience. Major discussions included the successful rollout of the new intake form, the upcoming acceptance of cramdown-rfc submissions, and the roadmap for integrating Git/GitHub into RPC workflows. A critical process update for handling errata reports was announced. The meeting concluded with a demonstration of the new rfceditor.org website (RED) and a brief but important discussion on the long-term implications of cramdown-rfc adoption and the five-digit RFC number problem.

Key Discussion Points

Intake Form Rollout: The RPC has successfully implemented an intake form for documents entering the queue, querying authors on style guidance and potential controversial text. 19 forms have been sent, with 16 replies received; over half within a day. Sarah noted the forms significantly aid in quickly identifying source code types, updated contact info, and style preferences.
Cramdown RFC Format Support:
- The RPC is conducting advanced training sessions for staff on editing cramdown-rfc files, covering complex elements like nested lists, tables, and SVG artwork.
- Pilot testing is underway with three cramdown-rfc documents in the queue.
- The new workflow involves a two-step O48 approval process: authors first review content changes in the Markdown file, then approve the final RFC XML format. This aims to ease integration with authors' GitHub repositories.
- Discussion arose regarding potential "forking" of authoring tools (XML vs. Markdown). While RFC XML remains the publication format, it was noted that 40-50% of authors may already be using cramdown-rfc. Existing documentation on authors.ietf.org focuses on RFC XML, leading to calls for more RPC-provided cramdown-rfc specific documentation. The RPC is working on internal documentation and plans to share it publicly.
Arratum Reports Process Update: Previously, RPC staff manually reviewed ARAT reports for obsoleting or updating RFCs, which was time-consuming. For example, RFC 9293 addressed 27 reports.
GitHub Roadmap: The RPC plans to leverage Git and GitHub for internal version control of documents in the queue (Phase 1). Phase 2 will open these repositories during O48 for authors who prefer a GitHub-based review process. The existing email-based O48 process will continue to be supported. More specific timelines for author interaction with GitHub were requested.
Tooling Updates:
- "Purple": A new queue management system is under development, with recent work on document labels and editor assignment import.
- "RED" (rfceditor.org): A new rfceditor.org website is being developed. A demonstration highlighted its focus on readers, easily accessible information about RFCs, fast search capabilities (including full-text search), mobile-friendliness, and a design for modern CDN deployment. The site currently draws data from Data Tracker.
RFC 9796 Publication Issue: An incomplete publication occurred where unprepped files were mistakenly placed on the public website instead of the prepped (V3 RFC XML) files. The issue was rectified, and an apology was issued, noting this was a first for V3 RFC XML processing.
Team Updates: Individual RPC editors provided updates on their current workload, documents in various stages (edit, O48, reference review), and specific cluster activities.
- Sandy noted testing a new workflow for a TSVWG document that lacked a source file: converting the text file to cramdown-rfc first, then to XML, yielding "much better XML" than id2xml.
- Karen highlighted RFC 9839 as her first document with emojis (black heart, question mark symbols) used as examples, with successful V3 processing.
Processing Statistics: The average processing time from document entry to O48 is currently 12.6 weeks, a slight decrease from 13 weeks previously.
Cramdown Archiving and Future Updates: A discussion revisited how cramdown-rfc documents, once converted to XML and published, would be handled for future updates. While current cramdown-rfc tools embed the source within the XML, the RPC acknowledges the need for a clear strategy for authors to access a cramdown-rfc representation for updates, even if the original was XML-only.
Five-Digit RFC Problem: Gene Mahoney affirmed that the RPC is "running a race" to address the five-digit RFC number problem, with significant focus on replacing tools and systems before RFC 10,000 is reached (estimated around Spring 2026). The publication rate is stable, and confidence was expressed in the work done to prepare for this transition, including the need for the wider community to adapt to RFCs without leading zeros.
RFC 10K Celebration: Ideas for celebrating RFC 10,000 are welcome via rfc-interest (with a request to avoid an April Fool's RFC for the milestone).

Decisions and Action Items

Decision: Starting September 1st, the RPC will accept cramdown-rfc file format for document submissions.
Decision: A new process for handling ARAT reports for obsoleting/updating RFCs will be implemented: authors will be asked in the intake form and again at O48 to confirm that relevant ARAT reports have been addressed or are not applicable.
Action Item: RPC will hold a working meeting in mid-September to discuss the GitHub roadmap and implementation details.
Action Item: The RPC will work on developing its own internal cramdown-rfc documentation, with a view to potentially providing public documentation on authors.ietf.org as it matures.
Action Item: The RPC will continue its focused efforts on addressing the five-digit RFC number problem, ensuring tooling and processes are updated.

Next Steps

Continue cramdown-rfc training and pilot testing, preparing for the September 1st acceptance date.
Organize and conduct the mid-September working meeting for the GitHub roadmap.
Roll out the new rfceditor.org (RED) website, with an anticipated testing opportunity at the Montreal IETF meeting.
RPC staff to continue refining and testing the new ARAT report handling process.
Community members are encouraged to send ideas for celebrating RFC 10,000 to the rfc-interest mailing list.