IAB Charter Update for RFC Editor Model

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 6 August 2022.¶

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

In the RFC Editor model defined by [I-D.iab-rfcefdp-rfced-model], the RFC Series is now governed by its own mechanisms. This requires a modification to the Internet Architecture Board charter [RFC2850].¶

Note that RFC 2850 states that the RFC Editor appoints a liaison member to the IAB. This does not change, but refers to the RFC Editor function as described in [I-D.iab-rfcefdp-rfced-model].¶

2. Changed Text

In Section 2 of RFC 2850, entitled "The Role of the IAB", under the sub-heading "(b) 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 [I-D.iab-rfcefdp-rfced-model]."¶

3. Approval

This document is published as an IETF Best Current Practice and has also been approved by the IAB.¶

4. IANA Considerations

This document makes no request of IANA.¶

5. Security Considerations

This document should not affect the security of the Internet.¶

6. Acknowledgements

Useful comments were received from John Klensin, Eliot Lear, Peter Saint-Andre, Rich Salz and others.¶

Appendix A. Change Log [RFC Editor: please remove]

Author's Address