Internet-Draft termlimits October 2021
Salz Expires 23 April 2022 [Page]
Workgroup:
TBD
Internet-Draft:
draft-rsalz-termlimits-00
Published:
Intended Status:
Informational
Expires:
Author:
R. Salz
Akamai Technologies, Inc.

Term limits for IETF Leadership Positions

Abstract

This document says that nobody can be picked by NomCom for a position more than two consecutive terms.

It obsoletes some other documents, which ones are TBD.

Discussion Venues

This note is to be removed before publishing as an RFC.

Source for this draft and an issue tracker can be found at https://github.com/richsalz/draft-rsalz-termlimits.

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 23 April 2022.

Table of Contents

1. Introduction

After a person has served two consecutive terms in any NomCom-chosen position, they are ineligible to directly serve for another term in any NomCom-chosen position; there must be a gap of at least one year. This rule goes into effect starting in March, 2023.

2. Conventions and Definitions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

3. Security Considerations

This document has no security considerations.

4. IANA Considerations

This document has no IANA actions.

5. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/rfc/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/rfc/rfc8174>.

Acknowledgments

TODO acknowledge.

Author's Address

Rich Salz
Akamai Technologies, Inc.