idnits 2.17.00 (12 Aug 2021) /tmp/idnits28043/draft-rsalz-termlimits-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (20 October 2021) is 206 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 TBD R. Salz 3 Internet-Draft Akamai Technologies, Inc. 4 Intended status: Informational 20 October 2021 5 Expires: 23 April 2022 7 Term limits for IETF Leadership Positions 8 draft-rsalz-termlimits-00 10 Abstract 12 This document says that nobody can be picked by NomCom for a position 13 more than two consecutive terms. 15 It obsoletes some other documents, which ones are TBD. 17 Discussion Venues 19 This note is to be removed before publishing as an RFC. 21 Source for this draft and an issue tracker can be found at 22 https://github.com/richsalz/draft-rsalz-termlimits. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at https://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on 23 April 2022. 41 Copyright Notice 43 Copyright (c) 2021 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 48 license-info) in effect on the date of publication of this document. 49 Please review these documents carefully, as they describe your rights 50 and restrictions with respect to this document. Code Components 51 extracted from this document must include Simplified BSD License text 52 as described in Section 4.e of the Trust Legal Provisions and are 53 provided without warranty as described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 2 59 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 60 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 61 5. Normative References . . . . . . . . . . . . . . . . . . . . 2 62 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 65 1. Introduction 67 After a person has served two consecutive terms in any NomCom-chosen 68 position, they are ineligible to directly serve for another term in 69 any NomCom-chosen position; there must be a gap of at least one year. 70 This rule goes into effect starting in March, 2023. 72 2. Conventions and Definitions 74 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 75 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 76 "OPTIONAL" in this document are to be interpreted as described in 77 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 78 capitals, as shown here. 80 3. Security Considerations 82 This document has no security considerations. 84 4. IANA Considerations 86 This document has no IANA actions. 88 5. Normative References 90 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 91 Requirement Levels", BCP 14, RFC 2119, 92 DOI 10.17487/RFC2119, March 1997, 93 . 95 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 96 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 97 May 2017, . 99 Acknowledgments 101 TODO acknowledge. 103 Author's Address 105 Rich Salz 106 Akamai Technologies, Inc. 108 Email: rsalz@akamai.com