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 [email protected] or to the public administrative discussion 
list [email protected].

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

2. Second consultation on Remote Rooms for IETF Meetings - 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 send your feedback to the IETF Executive Director at 
[email protected]. If you wish to discuss any of this on a public list 
then please use the [email protected] list.

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

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 [email protected] or to the public tools discussion list 
[email protected].

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

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 [email protected] or to the public tools discussion list 
[email protected].

-- 
Jay Daley
[email protected]
www.ietf.org



_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to