idnits 2.17.1 draft-ietf-genarea-bcp10upd-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 : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 24, 2012) is 4202 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 3777 (Obsoleted by RFC 7437) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group D. Crocker 3 Internet-Draft Brandenburg InternetWorking 4 Updates: BCP10 (if approved) J. Galvin 5 Intended status: BCP Afilias USA 6 Expires: April 27, 2013 October 24, 2012 8 RFC 3777 Update for Vacancies 9 draft-ietf-genarea-bcp10upd-00 11 Abstract 13 BCP 10 (RFC 3777) specifies IETF processes for selection, 14 confirmation and recall of appointees to IETF positions. It also 15 refers to the mechanism of resignation as part of a sequence that 16 moves a sitting member to a new IETF position. However it does not 17 more generally deal with vacancies created by resignation, death or 18 uncontested, sustained absence from participation. This update to 19 BCP 10 specifies procedures for handling vacancies. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on April 27, 2013. 38 Copyright Notice 40 Copyright (c) 2012 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. Changes to RFC 3777 (BCP 10) . . . . . . . . . . . . . . . . . 3 57 3. Mid-Term Vacancy . . . . . . . . . . . . . . . . . . . . . . . 3 58 3.1. Definition . . . . . . . . . . . . . . . . . . . . . . . . 3 59 3.2. Determination . . . . . . . . . . . . . . . . . . . . . . . 3 60 3.3. Confirmation . . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 62 5. References - Normative . . . . . . . . . . . . . . . . . . . . 4 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 65 1. Introduction 67 [RFC3777] (BCP 10) specifies IETF processes for selection, 68 confirmation and recall of appointees to IETF positions. It also 69 refers to the mechanism of resignation as part of a sequence that 70 moves a sitting member to a new IETF position. However it does not 71 more generally deal with vacancies created by resignation, death or 72 uncontested, sustained absence from participation. This update to 73 RFC 3777 specifies procedures for handling vacancies. 75 2. Changes to RFC 3777 (BCP 10) 77 BCP 10 is modified as follows: 79 o A new section is added, containing the text of the Mid-Term 80 Vacancy (Section 3) section, below. 82 3. Mid-Term Vacancy 84 The process of filling a mid-term vacancy is specified in Section 5 85 of [RFC3777](BCP10). 87 3.1. Definition 89 A mid-term vacancy occurs in the IAB, IESG or IAOC when a sitting 90 member of that body ceases to participate in its activities. Vacancy 91 can occur due to death, resignation, or sustained absence. 93 3.2. Determination 95 The IETF body of which the sitting member is a part will determine 96 that the sitting member has vacated their position. In the case of 97 vacancy due to uncontested, sustained absence, the body will make 98 multiple different queries to the member, to determine the cause and 99 likely duration of the absence. For a contested, sustained absence, 100 the existing Member Recall process, as specified in Section 7 of 101 [RFC3777], is required. 103 A two-thirds majority vote of the IETF body is needed to determine 104 that a vacancy exists. 106 3.3. Confirmation 108 For vacancies due to death or resignation, no further action is 109 required, to declare the seat vacant. 111 For vacancies due to uncontested, sustained absence, the IETF body 112 making that determination will issue an Extended Last Call to the 113 community. The Last Call will explain the basis for declaring the 114 position vacant and include a summary of efforts to contact the 115 member to resolve the issue. 117 The results of the Last Call are assessed by the IETF body, with a 118 two-thirds vote of the body. 120 4. Security Considerations 122 This document carries no security concerns. 124 5. References - Normative 126 [RFC3777] Galvin, J., Ed., "IAB and IESG Selection, Confirmation, 127 and Recall Process: Operation of the Nominating and Recall 128 Committees", rfc 3777, BCP 10, June 3004. 130 Authors' Addresses 132 Dave Crocker 133 Brandenburg InternetWorking 134 675 Spruce Drive 135 Sunnyvale, CA 94086 136 USA 138 Phone: +1.408.246.8253 139 Email: dcrocker@bbiw.net 141 J. Galvin 142 Afilias USA 143 300 Welsh Road, Bldg 3, Ste 105 144 Horsham, PA 19044 145 USA 147 Phone: +1-215-706-5715 148 Email: galvin+ietf@elistx.com