RFC 3777 Update for Vacancies
draft-ietf-genarea-bcp10upd-01

Abstract

BCP 10 (RFC 3777) specifies IETF processes for selection, confirmation and recall of appointees to IETF positions. It also refers to the mechanism of resignation as part of a sequence that moves a sitting member to a new IETF position. However it does not more generally deal with vacancies created by resignation, death or uncontested, sustained absence from participation. This update to BCP 10 specifies procedures for handling vacancies.

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 http:/⁠/⁠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 May 05, 2013.

Copyright Notice

Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http:/⁠/⁠trustee.ietf.org/⁠license-⁠info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 1.1. Draft changes
• 2. Changes to RFC 3777 (BCP 10)
• 3. Mid-Term Vacancy
• 3.1. Definition
• 3.2. Determination
• 3.3. Confirmation
• 4. Security Considerations
• 5. References - Normative
• Authors' Addresses

1. Introduction

[RFC3777] (BCP 10) specifies IETF processes for selection, confirmation and recall of appointees to IETF positions. It also refers to the mechanism of resignation as part of a sequence that moves a sitting member to a new IETF position. However it does not more generally deal with vacancies created by resignation, death or uncontested, sustained absence from participation. This update to RFC 3777 specifies procedures for handling vacancies.

1.1. Draft changes

NOTE TO RFC EDITOR:

Remove this section prior to publication.

• "For vacancies due to death or resignation..." - slight wording tweak.
• "Extended Last Call" - changed to cite RFC 2026 and match its use of the label.
• "For a contested, sustained absence,..." - reworded

2. Changes to RFC 3777 (BCP 10)

BCP 10 is modified as follows:

• A new section is added, containing the text of the Mid-Term Vacancy [vacancy] section, below.

3. Mid-Term Vacancy

The process of filling a mid-term vacancy is specified in Section 5 of [RFC3777](BCP10).

3.1. Definition

A mid-term vacancy occurs in the IAB, IESG or IAOC when a sitting member of that body ceases to participate in its activities. Vacancy can occur due to death, resignation, or sustained absence.

3.2. Determination

The IETF body of which the sitting member is a part will determine that the sitting member has vacated their position. In the case of vacancy due to uncontested, sustained absence, the body will make multiple different queries to the member, to determine the cause and likely duration of the absence. If the member who is at issue contests the determination that they have vacated the position, the existing Member Recall process, as specified in Section 7 of [RFC3777], is required.

A two-thirds majority vote of the IETF body is needed to determine that a vacancy exists.

3.3. Confirmation

For vacancies due to death or resignation, no further action is required before declaring the seat vacant.

For vacancies due to uncontested, sustained absence, the IETF body making that determination will issue an extended Last-Call Section 9.1, RFC 2026 [RFC2026] to the community. The Last Call will explain the basis for declaring the position vacant and include a summary of efforts to contact the member to resolve the issue.

The results of the Last Call are assessed by the IETF body, with a two-thirds vote of the body.

4. Security Considerations

This document carries no security concerns.

5. References - Normative

Authors' Addresses