idnits 2.17.1 draft-bradner-iaoc-terms-04.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 date (September 1, 2015) is 3160 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4071 (Obsoleted by RFC 8711) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Scott Bradner 3 Internet-Draft Harvard University 4 Intended status: BCP 5 Updates: 4071 6 Expires: March 1, 2015 September 1, 2015 8 Updating the Definition of Term for IAOC Members 9 draft-bradner-iaoc-terms-04.txt 11 Abstract 13 The start and end dates specified in BCP 101 for terms of IAOC 14 members has proven to be impractical. This memo updates BCP 101 to 15 establish that the IAOC is directed to establish start and end dates 16 for terms of IAOC members that will be more practical. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on November 22, 2015. 35 Copyright Notice 37 Copyright (c) 2015 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 1. Background 52 BCP 101 says "IAOC terms normally end at the end of the first IETF 53 meeting of a year". ([RFC4071] Section 4.) Having the terms of the 54 IAOC members expire at the end of the first IETF meeting of the year 55 has proved impractical for the IAOC to carry out its business and to 56 elect its Chair during the meeting week. For a number of years, the 57 IAOC has fudged the issue somewhat by defaulting to an informal 58 process of having the transition occur during the administrative 59 plenary (as the IESG does). This informal arrangement violates the 60 letter of BCP 101. But even this arrangement is problematic if the 61 transfer happens after the IAOC's face-to-face meeting that happens 62 during the week. For a number of years, the IAOC's meeting has been 63 on the morning of the administrative plenary so the incoming IAOC 64 members, while present, are not seated even with the informal 65 arrangement. 67 Having the new IAOC members take office after the face-to-face 68 meeting has caused difficulties in the chair selection and voting 69 processes during the IAOC's face-to-face meeting held during the same 70 week. There has been confusion over who should vote in the chair 71 election and on any business actions that require a vote of the 72 Trustees. If the incoming members are not seated then they should not 73 vote, for example, to select a chair for the next year yet they, more 74 than the outgoing members, should have a say in the chair selection. 75 There is also confusion over who is eligible to be elected as chair - 76 if the term of an IAOC member has not yet started could that IAOC 77 member be elected chair (since the chair is selected from among the 78 members). Having the terms expire at the end of the week also risks 79 the IAOC not being able to raise a quorum if outgoing members decide 80 to not come to the meeting. Since the IAOC members are the Trustees 81 of the IETF Trust the same issues arise with the IETF Trust and its 82 ability to carry out its business and elect a Chair during the 83 meeting week 85 An additional issue with BCP 101 is the current definition of the 86 term of the IAOC Chair. BCP 101 says "The term of the IAOC chair 87 shall be one year from the time of selection or the remaining time of 88 his or her tenure on the IAOC, whichever is less". Since the dates 89 for the first IETF meeting of the year vary from year to year the 90 current BCP 101 text could result in there being no IAOC chair in 91 weeks before the a meeting or in overlapping terms for IAOC Chairs. 93 2. BCP 101 Update 95 This memo updates Section 4 of BCP 101 to remove the sentence "IAOC 96 terms normally end at the end of the first IETF meeting of a year" 97 and to add the following requirements: 99 1. that the IAOC and the IETF Trust each hold a regular meeting close 100 to the time of, or during, the first IETF meeting of the year; and 102 2. that the IAOC and the Trust select their chairs as the first order 103 of business in their individual meetings in a manner of their 104 choosing; and 106 3. that the IAOC determine the beginning and end of the normal terms 107 of its members relative to the above mentioned IAOC meeting, such 108 terms must start and end close to the time of this meeting, unless 109 those determinations are made by the appointing bodies, 111 A regular meeting has proper notice, with minutes posted, and may be 112 held as face-to-face, teleconference, or as a combination of the two. 114 3. Security Considerations 116 This memo relates to IETF process, not any particular technology so 117 it does not impact the security of the Internet. 119 4. References 121 4.1. Normative References 123 [RFC4071] Austein, R and B. Wijnen, "Structure of the IETF 124 Administrative Support Activity (IASA)", BCP 101, RFC 4071, April 125 2005. 127 IANA Considerations 129 This memo requires no action by the IANA. [this section should be 130 removed for publication] 132 5. Editor's Addresses 134 Scott Bradner 135 Harvard University 136 8 Story St. 137 Cambridge MA, 02138 138 Phone: +1 617 495 3864 139 EMail: sob@harvard.edu 141 6. changes between versions 142 This section to be removed by the RFC Editor before publication 144 ver 00 -> ver 01 145 add "or teleconference" in 2nd paragraph of section 2 146 clarified last paragraph of section 2 147 fixed typo and punctuation 149 ver 01 -> ver 02 150 replaced section 2 to allow the IAOC to (re)define its procedures 151 when needed 152 removed reference to the Trust Agreement 154 ver 02 -> ver 03 155 reword abstract 156 reformat section 2 158 ver 02 -> ver 03 159 updated 1st paragraph of section 2 to quote the sentence being 160 removed 161 added text to 2.3 to say that the term ends need to be neat the time 162 of the 1st ietf meeting of the year