Tech-invite3GPPspaceIETF RFCsSIP
929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 9283

IAB Charter Update for RFC Editor Model

Pages: ~3
IETF/draft-carpenter-rfced-iab-charter-09
Best Current Practice: 39
BCP 39 is also:    2850
Updates:  2850

Top   ToC   RFCv3-9283
B. Carpenter, Ed.
The University of Auckland
June 2022

IAB Charter Update for RFC Editor Model

Abstract

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 https://www.rfc-editor.org/info/rfc9283.

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.
Top   ToC   RFCv3-9283

1.  Introduction

In version 3 of the RFC Editor Model defined by [RFC 9280], the RFC Series is governed by its own mechanisms. This requires a modification to the Internet Architecture Board Charter [RFC 2850].
Also, RFC 2850 states that the RFC Editor appoints a liaison member to the IAB. This is no longer necessary.
Top   ToC   RFCv3-9283

2.  Changed Text

In Section 1.2 of [RFC 2850], the phrase "the RFC Editor," is deleted.
In Section 2 of [RFC 2850], 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 [RFC 9280].

Top   ToC   RFCv3-9283

3.  Approval

This 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.
Top   ToC   RFCv3-9283

4.  IANA Considerations

This document has no IANA actions.
Top   ToC   RFCv3-9283

5.  Security Considerations

This document should not affect the security of the Internet.
Top   ToC   RFCv3-9283

6.  Normative References

[RFC2850]
B. Carpenter, "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]
P. Saint-Andre, "RFC Editor Model (Version 3)", RFC 9280, DOI 10.17487/RFC9280, June 2022,
<https://www.rfc-editor.org/info/rfc9280>.
Top   ToC   RFCv3-9283

Acknowledgements

Useful comments were received from John Klensin, Eliot Lear, Peter Saint-Andre, Rich Salz, and others.
Top   ToC   RFCv3-9283

Author's Address

Brian E. Carpenter

The University of Auckland
PB 92019
Auckland   1142
New Zealand
Top   ToC