CORRECTED: Reminder on open IETF LLC consultations

[IETF Executive Director <[e-mail]>]

[This is a corrected version as the text for consultation 2 was incorrect on the original]


This is a reminder of the four open IETF LLC consultations:


1. Extended consultation on a Service Level Agreement (SLA) for RFC Editing and Publication - feedback due by 27 September 2026

The RFC Production Center (RPC) has had a Service Level Agreement (SLA) for document production for many years. However, the RPC has not met this SLA for some years and an analysis shows that this is primarily due to a significant increase in the work expected of the RPC. Furthermore, the old SLA excluded some key measures as the measurement in place until recently had significant gaps. Given this, the current SLA is no longer fit for purpose and needs replacing.

A consultation document has been published that provides an explanation of the old SLA, data of performance since its inception in 2016, an analysis of the issue and a proposed way forward. This is then followed by a series of questions for community feedback:

https://www.ietf.org/media/documents/Consultation_on_a_Service_Level_Agreement_SLA_for_RFC_Editing_and_Publication.pdf

Please respond either privately to the IETF LLC Board and the Executive Director at [e-mail] or to the public administrative discussion list [e-mail].

------------

2. Second consultation on Remote Rooms for IETF Meetings - feedback due by 27 September 2026

This is a request for community feedback following the Remote Rooms experiment which took place during IETF 125 in Shenzhen, China in March 2026.

The specification for Remote Rooms was developed with input gathered through community consultation and following an open call for interest, a single Remote Hub was supported that operated in Tokyo, Japan with three simultaneous Remote Rooms hosting approximately 30 participants. 

While engagement and satisfaction among participants who used the Remote Rooms was high, the experiment highlighted technical challenges and significant resource requirements for both organizers and IETF staff that require consideration for possible future editions. It also raised concerns about effects on the IETF meeting experience.

Please read the full consultation document here: 

https://www.ietf.org/media/documents/Second_Consultation_on_Remote_Rooms_for_IETF_Meetings.pdf

Please respond either privately to the IETF LLC Board and the Executive Director at [e-mail] or to the public administrative discussion list [e-mail].

------------

3. Consultation on the User Experience of IETF Tools - feedback due by 12 October 2026 

User Experience (UX) in this document covers the many aspects of IETF participant interaction with IETF Tools including user interfaces, access controls, client software requirements and usage modes (e.g. offline usage). 
IETF Tools have developed organically over many years for most of that time the user experience was designed by the developer responsible for each system. 

While developers can design functional UIs, there is a difference between that and those designed by User Experience (UX) specialists. Specialists have recently been used for the first time to design the UX for the new rfc-editor.org website.  The other aspects of the user experience have had explicit decisions and others have developed organically. While there have been some community discussions on some aspects, until now there has not been a formal process to elicit and incorporate community views into Tools development plans.

This consultation documents the current approach to the User Experience of IETF Tools, with the exception of systems performance as that is the subject of a parallel consultation, and seeks feedback on what needs to change.  Please read the full consultation document here: 

https://www.ietf.org/media/documents/Consultation_on_the_User_Experience_of_IETF_Tools.pdf

Please respond either privately to the IETF LLC Board and the Executive Director at [e-mail] or to the public tools discussion list [e-mail].

------------

4. Consultation on a Service Level Agreement for IETF Tools - feedback due by 12 October 2026 

The IETF Tools are a critical resource for the Internet standards process but SLA coverage is poor. Some small aspects have had a performance SLA, but most parts of this service have, since inception, been provided on a “best efforts” basis with formal agreements only covering capacity and incident response times, not availability and system performance as normally found in an SLA. 

This consultation closes that gap by proposing an SLA framework and some initial targets, on which community feedback is sought.

For clarity, this SLA is solely targeted at system performance and availability, not the performance of the Tools Team or their scheduling/planning of work, though it is understood that those are subjects that also require in-depth discussion with the community.

Please read the full consultation document here:

https://www.ietf.org/media/documents/Consultation_on_a_Service_Level_Agreement_for_IETF_Tools.pdf

Please respond either privately to the IETF LLC Board and the Executive Director at [e-mail] or to the public tools discussion list [e-mail].


-- 
Jay Daley
[e-mail]
www.ietf.org