RFC 9282: Responsibility Change for the RFC Series
In plain English — editorial summary, not part of the RFC
In RFC 9280, responsibility for the RFC Series moved to the RFC Series Working Group and the RFC Series Approval Board. It is no longer the responsibility of the RFC Editor, and the role of the IAB in the RFC Series is altered. Accordingly, in Section 2.1 of RFC 2026, the sentence "RFC publication is the direct responsibility of the RFC Editor, under the general direction of the IAB" is deleted.
Document record
- Document ID
- RFC9282
- Published
- June 2022
- Authors
- B. Rosen
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 3
- Also known as
- BCP9
- Updates:
- RFC 2026
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9880Semantic Definition Format (SDF) for Data and Interactions of ThingsCurrent
January 2026
- RFC 2450Proposed TLA and NLA Assignment RuleCurrent
December 1998
- RFC 8280Research into Human Rights Protocol ConsiderationsUpdated
October 2017
- RFC 2768Network Policy and Services: A Report of a Workshop on MiddlewareCurrent
February 2000
- RFC 2551The Roman Standards Process -- Revision IIICurrent
April 1999
- RFC 2316Report of the IAB Security Architecture WorkshopCurrent
April 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?