rfc9920v2.txt		rfc9920.txt
	Editorial Stream P. Hoffman		Editorial Stream P. Hoffman
	Request for Comments: 9920 ICANN		Request for Comments: 9920 ICANN
	Obsoletes: 9280 A. Rossi		Obsoletes: 9280 A. Rossi
	Updates: 7841, 7991, 7992, 7993, 7994, RFC Series Consulting Editor		Updates: 7841, 7991, 7992, 7993, 7994, RFC Series Consulting Editor
	7995, 7996, 7997, 8729, 8730, December 2025		7995, 7996, 7997, 8729, 8730, February 2026
	9720		9720
	Category: Informational		Category: Informational
	ISSN: 2070-1721		ISSN: 2070-1721
	RFC Editor Model (Version 3)		RFC Editor Model (Version 3)
	Abstract		Abstract
	This document specifies version 3 of the RFC Editor Model. The model		This document specifies version 3 of the RFC Editor Model. The model
	defines two high-level tasks related to the RFC Series. First,		defines two high-level tasks related to the RFC Series. First,
	skipping to change at line 54 ¶		skipping to change at line 54 ¶
	approved by the RFC Series Approval Board. Such documents are not		approved by the RFC Series Approval Board. Such documents are not
	candidates for any level of Internet Standard; see Section 2 of RFC		candidates for any level of Internet Standard; see Section 2 of RFC
	7841.		7841.
	Information about the current status of this document, any errata,		Information about the current status of this document, any errata,
	and how to provide feedback on it may be obtained at		and how to provide feedback on it may be obtained at
	https://www.rfc-editor.org/info/rfc9920.		https://www.rfc-editor.org/info/rfc9920.
	Copyright Notice		Copyright Notice
	Copyright (c) 2025 IETF Trust and the persons identified as the		Copyright (c) 2026 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document.		to this document.
	Table of Contents		Table of Contents
	skipping to change at line 182 ¶		skipping to change at line 182 ¶
	1.1. Changes to RFC 9280		1.1. Changes to RFC 9280
	This section details the changes made to [RFC9280] by the RSWG		This section details the changes made to [RFC9280] by the RSWG
	starting in 2022. If you are not interested in how this document was		starting in 2022. If you are not interested in how this document was
	changed, skip directly to Section 2.		changed, skip directly to Section 2.
	[RFC9280] contained significant changes to the publication model for		[RFC9280] contained significant changes to the publication model for
	RFCs. Those changes created new structures and new processes for the		RFCs. Those changes created new structures and new processes for the
	publication of RFCs. As these structures and processes have been		publication of RFCs. As these structures and processes have been
	exercised, the community has found places where they can might be		exercised, the community has found places where they can be improved.
	improved. In addition, gaps in some of the processes have been		In addition, gaps in some of the processes have been found. This
	found. This document updates [RFC9280] based on these findings.		document updates [RFC9280] based on these findings.
	The organization of this RFC is different from typical RFCs in order		The organization of this RFC is different from typical RFCs in order
	to keep the section numbering the same as [RFC9280]. To keep the		to keep the section numbering the same as [RFC9280]. To keep the
	section numbering the same, the Introduction section is much longer,		section numbering the same, the Introduction section is much longer,
	with several subsections that refer to the main body.		with several subsections that refer to the main body.
	The remainder of this introduction is a list of changes to [RFC9280].		The remainder of this introduction is a list of changes to [RFC9280].
	Those changes are instantiated in the rest of the document, with		Those changes are instantiated in the rest of the document, with
	cross-references between the list of changes and the main body.		cross-references between the list of changes and the main body.
	skipping to change at line 300 ¶		skipping to change at line 300 ¶
	| If the RPC is responsible for interpreting policy decisions at		| If the RPC is responsible for interpreting policy decisions at
	| both the document and editorial process tooling level, conflicts		| both the document and editorial process tooling level, conflicts
	| on either level will involve interpretation of written policy (or		| on either level will involve interpretation of written policy (or
	| the acknowledgment that policy does not exist to cover a given		| the acknowledgment that policy does not exist to cover a given
	| situation). In any case, the conflict resolution will now use the		| situation). In any case, the conflict resolution will now use the
	| same path of appeal: to the RSAB.		| same path of appeal: to the RSAB.
	1.2.3. RFC Consumers		1.2.3. RFC Consumers
	The text in Section 3.3 of this document, concerning RFC consumers,		This text is reflected in Section 3.3 of this document:
	is all new.
			| The IETF mission statement [RFC3935] is clear that the documents
			| it produces are intended to be consumed by anyone who wishes to
			| implement an IETF protocol or operational recommendation:
			|
			| to produce high quality, relevant technical and engineering
			| documents that influence the way people design, use, and manage
			| the Internet in such a way as to make the Internet work better.
			|
			| Section 3.2.1 introduces the term "consumers of RFCs", referring
			| to them as "constituent stakeholders" who should be considered by
			| the RSAB when approving Editorial Stream policy documents.
			|
			| "Consumers of RFCs" is now defined to mean those people who read
			| RFCs to understand, implement, critique, and research the
			| protocols, operational practices, and other content as found in
			| RFCs.
			|
			| The policy to be followed by the RFC publication streams and RFC
			| Editor in respect to consumers of RFCs is as follows:
			|
			| * Consumers of RFCs MUST be considered as separate constituent
			| stakeholders from IETF/IRTF participants. While IETF/IRTF
			| participants and others involved in the development and
			| production of RFCs may be consumers of RFCs, the two are
			| distinct, overlapping sets.
			|
			| * The RFC Editor website (https://www.rfc-editor.org) MUST be
			| primarily focused on consumers of RFCs.
			|
			| * Consumers of RFCs MUST NOT be required or expected to become
			| IETF/IRTF participants unless they wish to extend, update, or
			| modify an RFC.
	1.3. Updates to RFC 9720		1.3. Updates to RFC 9720
	[RFC9720], "RFC Formats and Versions", updates [RFC9280]. This		[RFC9720], "RFC Formats and Versions", updates [RFC9280]. This
	document updates [RFC9720].		document updates [RFC9720].
	1.3.1. RFCs May Be Reissued		1.3.1. RFCs May Be Reissued
	Section 7.6 of [RFC9280] says:		Section 7.6 of [RFC9280] says:
	skipping to change at line 331 ¶		skipping to change at line 363 ¶
	A new policy is added to Section 7 of this document:		A new policy is added to Section 7 of this document:
	| 7.8. Consistency		| 7.8. Consistency
	|		|
	| RFCs are copyedited, formatted, and then published. They may be		| RFCs are copyedited, formatted, and then published. They may be
	| reissued to maintain a consistent presentation.		| reissued to maintain a consistent presentation.
	1.4. Purview of the RSWG and RSAB		1.4. Purview of the RSWG and RSAB
	Section 3 says:		Section 3 of [RFC9280] says:
	| Policies under the purview of the RSWG and RSAB might include, but		| Policies under the purview of the RSWG and RSAB might include, but
	| are not limited to, document formats, processes for publication		| are not limited to, document formats, processes for publication
	| and dissemination of RFCs, and overall management of the RFC		| and dissemination of RFCs, and overall management of the RFC
	| Series.		| Series.
	The following is added to Section 3 of this document immediately		The following is added to Section 3 of this document immediately
	following that sentence:		following that sentence:
	| Such policies will not include detailed technical specifications,		| Such policies will not include detailed technical specifications,
End of changes. 5 change blocks.
	8 lines changed or deleted		40 lines changed or added
This html diff was produced by rfcdiff 1.48.