IAB Charter Update for RFC Editor ModelThe University of AucklandSchool of Computer SciencePB 92019Auckland1142New Zealandbrian.e.carpenter@gmail.com
General
This document updates the IAB Charter (RFC 2850) to
be consistent with version 3 of the RFC Editor Model
(RFC 9280).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
.
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
() 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
. Introduction
. Changed Text
. Approval
. IANA Considerations
. Security Considerations
. Normative References
Acknowledgements
Author's Address
IntroductionIn version 3 of the RFC Editor Model defined by ,
the RFC Series is governed by its own mechanisms. This requires
a modification to the Internet Architecture Board Charter .Also, RFC 2850 states that the RFC Editor appoints a liaison member
to the IAB. This is no longer necessary.Changed TextIn Section "Ex-Officio and Liaison members" of ,
the phrase "the RFC Editor," is deleted.In Section "The Role of the IAB" of , under the heading
"(d) RFC Series and IANA", the following sentence:
The IAB must approve the appointment of an organization to
act as RFC Editor and the general policy followed by the RFC Editor.
is replaced by:
The RFC Editor function is defined under the authority of the
IAB by .
ApprovalThis document is published as an IETF Best Current Practice. It has
also been approved by the IAB and acknowledged by the Board of
Trustees of the Internet Society.IANA ConsiderationsThis document has no IANA actions.Security ConsiderationsThis document should not affect the security of the Internet.Normative ReferencesCharter of the Internet Architecture Board (IAB)Internet Architecture BoardThis memo documents the composition, selection, roles, and organization of the Internet Architecture Board. It replaces RFC 1601. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.RFC Editor Model (Version 3)AcknowledgementsUseful comments were received from
, , , ,
and others.Author's AddressThe University of AucklandSchool of Computer SciencePB 92019Auckland1142New Zealandbrian.e.carpenter@gmail.com