BCP 10, RFC 6859 on Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership

rfc-editor@rfc-editor.org Tue, 15 January 2013 01:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8213721F8B9C for <ietf-announce@ietfa.amsl.com>; Mon, 14 Jan 2013 17:36:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.444
X-Spam-Level:
X-Spam-Status: No, score=-102.444 tagged_above=-999 required=5 tests=[AWL=0.156, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jHrv01DdlgjV for <ietf-announce@ietfa.amsl.com>; Mon, 14 Jan 2013 17:36:21 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 09D8521F8473 for <ietf-announce@ietf.org>; Mon, 14 Jan 2013 17:36:21 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8E537B1E00A; Mon, 14 Jan 2013 17:25:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 10, RFC 6859 on Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership
From: rfc-editor@rfc-editor.org
Message-Id: <20130115012538.8E537B1E00A@rfc-editor.org>
Date: Mon, 14 Jan 2013 17:25:38 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 01:36:21 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 10        
        RFC 6859

        Title:      Update to RFC 3777 to 
                    Clarify Nominating Committee Eligibility of IETF 
                    Leadership 
        Author:     B. Leiba
        Status:     Best Current Practice
        Stream:     IETF
        Date:       January 2013
        Mailbox:    barryleiba@computer.org
        Pages:      3
        Characters: 5619
        Updates:    RFC3777
        See Also:   BCP0010

        I-D Tag:    draft-leiba-3777upd-eligibility-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6859.txt

RFC 3777 specifies that "sitting members" of the IAB and IESG 
"may not volunteer to serve on the nominating committee".  Since the time
that document was written, the IETF Administrative Oversight
Committee (IAOC) was formed; that body is not covered by RFC 3777.
There is also ambiguity in RFC 3777 about whether ex officio members
and liaisons are included as "sitting members".  This document
updates RFC 3777 to clarify the rules as they apply to members of the
IAB, the IESG, and the IAOC.  This memo documents an Internet Best 
Current Practice.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC