Re: Consolidating BCP 10 (Operation of the NomCom)
Spencer Dawkins <spencerdawkins.ietf@gmail.com> Sat, 13 September 2014 01:35 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5669C1A0198 for <ietf@ietfa.amsl.com>; Fri, 12 Sep 2014 18:35:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id npPkkrdGJfKs for <ietf@ietfa.amsl.com>; Fri, 12 Sep 2014 18:35:22 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FEA01A0193 for <ietf@ietf.org>; Fri, 12 Sep 2014 18:35:22 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id m1so1095974oag.24 for <ietf@ietf.org>; Fri, 12 Sep 2014 18:35:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Krdwi490D38tuIibCkwW1eXjMrMYiTvLDE4zJELgGgY=; b=QrawC1YiXiTnakN0kfh/GYJojY3uAPZgVPSkqIYH/CAPMtNOie3l8Zr38Sp1zmMmcY biHgeQhAXiN13unBW0Jxrdh9jbvLrVADwYpym/gB2N0Ac2Lv3B9n2dZSUgEmOsyY7ykz n+GxRXI+t1qOp70Im8cmVYZQrRR2w55lhTk5ZKuNR5rscU6KOuCJqnvPDnjrs2T0ZY2u Msg/FVFbngS0ymAwKbEOvu4UskMhfj37SzHk3IgtMAWqmqkm2FHymTlHghh+AHo/uJhk rdQvwEYKmMTMFOuN8pL1oPnS+2iynuOF0LfvWUUO95NeOke6umnRtLn/tnsR3fa1tJGx D+uQ==
X-Received: by 10.182.44.135 with SMTP id e7mr12360545obm.18.1410572121731; Fri, 12 Sep 2014 18:35:21 -0700 (PDT)
Received: from ?IPv6:2605:6000:9005:3f00:15b9:d874:50aa:6dea? ([2605:6000:9005:3f00:15b9:d874:50aa:6dea]) by mx.google.com with ESMTPSA id ik6sm3695171obb.7.2014.09.12.18.35.19 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Sep 2014 18:35:20 -0700 (PDT)
Message-ID: <54139F56.9050907@gmail.com>
Date: Fri, 12 Sep 2014 20:35:18 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Consolidating BCP 10 (Operation of the NomCom)
References: <CAL0qLwaK1buBO9W+eUY53OxMVAa9aAMHibrTNVqSB5244f8t_Q@mail.gmail.com>
In-Reply-To: <CAL0qLwaK1buBO9W+eUY53OxMVAa9aAMHibrTNVqSB5244f8t_Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mh6HDMrOcHa1F33LjtqLEPobUYg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Sep 2014 01:35:24 -0000
Hi, Murray, On 09/04/2014 01:09 AM, Murray S. Kucherawy wrote: > Colleagues, > > As part of my work with NomCom '14, I'm preparing a revision of > RFC3777 that incorporates all of the updates made to it subsequent to > its publication ten years ago. This would roll all of the documents > making up the NomCom's definition and procedures into one place. > > The draft is available here: > > https://datatracker.ietf.org/doc/draft-kucherawy-rfc3777bis/ > > It is at present nothing more than a republishing of RFC3777 verbatim, > with some slight organization adjustments that come along with > conversion to xml2rfc (RFC3777 was done in nroff), and all of the > changes made by the other documents that currently comprise BCP 10 > have been incorporated. There have been no other substantive content > changes made. > > My plan is to keep it that way for this go-around. Then, if the > community would like to actually crack open the document and revisit > some of the content, that would be a second project (for which I would > probably volunteer to act as editor). > > Comments welcome. Thank you for doing this work. It looks good. I know that wasn't easy because every word matters :-) I have some comments you may wish to consider. -- This isn't text you changed in this revision, but it jumped out at me for the first time. 3.2. Nominating Committee Principal Functions The principal functions of the nominating committee are to review each open IESG, IAB, and IAOC position and to nominate either its ^^ ^^^^^^^^ incumbent or a superior candidate. That text hasn't changed since http://tools.ietf.org/html/rfc2027 in October 1996. I've always tried to use "nominee" to describe Nomcom inputs, and "candidate" to describe Nomcom outputs. That's the way I read the definitions, anyway. The previous section correctly calls what Nomcom is doing "selection of candidates", as in 3.1. Completion Due (deleted down to) The annual process is comprised of three major components as follows: 1. The selection and organization of the nominating committee members. 2. The selection of candidates by the nominating committee. ^^^^^^^^^ ^^ ^^^^^^^^^^ 3. The confirmation of the candidates. I know this is supposed to be as small a revision as possible, but if the two descriptions really do conflict, and you don't want to preserve the conflict, I'd suggest "to select either its incumbent or a superior nominee as the candidate". -- 3.7.1. Positions To Be Reviewed deleted down to The IESG, IAB, and IAOC are responsible for providing summary of the "summaries" ^^^^^^^ expertise desired of the candidates selected for their respective open positions to the Executive Director. The summaries are provided to the nominating committee for its consideration. -- 4.13. Open Positions The Chair (or the IETF Executive Director, if no Chair has been named four weeks after the first IETF meeting of the year) obtains the list of positions to be reviewed and announces it along with a solicitation for names of volunteers from the IETF community willing to serve on the nominating committee. If the IETF Executive Director issues the solicitation for volunteers, the IETF Executive Director must also collect responses to the solicitation and provide the names of volunteers to the incoming nominating committee Chair when the incoming nominating committee Chair is named. > At the Chair's request, the IETF Secretariat may perform other > clerical support tasks, as long as the task being performed does not > require nominating committee Chair judgment, in the nominating > committee Chair's opinion, and as long as the community is > appropriately notified that this request is being made. This request > may come from the incoming nominating committee Chair (if one has > been selected for this nominating committee cycle) or the previous > nominating committee Chair (if the search for an incoming nominating > committee Chair is still underway). I was probably the one who put this paragraph where it is, but on reflection, it really has nothing to do with the rest of the section. Maybe move it to its own section about "Other Duties Performed by the IETF Secretariat"?
- Consolidating BCP 10 (Operation of the NomCom) Murray S. Kucherawy
- Re: Consolidating BCP 10 (Operation of the NomCom) Jari Arkko
- Re: Consolidating BCP 10 (Operation of the NomCom) Murray S. Kucherawy
- Re: Consolidating BCP 10 (Operation of the NomCom) Murray S. Kucherawy
- Re: Consolidating BCP 10 (Operation of the NomCom) Spencer Dawkins
- Re: Consolidating BCP 10 (Operation of the NomCom) Spencer Dawkins
- Re: Consolidating BCP 10 (Operation of the NomCom) Jari Arkko
- Re: Consolidating BCP 10 (Operation of the NomCom) Michael StJohns
- Re: Consolidating BCP 10 (Operation of the NomCom) Brian E Carpenter
- Re: Consolidating BCP 10 (Operation of the NomCom) Joel M. Halpern
- Re: Consolidating BCP 10 (Operation of the NomCom) Michael StJohns
- Re: Consolidating BCP 10 (Operation of the NomCom) Murray S. Kucherawy
- Re: Consolidating BCP 10 (Operation of the NomCom) Murray S. Kucherawy
- Re: Consolidating BCP 10 (Operation of the NomCom) Michael StJohns
- Re: Consolidating BCP 10 (Operation of the NomCom) Dave Crocker
- Re: Consolidating BCP 10 (Operation of the NomCom) Michael Richardson
- Re: Consolidating BCP 10 (Operation of the NomCom) Jari Arkko
- Substantial nomcom procedure updates (Was: Re: Co… Jari Arkko
- Re: Substantial nomcom procedure updates (Was: Re… Brian E Carpenter
- Re: Substantial nomcom procedure updates (Was: Re… Dave Crocker
- Re: Substantial nomcom procedure updates (Was: Re… Mary Barnes
- Re: Substantial nomcom procedure updates (Was: Re… Doug Barton
- Re: Substantial nomcom procedure updates (Was: Re… Brian E Carpenter
- Re: Substantial nomcom procedure updates (Was: Re… Mary Barnes
- Re: Substantial nomcom procedure updates (Was: Re… Michael StJohns
- Re: Substantial nomcom procedure updates (Was: Re… Michael StJohns
- Re: Substantial nomcom procedure updates (Was: Re… Melinda Shore
- Re: Substantial nomcom procedure updates (Was: Re… Olafur Gudmundsson
- Re: Substantial nomcom procedure updates (Was: Re… Stephen Kent
- Re: Substantial nomcom procedure updates (Was: Re… Bert Wijnen (IETF)
- RE: Substantial nomcom procedure updates (Was: Re… Ersue, Mehmet (NSN - DE/Munich)
- Re: Substantial nomcom procedure updates (Was: Re… Allison Mankin
- Re: Substantial nomcom procedure updates (Was: Re… Stewart Bryant
- Re: Substantial nomcom procedure updates (Was: Re… Stewart Bryant
- Re: Substantial nomcom procedure updates (Was: Re… Michael Richardson
- Re: Substantial nomcom procedure updates (Was: Re… Dave Crocker
- Re: Substantial nomcom procedure updates (Was: Re… Michael StJohns
- Re: Substantial nomcom procedure updates (Was: Re… Doug Barton
- Re: Substantial nomcom procedure updates (Was: Re… Mary Barnes
- Re: Substantial nomcom procedure updates (Was: Re… Michael StJohns
- Re: Substantial nomcom procedure updates (Was: Re… Michael StJohns
- Re: Substantial nomcom procedure updates (Was: Re… Doug Barton
- Re: Substantial nomcom procedure updates (Was: Re… Mary Barnes
- Re: Substantial nomcom procedure updates (Was: Re… Doug Barton
- Re: Substantial nomcom procedure updates (Was: Re… Joel M. Halpern
- Re: Substantial nomcom procedure updates (Was: Re… Dave Crocker
- Re: Substantial nomcom procedure updates (Was: Re… Melinda Shore
- Re: Substantial nomcom procedure updates (Was: Re… Mary Barnes
- Re: Substantial nomcom procedure updates (Was: Re… Joel M. Halpern
- Re: Substantial nomcom procedure updates (Was: Re… Nico Williams
- Re: Substantial nomcom procedure updates (Was: Re… Brian E Carpenter
- Re: Substantial nomcom procedure updates (Was: Re… Spencer Dawkins at IETF
- Re: Substantial nomcom procedure updates (Was: Re… Murray S. Kucherawy
- Attracting volunteers for leadership roles (Was: … Jari Arkko
- Re: Substantial nomcom procedure updates (Was: Re… Abdussalam Baryun
- Re: Substantial nomcom procedure updates (Was: Re… Stewart Bryant
- Re: Substantial nomcom procedure updates (Was: Re… Loa Andersson
- Re: Substantial nomcom procedure updates (Was: Re… Michael StJohns
- Re: Substantial nomcom procedure updates (Was: Re… Phillip Hallam-Baker
- Re: Substantial nomcom procedure updates (Was: Re… Yoav Nir
- Re: Substantial nomcom procedure updates (Was: Re… Phillip Hallam-Baker
- Re: Substantial nomcom procedure updates (Was: Re… Abdussalam Baryun