9:30 - 9:40: Agenda bashing

9:40 - 9:50: Chairs' welcome, opening and panellists' introductions

9:50 - 10:10 : Panellist Statements on the topic: "How does standardisation look in an LLM-enabled future?" (7 mins each)

10 - 11 : Discussion: lead by the chairs and for the panellists to discuss with each other.

11- 11:30 : Q&A

Bios

Abstracts/statements

*Jie Bian
RFCs don’t usually contain much text that explains the reasons behind the design decisions that were taken. Yet, making these rationales visible is vital for several reasons: it supports the newcomers to the IETF, fosters transparency and trust, and enables more informed participation. When the underlying reasonings are clearly articulated, newcomers gain insight into trade-offs and historical context, while implementers can better align their work with the intent of the specification rather than relying solely on prescriptive rules. Beyond immediate benefits, preserving and exposing design rationales is crucial for the evolution of next-generation protocols. Without access to the considerations that shaped earlier standards, future designers risk repeating past mistakes or overlooking subtle compromises that influenced prior decisions.

Building on the above work, we also explored leveraging LLMs for auto-editing RFCs, enabling models to refine draft text based on feedback from WG members. This capability has the potential to significantly accelerate iterative development of Internet-Drafts and streamline IETF workflows.

*Jaime Jiménez
This presentation demonstrates how AI agents can assist with IETF specification making process, based on practical experience. It covers where AI can immediately help with examples. It also discusses practical adoption steps and challenges.

*Joseph Potvin
LLM-Assisted Transformation of IETF Standards into Machine-Processable Rules-as-Data
Developers are challenged to maintain awareness and practical applicability of requirements embedded in the prose of standards, such as more than 9,000 RFCs/BCPs. The Data With Direction Specification (DWDS) is a framework for transforming normative rules into consistent, canonical 'Rules-as-Data' optimized for machine processing, while also being human-auditable. During unit testing, developers could get specific "in effect", "applicable" and "invoked" requirements in standards dynamically discovered, fetched, delivered inside existing developer toolchains, for conformance support and validation. The free/libre/open source reference implementation involves: Rule-as-Data (canonical data structures), RuleMaker (authoring IDE), RuleReserve (IPFS-based distributed storage), and RuleTaker (edge-resident embedded discovery component). Rules-as-Data will be illustrated with a BGP-4 propagation rule example from RFC 4271.

We use LLMs as linguistic tools (not oracles) with human-in-the-loop iteration to: (1) distill RFC prose into discrete declarative statements of Input Conditions and Output Assertions; (2) structure each with a six-element finite grammar; (3) generate a concise interpretive explanation; and (4) cycle human-validated results back into LLMs to iteratively improve performance with (1), (2) and (3) for emergent scalability. Current R&D involves integration of the Model Context Protocol.