**Session Date/Time:** 23 Feb 2026 15:00 # [IOTDIR](../wg/iotdir.html) ## Summary This was a pre-IETF 125 IOTDIR Directorate meeting to provide updates on various IETF Working Groups (WGs) and IRTF Research Groups (RGs) relevant to IoT, and to introduce the SL.I.C.E. project, a European research infrastructure for reproducible experimentation in digital infrastructures, including IoT. The session also covered administrative announcements and discussions on potential collaborations. ## Key Discussion Points * **Administrative Updates** * Tommy Jensen was welcomed as the new Area Director. Thanks were extended to Eric and Samita for their contributions. * A reminder was issued for directorate members to promptly accept or decline review assignments and to consider reviewing documents even if not feeling like a subject matter expert. * **Working Group Updates** * **6Lo WG (Carles)**: * Will meet at IETF 125. * Two new RFCs published: RFC 9926 (IPv6 Neighbor Discovery Prefix Registration) and RFC 9927 (fixing CFLAG in EARO). * Path-Aware Semantic Addressing (PASA) for LLMs passed WG Last Call, Shepard write-up ready, held pending Generic Address Assignment Option (GAO) publication. * GAO for SIXLO PAN-MD is nearing publication, pending one final discussion, to be requested with PASA. * "Transmission of SHIC compressed packets over 15.4 networks" was updated for review and aligned with SHIC architecture terminology. * "Transmission of IPv6 packets over short-range optical wireless communications" (visible light communication) will be updated before the next cutoff. * "Transmission of IPv6 over multi-drop serial bus token passing MSTP networks" was recently adopted, intended to obsolete RFC 8163 (part of BACnet fixes/terminology updates). * **SDF WG (Michael)**: * Held monthly virtual interim meetings. * SDF 1.0 was published as an RFC (later confirmed to be RFC 9934). * Focus on "digital twin non-affordance mapping" for describing what is *not* present or other kinds of things. * "Non-IP control" (NIPC) document was renamed to reflect a broader scope of semantic translation (e.g., Zigbee to SenML), including IPv4 to IPv6 or NAT scenarios. * Hackathon work is planned for Vienna. * **CoRE WG (Marco)**: * RFC 9876 was published in November (CoAP fixes and IANA registry). * Two documents on CoAP over DNS advanced to RFC Editor status. * Four documents were approved for publication via ISG evaluation: Constrained resource identifiers, two on CoAP group communication (CoAP itself and with group OSCORE security), and "Allocation of seed ranges for pen holders" (promoted to Proposed Standard). * Two documents passed WG Last Call and await new versions; two require more WG cycles. * Two new documents were adopted in December: an informational document on non-traditional CoAP responses and a standard track document on CoAP over Bluetooth. * An ongoing WG adoption call for encoding YANG metadata in CBOR (moved from CBOR to CoRE consideration). * Working on a new CoAP option for abbreviating URI paths and a new version of CoAP over bundle protocol. * Active discussions on GitHub for CoAP corrections/clarifications. * Will meet for two sessions at IETF 125 and resume bi-weekly interims in mid-April. * **LAKE WG (Renzo)**: * No interim meeting in the last period, but will meet at IETF 125 in Shenzhen for 1.5 hours. * Five adopted documents; E-DocPSK is awaiting formal analysis, and two others are pending implementation experience. * The WG's rechartering text was agreed upon, approved by the AD, and is now undergoing internal steering group review, with adoption expected before IETF 125. A key aspect of the new charter is opening the door to quantum-resilient solutions. * **ROLL WG (Carles)**: * Will not meet at IETF 125. * "Enrollment priorities" submitted to ISG; modifications merged with use cases; "NSA extension" is in progress. * **Research Group Updates** * **T2TRG (Karsten)**: * Not meeting at IETF 125 due to limited attendance; operating via interims. * An interim is being set up to continue discussions on interaction between AI agents and IoT infrastructure, focusing on how IoT can present itself to agentic AI for useful outcomes. This interim will be after IETF 125. * "Taxonomy for manufacturer installed anchors" completed RG Last Call, with a silent response (taken as a potential consensus), and is seeking final feedback. * "Security setup on IoT devices" needs more reviews and is nearing RG Last Call. * Another interim is planned on enabling containerization and mobile code for IoT devices, with optimism for progress. * **Other SDOs and Activities** * Karsten noted a potential meeting opportunity for Sustain-Argy and T2TRG around IETF 126, focusing on the interaction between IoT devices and energy control, organized by Sustain-Argy. * Michael mentioned the IOTSF, which will have a 3-4 day anniversary event in August, September, or October (details by end of April). He also highlighted the Device Identity Forum's progress on representing security icons, certificates, signatures, and quantum safety, which might be discussed at IETF 125 in Vienna. * **SL.I.C.E. Project Introduction (Aris)** * Aris presented the SL.I.C.E. project, a renewed European initiative aiming to provide research and industrial communities with access to infrastructure for reproducible research in computer science, including IoT. * The project integrates various testbeds under a homogeneous interface, supporting experimentation from bare metal (firmware/OS images) to containerization/virtual machines. * It is in its third phase ("implementation phase"), starting June 2026 for three years, with 26 participants from 16 countries. * The project builds on previous efforts like the FIT project in France, expanding to include diverse nodes (e.g., a Madrid node with satellite LoRa for direct-to-satellite communication, including its own microsatellite). * Aris's role involves outreach to standardization bodies like the IETF. He sought feedback and ideas on how the infrastructure could be utilized for IETF protocol validation and experimentation. * Emmanuel, a participant in the previous FIT IoT-Lab effort, confirmed its utility for validating IETF protocols and suggested highlighting past reports and papers, as well as new functionalities of SL.I.C.E. The reporter suggested Aris coordinate with Emmanuel to summarize existing examples and potential uses for the IOTDIR directorate. ## Decisions and Action Items * **Decision**: Tommy Jensen formally welcomed as the new IOTDIR Area Director. * **Decision**: LAKE WG rechartering approved by the AD, now in internal ISG review, significantly broadening scope to include quantum-resilient solutions. * **Action Item**: Aris to collaborate with Emmanuel to compile an email for the IOTDIR directorate. This email should reference existing examples of IETF protocol validation using testbed frameworks similar to SL.I.C.E. and outline potential opportunities for various IETF Working Groups and Research Groups to utilize the SL.I.C.E. infrastructure for experimentation once it is more concretely available and access is homogenized. ## Next Steps * IOTDIR directorate members are encouraged to continue engaging with document reviews by accepting or declining assignments promptly and contributing feedback. * Working Groups (6Lo, SDF, CoRE, LAKE, ROLL) and Research Groups (T2TRG) will continue their planned activities, including document progression, interims, and IETF 125 sessions as scheduled. * The SL.I.C.E. project will continue its development, with funding resuming in June, and aims to establish homogenized access to its diverse testbed infrastructure to support reproducible research and IETF-related validation. * Potential collaborative meetings between Sustain-Argy and T2TRG around IETF 126 will be explored. * Activities of the IOTSF and the Device Identity Forum will be monitored for their relevance to the IETF.