RFC 9283

RFC 9283: IAB Charter Update for RFC Editor Model 🎀

• RFC number and title: RFC 9283, "IAB Charter Update for RFC Editor Model" ✨
• Authors: B. Carpenter, Ed., of the Univ. of Auckland 💖
• Category: Best Current Practice (it's BCP 39) 👑
• Date: June 2022 🌸
• Updates: 2850 🦋
• ISSN: 2070-1721
• Published by: Internet Engineering Task Force (IETF) 🧚

---

Abstract 💅

okay so this doc updates the IAB Charter (RFC 2850) so it matches version 3 of the RFC Editor Model (RFC 9280). bestie, that's the whole vibe 🫶

Status of This Memo 🌈

This is an Internet Best Current Practice, so it's an official IETF best practice doc 💜

It's a product of the IETF, which means it represents what the IETF community agreed on. It got public review and the IESG approved it for publication. If you want more on BCPs, check out Section 2 of RFC 7841 🔥

You can find the current status, any errata, and a place to send feedback at https://www.rfc-editor.org/info/rfc9283 ✨

Copyright Notice 🎀

Copyright (c) 2022 IETF Trust and the people listed as document authors. All rights reserved 💅

This doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) as they stood on the publication date. Read those carefully because they spell out your rights and restrictions, no cap 🙈

Any Code Components pulled out of this doc have to include Revised BSD License text, as described in Section 4.e of the Trust Legal Provisions. They come with no warranty, as the Revised BSD License describes 🦋

Table of Contents 🧚

1.  Introduction
2.  Changed Text
3.  Approval
4.  IANA Considerations
5.  Security Considerations
6.  Normative References
Acknowledgements
Author's Address

1. Introduction 🌸

okay so in version 3 of the RFC Editor Model, defined by [RFC9280], the RFC Series runs on its own mechanisms. That means the Internet Architecture Board Charter [RFC2850] needs a tweak 💖

Also, RFC 2850 says the RFC Editor appoints a liaison member to the IAB. That's no longer needed, so it's gone ✨

2. Changed Text 💖

Here's the edit list, so you can see exactly what changes ✨

In Section 1.2 ("Ex-Officio and Liaison members") of [RFC2850], the phrase "the RFC Editor," is deleted 🌸

In Section 2 ("The Role of the IAB") of [RFC2850], under the heading "(d) RFC Series and IANA", this sentence:

|  The IAB must approve the appointment of an organization to act as
|  RFC Editor and the general policy followed by the RFC Editor.

gets replaced by:

|  The RFC Editor function is defined under the authority of the IAB
|  by [RFC9280].

3. Approval 👑

This doc is published as an IETF Best Current Practice. The IAB also approved it, and the Board of Trustees of the Internet Society acknowledged it 🔥

4. IANA Considerations 🦋

This doc has no IANA actions, so nothing to do there 💅

5. Security Considerations 🙈

This doc should not affect the security of the Internet. Phew, no drama here 💀

6. Normative References 🌈

[RFC2850]  Internet Architecture Board and B. Carpenter, Ed.,
           "Charter of the Internet Architecture Board (IAB)",
           BCP 39, RFC 2850, DOI 10.17487/RFC2850, May 2000,
           <https://www.rfc-editor.org/info/rfc2850>.

[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>.

Acknowledgements 💜

Useful comments came from John Klensin, Eliot Lear, Peter Saint-Andre, Rich Salz, and others. Thank you, besties 🫶

Author's Address 🧚

Brian E. Carpenter (editor)
The University of Auckland
School of Computer Science
PB 92019
Auckland 1142
New Zealand
Email: brian.e.carpenter@gmail.com