Organization of IETF Process Documents

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 4 April 2025.¶

Copyright Notice

Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

The IETF has a large number of documents (mainly RFCs) devoted to its standard process, its rules and procedures in general, and how it does its work. Some of these are BCPs, some of them are Informational RFCs, with occasional Experimental RFCs. In addition there are IESG Statements for specific topics, summaries of processes and procedures on the IETF web site, presentations made at IETF meetings or in educational material, snippets in email archives, unwritten rules, and external information such as this.¶

At a rough estimate, to have a complete understanding of IETF processes and procedures, a person would need to consult about 65 BCPs and RFCs -- there is an out of date informal list. There are also at least 30 relevant IESG statements.¶

This situation is clearly problematic. Obviously it is a major stumbling block for newcomers. Even for people with years of IETF participation it can be a source of confusion, mistakes, and wasted time.¶

This draft suggests that at the very least, the IETF needs an organizing principle or framework for its process and procedural documents.¶

Beyond that it seems desirable to start a project, which would take many years to complete, of consolidating documents (where that is feasible) and ensuring that they fit together into a common framework that will help newcomers and experienced participants alike.¶

Furthermore, a well-maintained guide to the IETF process is needed, for newcomers and experienced participants alike. Maintaining such a guide as part of the IETF web site would seem appropriate.¶

2. Framework

The idea is that process documents would be organized to fit into one of a set of major topics, with as little overlap as possible. The following list of topics is only a suggestion.¶

• Workflow in the IETF¶

• Bodies involved in the process¶

• Document types¶

• Standards track documents¶

• Review and approval process¶

• Intellectual Property Rights¶

• Conduct of participants¶

• Publication process (RFC Editor)¶

• Parameter registration process (IANA)¶

• Meetings¶

• Administration and support¶

• Process for modifying process and procedures¶

3. Consolidation

[I-D.rsalz-2026bis] and [I-D.rsalz-2418bis] are good examples of consolidation. If all the relevant RFCs and IESG statements could be consolidated in this way, resulting in say 10 or 15 documents fitting into the framework above, future participants would face much less complexity.¶

There is a question of finding the effort to do this. It seems unlikely that it can be entirely performed on a voluntary basis. Most of the work is editorial in nature, and could be performed without any decisions of principle being needed. That implies that it could be performed as paid work. Any decisions of principle (such as reconciling inconsistencies between existing documents, or incorporating an IESG Statement in an RFC) must of course be subject to IETF review and consensus, as must the final documents.¶

4. Guide

The informal list of process-related documents mentioned above has been present on the IETF web site for many years. Since it was carefully written not to paraphrase or summarize content, but only to cite existing documents, it could serve as an model of how a regularly maintained guide might look. This maintenance will not involve any decisions of principle.¶

5. IANA Considerations

No IANA actions are needed.¶

6. Security Considerations

This document does not directly affect the security of the Internet.¶

7. Acknowledgements

Useful comments were received from Jay Daley, Stephen Farrell, Ted Hardie, Eliot Lear, Eric Rescorla, Rich Salz, and others.¶

8. Informative References

[I-D.rsalz-2026bis]

Salz, R. and S. O. Bradner, "The Internet Standards Process", Work in Progress, Internet-Draft, draft-rsalz-2026bis-10, 5 September 2024, <https://datatracker.ietf.org/doc/html/draft-rsalz-2026bis-10>.

[I-D.rsalz-2418bis]

Salz, R. and S. O. Bradner, "IETF Working Group Guidelines and Procedures", Work in Progress, Internet-Draft, draft-rsalz-2418bis-05, 9 September 2024, <https://datatracker.ietf.org/doc/html/draft-rsalz-2418bis-05>.

Appendix A. Change Log [RFC Editor: please remove]

Author's Address