RFC Series Change: Responsibility Change for the RFC Series
A Best Current Practice deletes an outdated responsibility statement from RFC 2026.
Rosen, B., "Responsibility Change for the RFC Series", BCP 9, RFC 9282, DOI 10.17487/RFC9282, June 2022, <https://www.rfc-editor.org/info/rfc9282>.
@misc{rfc9282,
series = {Request for Comments},
number = 9282,
howpublished = {RFC 9282},
publisher = {RFC Editor},
doi = {10.17487/RFC9282},
url = {https://www.rfc-editor.org/info/rfc9282},
author = {B. Rosen},
title = {{Responsibility Change for the RFC Series}},
pagetotal = 3,
year = 2022,
month = jun,
} RFC text
Contents
Internet Engineering Task Force (IETF) B. Rosen
Request for Comments: 9282 June 2022
BCP: 9
Updates: 2026
Category: Best Current Practice
ISSN: 2070-1721
Responsibility Change for the RFC Series
Abstract
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.
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9282.
Copyright Notice
Copyright (c) 2022 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. Responsibility Change
2. IANA Considerations
3. Security Considerations
4. References
4.1. Normative References
Author's Address
1. Responsibility Change
In [RFC9280], 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
[RFC2026], the sentence "RFC publication is the direct responsibility
of the RFC Editor, under the general direction of the IAB" is
deleted.
2. IANA Considerations
This document has no IANA actions.
3. Security Considerations
This document presents no security considerations.
4. References
4.1. Normative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,
<https://www.rfc-editor.org/info/rfc2026>.
[RFC9280] Saint-Andre, P., Ed., "RFC Editor Model (Version 3)",
RFC 9280, DOI 10.17487/RFC9280, June 2022,
<https://www.rfc-editor.org/info/rfc9280>.
Author's Address
Brian Rosen
470 Conrad Dr
Mars, PA 16046
United States of America
Email: br@brianrosen.net
ISO Plain Language
On this page
§1The Responsibility Change
RFC 9280 moved responsibility for the RFC Series to the RFC Series Working Group and the RFC Series Approval Board. The RFC Editor is no longer responsible for the series in the way described by the old text, and the IAB's role changed.
RFC 9282 updates Section 2.1 of RFC 2026 to reflect that change.
The RFC Series model changed, so an older sentence about responsibility was no longer accurate. This RFC removes that sentence.
§1The Sentence Removed
RFC 9282 deletes the sentence in Section 2.1 of RFC 2026 that says RFC publication is the direct responsibility of the RFC Editor under the general direction of the IAB.
The document does not provide replacement wording.
The old sentence assigning direct responsibility for publication is removed. The RFC does not add a replacement sentence.
§2IANA and Security Considerations
The RFC has no IANA actions and presents no security considerations. It changes only the responsibility sentence in Section 2.1 of RFC 2026.
This change to an organizational statement requires no IANA action and presents no security considerations.