idnits 2.17.1 draft-ietf-genarea-bcp10upd-01.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 25, 2012) is 4200 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 28, 2013 October 25, 2012 8 RFC 3777 Update for Vacancies 9 draft-ietf-genarea-bcp10upd-01 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 28, 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 1.1. Draft changes . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Changes to RFC 3777 (BCP 10) . . . . . . . . . . . . . . . . . 3 58 3. Mid-Term Vacancy . . . . . . . . . . . . . . . . . . . . . . . 3 59 3.1. Definition . . . . . . . . . . . . . . . . . . . . . . . . 3 60 3.2. Determination . . . . . . . . . . . . . . . . . . . . . . . 3 61 3.3. Confirmation . . . . . . . . . . . . . . . . . . . . . . . 4 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 63 5. References - Normative . . . . . . . . . . . . . . . . . . . . 4 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 66 1. Introduction 68 [RFC3777] (BCP 10) specifies IETF processes for selection, 69 confirmation and recall of appointees to IETF positions. It also 70 refers to the mechanism of resignation as part of a sequence that 71 moves a sitting member to a new IETF position. However it does not 72 more generally deal with vacancies created by resignation, death or 73 uncontested, sustained absence from participation. This update to 74 RFC 3777 specifies procedures for handling vacancies. 76 1.1. Draft changes 78 NOTE TO RFC EDITOR: Remove this section prior to publication. 80 o "For vacancies due to death or resignation..." - slight wording 81 tweak. 83 o "Extended Last Call" - changed to cite RFC 2026 and match its use 84 of the label. 86 o "For a contested, sustained absence,..." - reworded 88 2. Changes to RFC 3777 (BCP 10) 90 BCP 10 is modified as follows: 92 o A new section is added, containing the text of the Mid-Term 93 Vacancy (Section 3) section, below. 95 3. Mid-Term Vacancy 97 The process of filling a mid-term vacancy is specified in Section 5 98 of [RFC3777](BCP10). 100 3.1. Definition 102 A mid-term vacancy occurs in the IAB, IESG or IAOC when a sitting 103 member of that body ceases to participate in its activities. Vacancy 104 can occur due to death, resignation, or sustained absence. 106 3.2. Determination 108 The IETF body of which the sitting member is a part will determine 109 that the sitting member has vacated their position. In the case of 110 vacancy due to uncontested, sustained absence, the body will make 111 multiple different queries to the member, to determine the cause and 112 likely duration of the absence. If the member who is at issue 113 contests the determination that they have vacated the position, the 114 existing Member Recall process, as specified in Section 7 of 115 [RFC3777], is required. 117 A two-thirds majority vote of the IETF body is needed to determine 118 that a vacancy exists. 120 3.3. Confirmation 122 For vacancies due to death or resignation, no further action is 123 required before declaring the seat vacant. 125 For vacancies due to uncontested, sustained absence, the IETF body 126 making that determination will issue an extended Last-Call Section 127 9.1, RFC 2026 [RFC2026] to the community. The Last Call will explain 128 the basis for declaring the position vacant and include a summary of 129 efforts to contact the member to resolve the issue. 131 The results of the Last Call are assessed by the IETF body, with a 132 two-thirds vote of the body. 134 4. Security Considerations 136 This document carries no security concerns. 138 5. References - Normative 140 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 141 3", RFC 2026, BCP 9, October 1996. 143 [RFC3777] Galvin, J., Ed., "IAB and IESG Selection, Confirmation, 144 and Recall Process: Operation of the Nominating and Recall 145 Committees", RFC 3777, BCP 10, June 3004. 147 Authors' Addresses 149 Dave Crocker 150 Brandenburg InternetWorking 151 675 Spruce Drive 152 Sunnyvale, CA 94086 153 USA 155 Phone: +1.408.246.8253 156 Email: dcrocker@bbiw.net 158 J. Galvin 159 Afilias USA 160 300 Welsh Road, Bldg 3, Ste 105 161 Horsham, PA 19044 162 USA 164 Phone: +1-215-706-5715 165 Email: galvin+ietf@elistx.com