From ietf-nomcom-errors@lists.elistx.com Mon Mar  3 06:55:12 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HB600F048XL4I@eListX.com> (original mail from nsyracus@cnri.reston.va.us)
 ; Mon, 03 Mar 2003 06:51:21 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HB600F018XJ43@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 03 Mar 2003 06:51:20 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HB600F018XJ41@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 03 Mar 2003 06:51:19 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HB6005CR8XIED@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 03 Mar 2003 06:51:18 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18735; Mon,
 03 Mar 2003 06:48:38 -0500 (EST)
Date: Mon, 03 Mar 2003 06:48:38 -0500
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-nomcom-rfc2727bis-03.txt
Sender: nsyracus@cnri.reston.va.us
To: IETF-Announce: ;
Cc: ietf-nomcom@lists.elistx.com
Reply-to: Internet-Drafts@ietf.org
Message-id: <200303031148.GAA18735@ietf.org>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_8SzLwJOMPC02pGRY6FC49g)"
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


--Boundary_(ID_8SzLwJOMPC02pGRY6FC49g)
Content-type: TEXT/PLAIN

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operation of the IESG/IAB Nominating and Recall Committees Working Group of the IETF.

	Title		: IAB and IESG Selection, Confirmation, and Recall 
                          Process: Operation of the Nominating and Recall 
                          Committees
	Author(s)	: J. Galvin
	Filename	: draft-ietf-nomcom-rfc2727bis-03.txt
	Pages		: 40
	Date		: 2003-2-28
	
The process by which the members of the IAB and IESG are selected,
confirmed, and recalled is specified.  This document is a
self-consistent, organized compilation of the process as it was known
at the time of publication.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nomcom-rfc2727bis-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-nomcom-rfc2727bis-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nomcom-rfc2727bis-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Boundary_(ID_8SzLwJOMPC02pGRY6FC49g)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_IPUjwEGVtd/Xt2G0lcrJ/A)"


--Boundary_(ID_IPUjwEGVtd/Xt2G0lcrJ/A)
Content-type: Message/External-body; server="mailserv@ietf.org";
 access-type=mail-server

Content-Type: text/plain
Content-ID:	<2003-2-28125539.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-nomcom-rfc2727bis-03.txt

--Boundary_(ID_IPUjwEGVtd/Xt2G0lcrJ/A)
Content-type: Message/External-body; directory=internet-drafts;
 access-type=anon-ftp; site=ftp.ietf.org;
 name=draft-ietf-nomcom-rfc2727bis-03.txt

Content-Type: text/plain
Content-ID:	<2003-2-28125539.I-D@ietf.org>

--Boundary_(ID_IPUjwEGVtd/Xt2G0lcrJ/A)--

--Boundary_(ID_8SzLwJOMPC02pGRY6FC49g)--

From ietf-nomcom-errors@lists.elistx.com Mon Mar  3 10:35:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HB600204J0A1H@eListX.com> (original mail from brian@hursley.ibm.com)
 ; Mon, 03 Mar 2003 10:28:58 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HB600201J0A1E@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 03 Mar 2003 10:28:58 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HB600201J091D@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 03 Mar 2003 10:28:57 -0500 (EST)
Received: from d12lmsgate.de.ibm.com (d12lmsgate.de.ibm.com [194.196.100.234])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HB600JO2J07GY@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 03 Mar 2003 10:28:57 -0500 (EST)
Received: from d12relay01.de.ibm.com (d12relay01.de.ibm.com [9.165.215.22])
	by d12lmsgate.de.ibm.com (8.12.3/8.12.3) with ESMTP id h23FS9Xu036014; Mon,
 03 Mar 2003 16:28:13 +0100
Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140])
	by d12relay01.de.ibm.com (8.12.3/NCO/VER6.5) with SMTP id h23FS2FF049738; Mon,
 03 Mar 2003 16:28:03 +0100
Received: from dhcp23-27.zurich.ibm.com by ochsehorn.zurich.ibm.com
 (AIX 4.3/UCB 5.64/4.03)          id AA28546 from <brian@hursley.ibm.com>; Mon,
 03 Mar 2003 16:27:59 +0100
Date: Mon, 03 Mar 2003 16:27:03 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Subject: Re: Question on draft-ietf-nomcom-rfc2727bis-03.txt
To: EKR <ekr@rtfm.com>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <3E637447.C10CB0E6@hursley.ibm.com>
Organization: IBM
MIME-version: 1.0
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en,fr,de
References: <3E5A9E1D.5050801@acm.org> <3E5DECC8.B9B7EE3@hursley.ibm.com>
 <kj1y1tsl0l.fsf@romeo.rtfm.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Eric Rescorla wrote:
> 
> Brian E Carpenter <brian@hursley.ibm.com> writes:
> > See rule 11 in section 5:
> >
> > >         Nominating committee members are not eligible to be considered
> > >         for filling any open position.  They become ineligible as soon
> > >         as the term of the nominating committee on which they serve
> > >         officially begins.  They remain ineligible for the duration of
> > >         that nominating committee's term.
> >
> > Nomcom N overlaps by about 3 months with Nomcom N+1. Due to this overlap,
> > is a member of Nomcom N ineligible for nomination by Nomcom N+1? As I read
> > the timeline, there are probably a few hours or days after the Third IETF
> > when a member of Nomcom N would become eligible, i.e. after Nomcom N is
> > dissolved but before nominations close. Is this correct? Whatever the
> > answer, I think the document should state it.
> >
> > To put it another way, is it our intention that Nomcom members are
> > immunized for one year or two years?
> Unless we're changing existing practice, it must be one year.
> 
> Otherwise, the liasons could not be nominated the following
> term, making nomcom liason a ticket out of the IESG/IAB.
> 
> Or have I missed something?
> -Ekr

No, we all seem to agree on that, and it just needs to be clear in the
text.

    Brian

From ietf-nomcom-errors@lists.elistx.com Tue Mar 11 13:45:11 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBL00H04LAJL1@eListX.com> (original mail from avri@acm.org); Tue,
 11 Mar 2003 13:42:19 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBL00H01LAIKZ@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Tue,
 11 Mar 2003 13:42:18 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBL00H01LAIKY@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Tue, 11 Mar 2003 13:42:18 -0500 (EST)
Received: from lakecmmtao02.coxmail.com
 (lakecmmtao02.coxmail.com [68.99.120.61]) by eListX.com (PMDF V6.0-025 #44856)
 with ESMTP id <0HBL00H0XLAHH6@eListX.com> for ietf-nomcom@lists.elistx.com;
 Tue, 11 Mar 2003 13:42:18 -0500 (EST)
Received: from acm.org ([68.15.42.104]) by lakecmmtao02.coxmail.com
 (InterMail vM.5.01.04.05 201-253-122-122-105-20011231)
 with ESMTP          id <20030311184132.OGFO11973.lakecmmtao02.coxmail.com@acm.org>          for
 <ietf-nomcom@lists.elistx.com>; Tue, 11 Mar 2003 13:41:32 -0500
Date: Tue, 11 Mar 2003 13:41:17 -0500
From: Avri Doria <avri@acm.org>
Subject: Staus of the Nomcom WG
To: ietf-nomcom@lists.elistx.com
Message-id: <3E6E2DCD.7040300@acm.org>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2)
 Gecko/20021120 Netscape/7.01
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Hi,

Since we are not holding a meeting this time, it seemed a
good idea to send the group my perception of our status.

I think we are close to the time for a WG last call.  I
certainly want to make sure we are totally finished before
a new Nomcom is chosen.

Recently draft-ietf-nomcom-rfc2727bis-03.txt was put out.
In addition to several minor errors which are currently
being corrected, there were two larger issues:

1. Whether the prohibition for voting members of
NomCom from being selected to serve on the IAB/IESG was now
lengthened to 2 years because of the provision that requires a
NomCom to sit longer then 12 months if there is a need to
fill a late season interim vacancy.
The consensus, as I understood it, is that this should
not be the case, and that text should be added to clarify
that the prohibition was only for selections made by the
NomCom in which a person is a voting member; i.e. 1 year.

2. Whether the occasional practice of giving incumbents
performance  feedback that is obtained incidentally
during interviews, should be formalized in any way.

A inconclusive discussion on this came up in the design
team.  There is nothing in 2727 which either permits this
or prohibits this as long as confidentiality is maintained.

Tradition and 2727 has left such decisions to the NomCom
itself.  This may mean that such feedback is either not
passed on or has marginal value when it is.  It is
also possible that in some cases, the nature of the feedback
may betray the source and this threatens confidentiality. Also
if such a practice where formalized it might change the amount
and quality of feedback; whether for better or worse.

I see several  paths we can follow in dealing with this issue:

A- Decide that the status quo achieves the right balance and
leave things as they are.  This is the default condition if
there is not strong consensus for change.

B- Decide that this feedback is important but in keeping with
the tradition of leaving as much up to the individual NomCom as
possible add a statement on this to the oral traditions.

C- Decide that this feedback is critical and deserves a rule
requiring it.

D- Decide that this practice is a risk to confidentiality
or negative in some other way and that it should be discouraged
in the oral traditions.

E- Decide that this practice is a threat to confidentiality
or negative in some other way and that it should be forbidden
by the rules.


I am asking the participants in this group to send in their
comments on this issue.  I request that you pick one of the
options and give reasons.  Of course, if there are other options
you can speak of them as well.

Supporters of options B-E are encouraged to suggest wording.

Finally if there are other open issues in -03 that have not been
discussed or other open issues I have lost track of,
please speak up.

I strongly encourage folks to read the current draft and send
in your comments.  As I said, I hope to be able to start the WG
last call right after -04 is released shortly after IETF56.

Thanks,
a.




From ietf-nomcom-errors@lists.elistx.com Tue Mar 11 17:15:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBL00504UWCMM@eListX.com> (original mail from leslie@thinkingcat.com)
 ; Tue, 11 Mar 2003 17:09:48 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBL00501UWCMI@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Tue,
 11 Mar 2003 17:09:48 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBL00501UWBMG@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Tue, 11 Mar 2003 17:09:47 -0500 (EST)
Received: from cliffie.verisignlabs.com
 (thing.verisignlabs.com [65.201.175.62]) by eListX.com (PMDF V6.0-025 #44856)
 with ESMTP id <0HBL000KIUWBFW@eListX.com> for ietf-nomcom@lists.elistx.com;
 Tue, 11 Mar 2003 17:09:47 -0500 (EST)
Received: from thinkingcat.com (h87.s239.netsol.com [216.168.239.87])
 (AUTH: PLAIN leslie, TLS: TLSv1/SSLv3,128bits,RC4-MD5)
 by cliffie.verisignlabs.com with esmtp; Tue, 11 Mar 2003 17:09:02 -0500
Date: Tue, 11 Mar 2003 17:09:13 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
Subject: IAB request for clarifications in RFC2727bis
To: ietf-nomcom@lists.elistx.com
Cc: avri@acm.org
Message-id: <3E6E5E89.7090205@thinkingcat.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

NOMCOM WG,

Every year, in the course of performing its role of
confirming the IESG slate, the IAB reviews and applies
the directives for that role as spelled out in RFC2727.
Since that document is under revision, the IAB this year
compiled a list of knotty questions it and previous
IABs have contemplated in applying the rules to fulfill the 
community's intent.  We think it would be helpful for future 
IABs if the revised document could address these issues.

There are 2 general areas we feel are in need of clarification.

1/ An overall clarification is needed in terms of how to handle the
mid-term transition of a member from one position to another.  That is,
if a member of one body, whose term there is not finishing, accepts
nomination to an opening in the other body (or a different
position in the IESG) as part of the annual cycle, what is the 
expected practice:

   Is this an automatic resignation from the first position?

   When is that resignation effective -- at the end of the
   IETF meeting when they officially begin their new role?

   Since it is particularly difficult to gauge precise
   numbers of months left in the term at that point, is
   this then a mid-term vacancy to be filled for the rest
   of the original member's term, or for the rest of the
   original member's term plus 2 years?

   How should the nomcom fill the mid-term vacancy:  as part
   of its slate for the affected body, since it created the
   vacancy, or by running a separate consideration process
   once the affected body is made aware of the vacancy
   (by seeing the confirmed slate).

   Is it the intent of the Nomcom WG that someone could serve
   simultaneously on the IESG and as a sitting member of the IAB
   (i.e. not talking about the IETF Chair special case) ?

   This is ambiguous in the current procedures, so should be
   explicitly clarified one way or the other in the next revision.

2/ Is the IAB's role to exercise good judgement about the
qualifications of each nominee or is the IAB's role limited to
process review only?

   If it is the IAB's role to exercise good judgement, what are the
   documented criteria for an IESG candidate ?

   If it is not the IAB's role to exercise good judgement, how does
   the IAB get sufficient visibility into the Nomcom process to
   exercise a purely process-oversight role without breaching the
   confidentiality and without intruding on Nomcom's deliberations ?



Leslie,
for the IAB.

-- 

-------------------------------------------------------------------
"Reality:
     Yours to discover."
                                -- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------



From ietf-nomcom-errors@lists.elistx.com Wed Mar 12 05:25:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBM00804SXC9A@eListX.com> (original mail from brian@hursley.ibm.com)
 ; Wed, 12 Mar 2003 05:24:48 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBM00801SXB98@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Wed,
 12 Mar 2003 05:24:47 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBM00801SXB97@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Wed, 12 Mar 2003 05:24:47 -0500 (EST)
Received: from d12lmsgate-3.de.ibm.com
 (d12lmsgate-3.de.ibm.com [194.196.100.236])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HBM000NOSXA9N@eListX.com>
 for ietf-nomcom@lists.elistx.com; Wed, 12 Mar 2003 05:24:47 -0500 (EST)
Received: from d12relay01.de.ibm.com (d12relay01.de.ibm.com [9.165.215.22])
	by d12lmsgate-3.de.ibm.com (8.12.8/8.12.8) with ESMTP id h2CANoEO102364; Wed,
 12 Mar 2003 11:23:54 +0100
Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140])
	by d12relay01.de.ibm.com (8.12.8/NCO/VER6.5) with SMTP id h2CANl9l109938; Wed,
 12 Mar 2003 11:23:48 +0100
Received: from dhcp23-54.zurich.ibm.com by ochsehorn.zurich.ibm.com
 (AIX 4.3/UCB 5.64/4.03)          id AA37682 from <brian@hursley.ibm.com>; Wed,
 12 Mar 2003 11:23:46 +0100
Date: Wed, 12 Mar 2003 11:22:46 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Subject: Re: Staus of the Nomcom WG
To: Avri Doria <avri@acm.org>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <3E6F0A76.8FFC0339@hursley.ibm.com>
Organization: IBM
MIME-version: 1.0
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en,fr,de
References: <3E6E2DCD.7040300@acm.org>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

in line...

Avri Doria wrote:
> 
> Hi,
> 
> Since we are not holding a meeting this time, it seemed a
> good idea to send the group my perception of our status.
> 
> I think we are close to the time for a WG last call.  I
> certainly want to make sure we are totally finished before
> a new Nomcom is chosen.
> 
> Recently draft-ietf-nomcom-rfc2727bis-03.txt was put out.
> In addition to several minor errors which are currently
> being corrected, there were two larger issues:
> 
> 1. Whether the prohibition for voting members of
> NomCom from being selected to serve on the IAB/IESG was now
> lengthened to 2 years because of the provision that requires a
> NomCom to sit longer then 12 months if there is a need to
> fill a late season interim vacancy.
> The consensus, as I understood it, is that this should
> not be the case, and that text should be added to clarify
> that the prohibition was only for selections made by the
> NomCom in which a person is a voting member; i.e. 1 year.

I think that's right.

> 
> 2. Whether the occasional practice of giving incumbents
> performance  feedback that is obtained incidentally
> during interviews, should be formalized in any way.
> 
> A inconclusive discussion on this came up in the design
> team.  There is nothing in 2727 which either permits this
> or prohibits this as long as confidentiality is maintained.
> 
> Tradition and 2727 has left such decisions to the NomCom
> itself.  This may mean that such feedback is either not
> passed on or has marginal value when it is.  It is
> also possible that in some cases, the nature of the feedback
> may betray the source and this threatens confidentiality. Also
> if such a practice where formalized it might change the amount
> and quality of feedback; whether for better or worse.
> 
> I see several  paths we can follow in dealing with this issue:
> 
> A- Decide that the status quo achieves the right balance and
> leave things as they are.  This is the default condition if
> there is not strong consensus for change.

Would be acceptable.

> 
> B- Decide that this feedback is important but in keeping with
> the tradition of leaving as much up to the individual NomCom as
> possible add a statement on this to the oral traditions.

I think this is slightly better - make it plain that the NomCom
is entitled to give such feedback, but not obliged.

> C- Decide that this feedback is critical and deserves a rule
> requiring it.

No. We are not running a personnel system here.

> 
> D- Decide that this practice is a risk to confidentiality
> or negative in some other way and that it should be discouraged
> in the oral traditions.

No. There is no special threat to confidentiality, and most 
people welcome feedback.

> 
> E- Decide that this practice is a threat to confidentiality
> or negative in some other way and that it should be forbidden
> by the rules.

No (same reasons).
   
   Brian

From ietf-nomcom-errors@lists.elistx.com Wed Mar 12 11:55:06 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBN00N04AWL28@eListX.com> (original mail from mallman@guns.lerc.nasa.gov)
 ; Wed, 12 Mar 2003 11:53:09 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBN00N01AWL26@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Wed,
 12 Mar 2003 11:53:09 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBN00N01AWK25@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Wed, 12 Mar 2003 11:53:08 -0500 (EST)
Received: from seraph2.grc.nasa.gov (seraph2.grc.nasa.gov [128.156.10.11])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HBN00L7GAWKT6@eListX.com>
 for ietf-nomcom@lists.elistx.com; Wed, 12 Mar 2003 11:53:08 -0500 (EST)
Received: from lombok-fi.lerc.nasa.gov
 (lombok-fi.lerc.nasa.gov [139.88.112.33])	by seraph2.grc.nasa.gov (Postfix)
 with ESMTP id 24F1E68A04	for <ietf-nomcom@lists.elistx.com>; Wed,
 12 Mar 2003 11:52:23 -0500 (EST)
Received: from guns.lerc.nasa.gov (guns.lerc.nasa.gov [139.88.87.35])
	by lombok-fi.lerc.nasa.gov (NASA GRC 8.12.8/8.12.3)
 with ESMTP id h2CGqM7h013909; Wed, 12 Mar 2003 11:52:22 -0500 (EST)
Received: from guns.lerc.nasa.gov (localhost.lerc.nasa.gov [127.0.0.1])
 by guns.lerc.nasa.gov with ESMTP (NASA LeRC 8.7.4.1/2.01-local)
 id LAA19206; Wed, 12 Mar 2003 11:52:22 -0500 (EST)
Date: Wed, 12 Mar 2003 11:52:22 -0500
From: Mark Allman <mallman@grc.nasa.gov>
Subject: Re: Staus of the Nomcom WG
In-reply-to: <3E6E2DCD.7040300@acm.org>
Sender: mallman@guns.lerc.nasa.gov
To: Avri Doria <avri@acm.org>, brian@hursley.ibm.com
Cc: ietf-nomcom@lists.elistx.com
Reply-to: mallman@grc.nasa.gov
Message-id: <200303121652.LAA19206@guns.lerc.nasa.gov>
Organization: BBN Technologies/NASA GRC
Content-type: TEXT/PLAIN
Song-of-the-Day: Nothingman
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


> > C- Decide that this feedback is critical and deserves a rule
> > requiring it.
> 
> No. We are not running a personnel system here.

Actually, we sort of are.

I'd tweak the above option a bit to not require it, but require it
if an incumbant who is re-upping requests it.  With all the
grumbling that is going on about the IESG it seems short-sighted to
just toss the collected information.

Having said that I'd tightly scope this so that the nomcom is only
responsible for producing one email message per incumbant that
sketches the feedback it receives (in an anonymous way).  That is, I
don't want to see this be a conversation or formal review.  Rather,
it should be fairly lightweight on nomcom and provide a sense of the
input that nomcom has gathered to help the incumbant understand any
performance problems percieved by the community.

(Of course, if a particular nomcom feels strongly that they don't
really want to give this feedback then they can always game things
by giving no-op sorts of review information back.)

allman


--
Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/

From ietf-nomcom-errors@lists.elistx.com Wed Mar 12 13:05:02 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBN00304DZIS2@eListX.com> (original mail from PRoberts@MEGISTO.com); Wed,
 12 Mar 2003 12:59:42 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBN00301DZHRU@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Wed,
 12 Mar 2003 12:59:41 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBN00301DZHRQ@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Wed, 12 Mar 2003 12:59:41 -0500 (EST)
Received: from megisto-sql1.megisto.com ([63.113.114.132])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HBN000KJDZDBA@eListX.com>
 for ietf-nomcom@lists.elistx.com; Wed, 12 Mar 2003 12:59:40 -0500 (EST)
Received: by megisto-sql1 with Internet Mail Service (5.5.2653.19)
	id <FCK404FA>; Wed, 12 Mar 2003 12:53:33 -0500
Content-return: allowed
Date: Wed, 12 Mar 2003 12:53:33 -0500
From: Phil Roberts <PRoberts@MEGISTO.com>
Subject: RE: IAB request for clarifications in RFC2727bis
To: 'Leslie Daigle' <leslie@thinkingcat.com>, ietf-nomcom@lists.elistx.com
Cc: avri@acm.org
Message-id: <C3F7A1AD0781F84784B5528466CA09DD7DD4E8@megisto-sql1>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: text/plain
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Presumably question #2 would have a variant for the ISOC
as well?


> -----Original Message-----
> From: Leslie Daigle [mailto:leslie@thinkingcat.com] 
> Sent: Tuesday, March 11, 2003 5:09 PM
> To: ietf-nomcom@lists.elistx.com
> Cc: avri@acm.org
> Subject: IAB request for clarifications in RFC2727bis
> 
> 
> NOMCOM WG,
> 
> Every year, in the course of performing its role of
> confirming the IESG slate, the IAB reviews and applies
> the directives for that role as spelled out in RFC2727.
> Since that document is under revision, the IAB this year 
> compiled a list of knotty questions it and previous IABs have 
> contemplated in applying the rules to fulfill the 
> community's intent.  We think it would be helpful for future 
> IABs if the revised document could address these issues.
> 
> There are 2 general areas we feel are in need of clarification.
> 
> 1/ An overall clarification is needed in terms of how to 
> handle the mid-term transition of a member from one position 
> to another.  That is, if a member of one body, whose term 
> there is not finishing, accepts nomination to an opening in 
> the other body (or a different position in the IESG) as part 
> of the annual cycle, what is the 
> expected practice:
> 
>    Is this an automatic resignation from the first position?
> 
>    When is that resignation effective -- at the end of the
>    IETF meeting when they officially begin their new role?
> 
>    Since it is particularly difficult to gauge precise
>    numbers of months left in the term at that point, is
>    this then a mid-term vacancy to be filled for the rest
>    of the original member's term, or for the rest of the
>    original member's term plus 2 years?
> 
>    How should the nomcom fill the mid-term vacancy:  as part
>    of its slate for the affected body, since it created the
>    vacancy, or by running a separate consideration process
>    once the affected body is made aware of the vacancy
>    (by seeing the confirmed slate).
> 
>    Is it the intent of the Nomcom WG that someone could serve
>    simultaneously on the IESG and as a sitting member of the IAB
>    (i.e. not talking about the IETF Chair special case) ?
> 
>    This is ambiguous in the current procedures, so should be
>    explicitly clarified one way or the other in the next revision.
> 
> 2/ Is the IAB's role to exercise good judgement about the 
> qualifications of each nominee or is the IAB's role limited 
> to process review only?
> 
>    If it is the IAB's role to exercise good judgement, what are the
>    documented criteria for an IESG candidate ?
> 
>    If it is not the IAB's role to exercise good judgement, how does
>    the IAB get sufficient visibility into the Nomcom process to
>    exercise a purely process-oversight role without breaching the
>    confidentiality and without intruding on Nomcom's deliberations ?
> 
> 
> 
> Leslie,
> for the IAB.
> 
> -- 
> 
> -------------------------------------------------------------------
> "Reality:
>      Yours to discover."
>                                 -- ThinkingCat
> Leslie Daigle
> leslie@thinkingcat.com
> -------------------------------------------------------------------
> 
> 
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.elistx.com/subscribe>
> 

From ietf-nomcom-errors@lists.elistx.com Wed Mar 12 14:25:14 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBN00C04HS95Z@eListX.com> (original mail from dhc@dcrocker.net); Wed,
 12 Mar 2003 14:21:46 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBN00C01HS95U@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Wed,
 12 Mar 2003 14:21:45 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBN00C01HS85S@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Wed, 12 Mar 2003 14:21:44 -0500 (EST)
Received: from joy.songbird.com (songbird.com [208.184.79.7])
 by eListX.com (PMDF V6.0-025 #44856)
 with ESMTP id <0HBN009CCHS76X@eListX.com>; Wed,
 12 Mar 2003 14:21:44 -0500 (EST)
Received: from BBFUJIP
 (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h2CJKfQ02773; Wed,
 12 Mar 2003 11:20:41 -0800
Date: Wed, 12 Mar 2003 13:21:56 -0600
From: Dave Crocker <dhc@dcrocker.net>
Subject: candidate evaluation vs. nomcom process evaluation
In-reply-to: <3E6E5E89.7090205@thinkingcat.com>
To: Leslie Daigle <leslie@thinkingcat.com>
Cc: ietf-nomcom@lists.elistx.com, avri@acm.org
Message-id: <801873463.20030312132156@brandenburg.com>
Organization: Brandenburg InternetWorking
MIME-version: 1.0
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Priority: 3 (Normal)
References: <3E6E5E89.7090205@thinkingcat.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Leslie,

Tuesday, March 11, 2003, 4:09:13 PM, you wrote:
LD> 2/ Is the IAB's role to exercise good judgement about the
LD> qualifications of each nominee or is the IAB's role limited to
LD> process review only?

LD>    If it is the IAB's role to exercise good judgement, what are the
LD>    documented criteria for an IESG candidate ?

LD>    If it is not the IAB's role to exercise good judgement, how does
LD>    the IAB get sufficient visibility into the Nomcom process to
LD>    exercise a purely process-oversight role without breaching the
LD>    confidentiality and without intruding on Nomcom's deliberations ?


Many thanks to the IAB for putting this issue forward.  It is a very
difficult one and it seems to have been a factor in the nomcom process
from the start.

The IAB is a collection of bright, motivated, experienced people.  So
how could it be at all reasonable to restrict their review to matters
only of process?  After all, they often know candidates, and very
well.

The difficulty is in the length and complexity of the nomcom committee
work.  Nomcoms put in a great deal of time, talk to many people, and
consider choices and tradeoffs at great length.  Hence, the reasons
for a particular slate of candidates can be difficult, subtle and
fragile.

An IAB review occurs after all of that extended Nomcom work. It cannot
replicate it, both due to calendar limitations and due to resource
limitations.

But we need to remember that the IAB really DOES have quite a lot of
knowledge about the IETF and its major participants.

Let me suggest, therefore, that the way to use that expertise, without
having the IAB try to second-guess (or replicate) the Nomcom's own
work, is to have the IAB treat "process" evaluation as more than a
matter of form.  It should treat it as an evaluation of the quality of
thinking done by the nomcom.  That is, it evaluates the nomcom, not
the nomcom's choices.  It uses the choices as a way of guiding the
focus of the review.

When a nomcom makes a recommendation that is, shall we say,
"surprising" the IAB should push back, requiring that the Nomcom
explain (and defend) that choice very carefully.

This has occurred for the two Nomcom's I've been on and I am quite
certain that the knowledge of having to pass through a review of that
type helped the Nomcom to be more deliberate in its considerations.
(One time, we essentially had to re-construct and re-consider our
entire basis for a choice.  This can be de-stablilizing, to the
group's effort, but I believe it still produces a better result.)

My own sense of difficulty in the two IAB review's of nomcom
recommendation was with the manner in which the IAB and Nomcom
interacted. It was extremely formal and slow, and only went through
liaisons. Hence, it did not permit a real dialogue and, if anything,
tended to produce defensiveness in the Nomcom. (To be clear: I believe
the defensiveness comes from the design of the interaction, rather
than from the IAB's pushback.)

So I suggest that IAB review of IESG choices, and ISOC review of IAB
choices, include a conference call with a collegial discussion.

That is, it should assume that everyone is working in good faith and
has worked hard, but that a surprising choice obligates everyone to
put in extra effort, to understand the basis for that choice.

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>


From ietf-nomcom-errors@lists.elistx.com Wed Mar 12 19:15:07 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBN00204UZOF8@eListX.com> (original mail from gih@telstra.net); Wed,
 12 Mar 2003 19:07:00 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBN00201UZNF6@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Wed,
 12 Mar 2003 19:07:00 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBN00201UZNF5@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Wed, 12 Mar 2003 19:06:59 -0500 (EST)
Received: from kahuna.telstra.net (kahuna.telstra.net [203.50.0.6])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HBN00MB7UZLJP@eListX.com>
 for ietf-nomcom@lists.elistx.com; Wed, 12 Mar 2003 19:06:59 -0500 (EST)
Received: from gih505.telstra.net (rsdhcp13.telstra.net [203.50.0.207])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id h2D05wMK046996; Thu,
 13 Mar 2003 11:06:06 +1100 (EST envelope-from gih@telstra.net)
Date: Thu, 13 Mar 2003 11:05:51 +1100
From: Geoff Huston <gih@telstra.net>
Subject: RE: IAB request for clarifications in RFC2727bis
In-reply-to: <C3F7A1AD0781F84784B5528466CA09DD7DD4E8@megisto-sql1>
X-Sender: gih@kahuna.telstra.net
To: Phil Roberts <PRoberts@MEGISTO.com>,
 'Leslie Daigle' <leslie@thinkingcat.com>, ietf-nomcom@lists.elistx.com
Cc: avri@acm.org
Message-id: <5.1.0.14.2.20030313105933.01bf3fe0@kahuna.telstra.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: text/plain; format=flowed; charset=us-ascii
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Maybe Fred  Baker and Brian Carpenter, as the two most immediate
past chairs of the ISOC BoT, should be asked this question

My own contribution on earlier experiences as an ISOC Trustee was
that the Board did not feel that it could make substantive comment
on the process used by the Nomcom, nor was it able to provide
and alternate view on the qualifications of the individuals named in
the slate, so the confirmation process was one of being assured by
the Nomcom Chair that the Nomcom had acted responsibly and
properly and that the slate was a considered slate that reflected
their impressions of the needs and will of the IETF community.

regards,

     Geoff Huston


At 12:53 PM 3/12/2003 -0500, Phil Roberts wrote:
>Presumably question #2 would have a variant for the ISOC
>as well?
>
>
> > -----Original Message-----
> > From: Leslie Daigle [mailto:leslie@thinkingcat.com]
> > Sent: Tuesday, March 11, 2003 5:09 PM
> > To: ietf-nomcom@lists.elistx.com
> > Cc: avri@acm.org
> > Subject: IAB request for clarifications in RFC2727bis
> >
> >
> > NOMCOM WG,
> >
> > Every year, in the course of performing its role of
> > confirming the IESG slate, the IAB reviews and applies
> > the directives for that role as spelled out in RFC2727.
> > Since that document is under revision, the IAB this year
> > compiled a list of knotty questions it and previous IABs have
> > contemplated in applying the rules to fulfill the
> > community's intent.  We think it would be helpful for future
> > IABs if the revised document could address these issues.
> >
> > There are 2 general areas we feel are in need of clarification.
> >
> > 1/ An overall clarification is needed in terms of how to
> > handle the mid-term transition of a member from one position
> > to another.  That is, if a member of one body, whose term
> > there is not finishing, accepts nomination to an opening in
> > the other body (or a different position in the IESG) as part
> > of the annual cycle, what is the
> > expected practice:
> >
> >    Is this an automatic resignation from the first position?
> >
> >    When is that resignation effective -- at the end of the
> >    IETF meeting when they officially begin their new role?
> >
> >    Since it is particularly difficult to gauge precise
> >    numbers of months left in the term at that point, is
> >    this then a mid-term vacancy to be filled for the rest
> >    of the original member's term, or for the rest of the
> >    original member's term plus 2 years?
> >
> >    How should the nomcom fill the mid-term vacancy:  as part
> >    of its slate for the affected body, since it created the
> >    vacancy, or by running a separate consideration process
> >    once the affected body is made aware of the vacancy
> >    (by seeing the confirmed slate).
> >
> >    Is it the intent of the Nomcom WG that someone could serve
> >    simultaneously on the IESG and as a sitting member of the IAB
> >    (i.e. not talking about the IETF Chair special case) ?
> >
> >    This is ambiguous in the current procedures, so should be
> >    explicitly clarified one way or the other in the next revision.
> >
> > 2/ Is the IAB's role to exercise good judgement about the
> > qualifications of each nominee or is the IAB's role limited
> > to process review only?
> >
> >    If it is the IAB's role to exercise good judgement, what are the
> >    documented criteria for an IESG candidate ?
> >
> >    If it is not the IAB's role to exercise good judgement, how does
> >    the IAB get sufficient visibility into the Nomcom process to
> >    exercise a purely process-oversight role without breaching the
> >    confidentiality and without intruding on Nomcom's deliberations ?
> >
> >
> >
> > Leslie,
> > for the IAB.
> >
> > --
> >
> > -------------------------------------------------------------------
> > "Reality:
> >      Yours to discover."
> >                                 -- ThinkingCat
> > Leslie Daigle
> > leslie@thinkingcat.com
> > -------------------------------------------------------------------
> >
> >
> >
> > ----------------------------------------------------------------
> > To subscribe or unsubscribe from this elist use the subscription
> > manager: <http://lists.elistx.com/subscribe>
> >
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.elistx.com/subscribe>




From ietf-nomcom-errors@lists.elistx.com Thu Mar 13 10:05:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBP00C0407E6A@eListX.com> (original mail from dhc@dcrocker.net); Thu,
 13 Mar 2003 09:57:14 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBP00C0107D60@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 13 Mar 2003 09:57:13 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBP00C0107C5Y@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 13 Mar 2003 09:57:12 -0500 (EST)
Received: from joy.songbird.com (songbird.com [208.184.79.7])
 by eListX.com (PMDF V6.0-025 #44856)
 with ESMTP id <0HBP00B6P07B3V@eListX.com>; Thu,
 13 Mar 2003 09:57:12 -0500 (EST)
Received: from 9-pool2.ras10.vaash.alerondial.net
 (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h2DEu1Q11814; Thu,
 13 Mar 2003 06:56:01 -0800
Date: Thu, 13 Mar 2003 09:57:11 -0500
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: IAB request for clarifications in RFC2727bis
In-reply-to: <5.1.0.14.2.20030313105933.01bf3fe0@kahuna.telstra.net>
To: Geoff Huston <gih@telstra.net>
Cc: Phil Roberts <PRoberts@MEGISTO.com>,
 'Leslie Daigle' <leslie@thinkingcat.com>, ietf-nomcom@lists.elistx.com,
 avri@acm.org
Message-id: <1739077783.20030313095711@brandenburg.com>
Organization: Brandenburg InternetWorking
MIME-version: 1.0
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Priority: 3 (Normal)
References: <5.1.0.14.2.20030313105933.01bf3fe0@kahuna.telstra.net>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Geoff,

GH> that the Board did not feel that it could make substantive comment
GH> on the process used by the Nomcom, nor was it able to provide
GH> and alternate view on the qualifications of the individuals named in

 Did those discussions, or your own thoughts, produce any suggestions
 that might enable the ISOC review to be more substantial (and
 therefore more useful)?
 
d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>


From ietf-nomcom-errors@lists.elistx.com Thu Mar 13 14:25:07 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBP00304CITF7@eListX.com>
 (original mail from galvin+ietf-nomcom@elistx.com); Thu,
 13 Mar 2003 14:23:17 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBP00301CISF2@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 13 Mar 2003 14:23:16 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBP00301CISF0@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 13 Mar 2003 14:23:16 -0500 (EST)
Received: from localhost (one.elistx.com [209.116.252.130])
 by eListX.com (PMDF V6.0-025 #44856)
 with ESMTP id <0HBP001AICIR3D@eListX.com>; Thu,
 13 Mar 2003 14:23:16 -0500 (EST)
Date: Thu, 13 Mar 2003 14:22:43 -0500 (Eastern Standard Time)
From: James M Galvin <galvin+ietf-nomcom@eListX.com>
Subject: Re: IAB request for clarifications in RFC2727bis
In-reply-to: <3E6E5E89.7090205@thinkingcat.com>
To: Leslie Daigle <leslie@thinkingcat.com>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <Pine.WNT.4.51.0303131404470.1056@office.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
References: <3E6E5E89.7090205@thinkingcat.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


On Tue, 11 Mar 2003, Leslie Daigle wrote:

    1/ An overall clarification is needed in terms of how to handle the
    mid-term transition of a member from one position to another.  That
    is, if a member of one body, whose term there is not finishing,
    accepts nomination to an opening in the other body (or a different
    position in the IESG) as part of the annual cycle, what is the
    expected practice:

It is my opinion you can treat this as a special case...or not.

Although it has been discussed, we have never called the question as to
whether or not an individual can serve in more than one role.  My
recollection of such discussions is a predominant theme was that no one
in their right mind would do such a thing, nor would the NOMCOM let
them.

So, on the one hand, if that's true, I think there's enough documented
process to address this issue.  Certainly, a person can resign at any
time from any position.  This then makes a mid-term vacancy for which
the process of filling is already specified.

The only real issue I see is one of timing.  Frankly, I don't believe we
need to document a specific sequence of events for this case.
Presumably everyone is acting in the best interests of the community
(you wouldn't be where you are if you weren't) and I for one trust the
"royal you" to do what works best for all parties concerned, including
the community.

On the other hand, if you want to call the question of a person filling
more than one role simultaneously, please say so.

    2/ Is the IAB's role to exercise good judgement about the
    qualifications of each nominee or is the IAB's role limited to
    process review only?

I like Dave Crocker's response.

Note that this iteration of the document includes an explicit statement
that the NOMCOM and the confirming body are to interact regarding the
slate.  In addition, the NOMCOM is required to support their chosen
slate with a summary of why they believe each candidate is the best
choice.  In other words, we are one step closer to Dave's suggestion for
a collegial teleconference, but we are not overly specific about it.

Jim

From ietf-nomcom-errors@lists.elistx.com Thu Mar 13 14:55:16 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBP00404DRBTM@eListX.com> (original mail from leslie@thinkingcat.com)
 ; Thu, 13 Mar 2003 14:49:59 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBP00401DRATD@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 13 Mar 2003 14:49:58 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBP00401DR9T9@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 13 Mar 2003 14:49:57 -0500 (EST)
Received: from cliffie.verisignlabs.com
 (thing.verisignlabs.com [65.201.175.62]) by eListX.com (PMDF V6.0-025 #44856)
 with ESMTP id <0HBP002AXDR9JL@eListX.com> for ietf-nomcom@lists.elistx.com;
 Thu, 13 Mar 2003 14:49:57 -0500 (EST)
Received: from thinkingcat.com (h87.s239.netsol.com [216.168.239.87])
 (AUTH: PLAIN leslie, TLS: TLSv1/SSLv3,128bits,RC4-MD5)
 by cliffie.verisignlabs.com with esmtp; Thu, 13 Mar 2003 14:49:09 -0500
Date: Thu, 13 Mar 2003 14:49:14 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
Subject: Re: IAB request for clarifications in RFC2727bis
To: James M Galvin <galvin+ietf-nomcom@eListX.com>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <3E70E0BA.1060704@thinkingcat.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
References: <3E6E5E89.7090205@thinkingcat.com>
 <Pine.WNT.4.51.0303131404470.1056@office.elistx.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>



To clarify:

James M Galvin wrote:
> On Tue, 11 Mar 2003, Leslie Daigle wrote:
> 
>     1/ An overall clarification is needed in terms of how to handle the
>     mid-term transition of a member from one position to another.  That
>     is, if a member of one body, whose term there is not finishing,
>     accepts nomination to an opening in the other body (or a different
>     position in the IESG) as part of the annual cycle, what is the
>     expected practice:
> 
> It is my opinion you can treat this as a special case...or not.
> 
> Although it has been discussed, we have never called the question as to
> whether or not an individual can serve in more than one role.  My
> recollection of such discussions is a predominant theme was that no one
> in their right mind would do such a thing, nor would the NOMCOM let
> them.
> 
> So, on the one hand, if that's true, I think there's enough documented
> process to address this issue.  Certainly, a person can resign at any
> time from any position.  This then makes a mid-term vacancy for which
> the process of filling is already specified.
> 
> The only real issue I see is one of timing.  Frankly, I don't believe we
> need to document a specific sequence of events for this case.
> Presumably everyone is acting in the best interests of the community
> (you wouldn't be where you are if you weren't) and I for one trust the
> "royal you" to do what works best for all parties concerned, including
> the community.
> 
> On the other hand, if you want to call the question of a person filling
> more than one role simultaneously, please say so.
> 

Timing is indeed the key issue.  For fun, why don't you document
what you think is the appropriate sequence of events given
the existing process?

Leslie.


-- 

-------------------------------------------------------------------
"Reality:
     Yours to discover."
                                -- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------



From ietf-nomcom-errors@lists.elistx.com Thu Mar 13 16:15:02 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBP00804HEVLD@eListX.com> (original mail from gih@telstra.net); Thu,
 13 Mar 2003 16:08:55 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBP00801HEUL9@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 13 Mar 2003 16:08:54 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBP00801HEUL8@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 13 Mar 2003 16:08:54 -0500 (EST)
Received: from kahuna.telstra.net (kahuna.telstra.net [203.50.0.6])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HBP00686HESXU@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 13 Mar 2003 16:08:53 -0500 (EST)
Received: from gih505.telstra.net (dhcp97.potaroo.net [203.10.60.97])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id h2DL7iMQ078384; Fri,
 14 Mar 2003 08:07:54 +1100 (EST envelope-from gih@telstra.net)
Date: Fri, 14 Mar 2003 08:03:38 +1100
From: Geoff Huston <gih@telstra.net>
Subject: Re: IAB request for clarifications in RFC2727bis
In-reply-to: <1739077783.20030313095711@brandenburg.com>
X-Sender: gih@kahuna.telstra.net
To: Dave Crocker <dhc@dcrocker.net>
Cc: Phil Roberts <PRoberts@MEGISTO.com>,
 'Leslie Daigle' <leslie@thinkingcat.com>, ietf-nomcom@lists.elistx.com,
 avri@acm.org
Message-id: <5.1.0.14.2.20030314080111.01b2ba88@kahuna.telstra.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: text/plain; format=flowed; charset=us-ascii
References: <5.1.0.14.2.20030313105933.01bf3fe0@kahuna.telstra.net>
 <5.1.0.14.2.20030313105933.01bf3fe0@kahuna.telstra.net>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

At 09:57 AM 3/13/2003 -0500, Dave Crocker wrote:
>Geoff,
>
>GH> that the Board did not feel that it could make substantive comment
>GH> on the process used by the Nomcom, nor was it able to provide
>GH> and alternate view on the qualifications of the individuals named in
>
>  Did those discussions, or your own thoughts, produce any suggestions
>  that might enable the ISOC review to be more substantial (and
>  therefore more useful)?


I am going back over 3 years in my comment. At the time the ISOC Board
did not want to be seen to interfere in the IETF, and saw themselves
in a scripted and bounded role.

Things may have changed in recent years, and Brian and Fred
are more up to date than I.

    Geoff





From ietf-nomcom-errors@lists.elistx.com Fri Mar 14 07:25:08 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBQ00I04NTN47@eListX.com> (original mail from brian@hursley.ibm.com)
 ; Fri, 14 Mar 2003 07:24:59 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBQ00I01NTM45@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Fri,
 14 Mar 2003 07:24:59 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBQ00I01NTM44@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Fri, 14 Mar 2003 07:24:58 -0500 (EST)
Received: from d12lmsgate.de.ibm.com (d12lmsgate.de.ibm.com [194.196.100.234])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HBQ00E6UNTLJE@eListX.com>
 for ietf-nomcom@lists.elistx.com; Fri, 14 Mar 2003 07:24:58 -0500 (EST)
Received: from d12relay01.de.ibm.com (d12relay01.de.ibm.com [9.165.215.22])
	by d12lmsgate.de.ibm.com (8.12.8/8.12.3) with ESMTP id h2ECNtSo096380; Fri,
 14 Mar 2003 13:23:56 +0100
Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140])
	by d12relay01.de.ibm.com (8.12.8/NCO/VER6.5) with SMTP id h2ECNs2w114232; Fri,
 14 Mar 2003 13:23:54 +0100
Received: from dhcp23-54.zurich.ibm.com by ochsehorn.zurich.ibm.com
 (AIX 4.3/UCB 5.64/4.03)          id AA40592 from <brian@hursley.ibm.com>; Fri,
 14 Mar 2003 13:23:49 +0100
Date: Fri, 14 Mar 2003 13:22:48 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Subject: Re: IAB request for clarifications in RFC2727bis
To: Geoff Huston <gih@telstra.net>
Cc: Dave Crocker <dhc@dcrocker.net>, Phil Roberts <PRoberts@MEGISTO.com>,
 'Leslie Daigle' <leslie@thinkingcat.com>, ietf-nomcom@lists.elistx.com,
 avri@acm.org
Message-id: <3E71C998.FF030DEB@hursley.ibm.com>
Organization: IBM
MIME-version: 1.0
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en,fr,de
References: <5.1.0.14.2.20030313105933.01bf3fe0@kahuna.telstra.net>
 <5.1.0.14.2.20030313105933.01bf3fe0@kahuna.telstra.net>
 <5.1.0.14.2.20030314080111.01b2ba88@kahuna.telstra.net>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

This is the main reason why I believe an ISOC Board liaison
in the NomCom is essential. Up to now, the Board has had no
way to get an unbiased view of whether the process has run
well. Last year, when NomCom took one or two surprising
decisions, this led to a good deal of last minute emergency
communication (and confusion).

On the second question the IAB raised - I believe very strongly
that both confirming bodies are *not* just there to verify process.
If a confirming body, after due diligence, concludes solemnly
that the NomCom has made an unacceptable choice, the confirming
body needs to say no. Otherwise, the checks and balances are
not meaningful.

Of course, I hope this will be an extremely rare situation.

    Brian

Geoff Huston wrote:
> 
> At 09:57 AM 3/13/2003 -0500, Dave Crocker wrote:
> >Geoff,
> >
> >GH> that the Board did not feel that it could make substantive comment
> >GH> on the process used by the Nomcom, nor was it able to provide
> >GH> and alternate view on the qualifications of the individuals named in
> >
> >  Did those discussions, or your own thoughts, produce any suggestions
> >  that might enable the ISOC review to be more substantial (and
> >  therefore more useful)?
> 
> I am going back over 3 years in my comment. At the time the ISOC Board
> did not want to be seen to interfere in the IETF, and saw themselves
> in a scripted and bounded role.
> 
> Things may have changed in recent years, and Brian and Fred
> are more up to date than I.
> 
>     Geoff
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.elistx.com/subscribe>

From ietf-nomcom-errors@lists.elistx.com Fri Mar 14 10:05:10 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBQ00104UZ80I@eListX.com>
 (original mail from galvin+ietf-nomcom@eListX.com); Fri,
 14 Mar 2003 09:59:33 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBQ00101UZ80A@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Fri,
 14 Mar 2003 09:59:32 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBQ00101UZ808@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Fri, 14 Mar 2003 09:59:32 -0500 (EST)
Received: from localhost (one.elistx.com [209.116.252.130])
 by eListX.com (PMDF V6.0-025 #44856)
 with ESMTP id <0HBQ00JFFUZ7UN@eListX.com>; Fri,
 14 Mar 2003 09:59:31 -0500 (EST)
Date: Fri, 14 Mar 2003 09:58:58 -0500 (Eastern Standard Time)
From: James M Galvin <galvin+ietf-nomcom@eListX.com>
Subject: Re: IAB request for clarifications in RFC2727bis
In-reply-to: <3E70E0BA.1060704@thinkingcat.com>
To: Leslie Daigle <leslie@thinkingcat.com>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <Pine.WNT.4.51.0303140937540.3676@office.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
References: <3E6E5E89.7090205@thinkingcat.com>
 <Pine.WNT.4.51.0303131404470.1056@office.elistx.com>
 <3E70E0BA.1060704@thinkingcat.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


On Thu, 13 Mar 2003, Leslie Daigle wrote:

    James M Galvin wrote:

    > On Tue, 11 Mar 2003, Leslie Daigle wrote:
    >
    >     1/ An overall clarification is needed in terms of how to handle the
    >     mid-term transition of a member from one position to another.

    > The only real issue I see is one of timing.  Frankly, I don't believe we
    > need to document a specific sequence of events for this case.

    Timing is indeed the key issue.  For fun, why don't you document
    what you think is the appropriate sequence of events given
    the existing process?

The only timing issue I see is how to deal with confidentiality, which
becomes increasingly awkward as the number of people who know about the
transition increases.

Setting that aside for the moment, since you asked for a sequence of
events, something like this:

    NOMCOM needs to fill roleB-1
    NOMCOM wants person in roleA-2
    personA-2 agrees
    NOMCOM needs to fill roleA-2
        note that roleA-1 is presumably already being replaced

    at IETF personB-1 is asked to step down
    at IETF personA-2 resigns roleA-2, gets 2 year term in roleB-1
    at IETF new person gets roleA-2 for 1 year term
        personally, I think the NOMCOM could make a case to give this
        person a 3 year term because to force it with the rules all you
        need is for personA-2 to resign just before the IETF so the
        remaining term is more than 1 year.

If all the parties in this transaction know what's happening I still
don't see an issue.  The critical party of course is personB-1.  If
personB-1 does not know then that makes it awkward for a fair number of
people, including:

    personB-2 - who will be consulted on their partner
    the incumbent in roleA-1 assuming they will be re-nominated, since
        they will be consulted on their partner
    personA-2 - who now knows about their situation, the situation of
	personA-1, and the situation of personB-1

It's also important to keep in mind that although the NOMCOM can not
comment on any action in progress, there is nothing to prevent personA-2
from commenting about their own situation, e.g., "I am talking to the
NOMCOM about moving to roleB-1."  This is allowed by the rules.

In any case, I don't see how specifying exactly how this situation
should play out will fix the confidentiality problem.

If there's a deeper timing issue I'm missing it.

Jim

From ietf-nomcom-errors@lists.elistx.com Fri Mar 14 15:55:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBR00H04BDG6O@eListX.com> (original mail from gih@telstra.net); Fri,
 14 Mar 2003 15:53:40 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBR00H01BDF6M@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Fri,
 14 Mar 2003 15:53:39 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBR00H01BDF6K@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Fri, 14 Mar 2003 15:53:39 -0500 (EST)
Received: from kahuna.telstra.net (kahuna.telstra.net [203.50.0.6])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HBR00F9SBDDI3@eListX.com>
 for ietf-nomcom@lists.elistx.com; Fri, 14 Mar 2003 15:53:39 -0500 (EST)
Received: from gih505.telstra.net (dhcp97.potaroo.net [203.10.60.97])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id h2EKqeMP013283	for
 <ietf-nomcom@lists.elistx.com>; Sat,
 15 Mar 2003 07:52:50 +1100 (EST envelope-from gih@telstra.net)
Date: Sat, 15 Mar 2003 07:49:14 +1100
From: Geoff Huston <gih@telstra.net>
Subject: Re: IAB request for clarifications in RFC2727bis
In-reply-to: <3E71C998.FF030DEB@hursley.ibm.com>
X-Sender: gih@kahuna.telstra.net
To: ietf-nomcom@lists.elistx.com
Message-id: <5.1.0.14.2.20030315074501.020c0928@kahuna.telstra.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: text/plain; format=flowed; charset=us-ascii
References: <5.1.0.14.2.20030313105933.01bf3fe0@kahuna.telstra.net>
 <5.1.0.14.2.20030313105933.01bf3fe0@kahuna.telstra.net>
 <5.1.0.14.2.20030314080111.01b2ba88@kahuna.telstra.net>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

At 01:22 PM 3/14/2003 +0100, Brian E Carpenter wrote:
>This is the main reason why I believe an ISOC Board liaison
>in the NomCom is essential. Up to now, the Board has had no
>way to get an unbiased view of whether the process has run
>well. Last year, when NomCom took one or two surprising
>decisions, this led to a good deal of last minute emergency
>communication (and confusion).


The ISOC Board did have a liaison to the Nomcom in the early days. I
was an ISOC liaison on the first Nomcom.

I can report that it certainly made it easier in the confirmation stage,
where the Board was able to gain some first-hard assurance that
the committee had acted diligently and appropriately in reaching
its slate.

I've forgotten when this was phased out, but by 1997 I know
that the ISOC liaison position had fallen by the wayside. LIke
Brian I would say that there is some considerable merit in having
such an ISOC liaison position from the ISOC Board of Trustees.

    Geoff




From ietf-nomcom-errors@lists.elistx.com Fri Mar 14 17:05:06 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBR00K04EMPCA@eListX.com> (original mail from leslie@thinkingcat.com)
 ; Fri, 14 Mar 2003 17:04:01 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBR00K01EMPC7@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Fri,
 14 Mar 2003 17:04:01 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBR00K01EMOC6@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Fri, 14 Mar 2003 17:04:00 -0500 (EST)
Received: from zak.ecotroph.net (zak.ecotroph.net [216.38.143.123])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HBR00FLIEMNI3@eListX.com>
 for ietf-nomcom@lists.elistx.com; Fri, 14 Mar 2003 17:04:00 -0500 (EST)
Received: from thinkingcat.com
 (ip68-98-181-124.nv.nv.cox.net [::ffff:68.98.181.124])
 (AUTH: LOGIN leslie, TLS: TLSv1/SSLv3,128bits,RC4-MD5)
 by zak.ecotroph.net with esmtp; Fri, 14 Mar 2003 17:03:02 -0500
Date: Fri, 14 Mar 2003 17:02:56 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
Subject: Re: IAB request for clarifications in RFC2727bis
To: James M Galvin <galvin+ietf-nomcom@eListX.com>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <3E725190.6060400@thinkingcat.com>
Organization: Thinking Cat Enterprises
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
References: <3E6E5E89.7090205@thinkingcat.com>
 <Pine.WNT.4.51.0303131404470.1056@office.elistx.com>
 <3E70E0BA.1060704@thinkingcat.com>
 <Pine.WNT.4.51.0303140937540.3676@office.elistx.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>



I believe that's the desired effect.

At issue is aligning it with stated procedure:

James M Galvin wrote:
> Setting that aside for the moment, since you asked for a sequence of
> events, something like this:
> 
>     NOMCOM needs to fill roleB-1
>     NOMCOM wants person in roleA-2
>     personA-2 agrees
>     NOMCOM needs to fill roleA-2

Bug:  NomCom doesn't declare open slots.  The IAB and IESG
tell the NomCom (via the IETF ExecDir) that they have a vacancy
to fill.  Therefore, according to RFC2727, this slot cannot
be declared open (and therefore filled) until the slate is
announced and the relevant body can make this declaration.

At which point the mid-term vacancy process kicks in, and there's
a question about whether or not the position should be separately
announced and a new round of nominees solicited.

As I said -- the process you outlined seems reasonable; it's
just not what appears to be documented.

Leslie.

-- 

-------------------------------------------------------------------
"Reality:
      Yours to discover."
                                 -- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------



From ietf-nomcom-errors@lists.elistx.com Fri Mar 14 20:35:05 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBR00504O3NYN@eListX.com> (original mail from sob@newdev.harvard.edu)
 ; Fri, 14 Mar 2003 20:28:36 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBR00501O3NYL@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Fri,
 14 Mar 2003 20:28:35 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBR00501O3NYJ@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Fri, 14 Mar 2003 20:28:35 -0500 (EST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
 by eListX.com (PMDF V6.0-025 #44856)
 with ESMTP id <0HBR00MIGO3M2M@eListX.com>; Fri,
 14 Mar 2003 20:28:34 -0500 (EST)
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h2F1RjkZ002718; Fri,
 14 Mar 2003 20:27:45 -0500 (EST)
Received: (from sob@localhost)	by newdev.harvard.edu (8.12.7/8.12.2/Submit)
 id h2F1RjGq002717; Fri, 14 Mar 2003 20:27:45 -0500 (EST)
Date: Fri, 14 Mar 2003 20:27:45 -0500 (EST)
From: Scott Bradner <sob@harvard.edu>
Subject: Re: IAB request for clarifications in RFC2727bis
In-reply-to: <3E725190.6060400@thinkingcat.com>
To: galvin+ietf-nomcom@eListX.com, leslie@thinkingcat.com
Cc: ietf-nomcom@lists.elistx.com
Message-id: <200303150127.h2F1RjGq002717@newdev.harvard.edu>
Content-type: TEXT/PLAIN
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

> Therefore, according to RFC2727, this slot cannot
> be declared open (and therefore filled) until the slate is
> announced and the relevant body can make this declaration.

a tweak on this happend this year (and once before) where 
someone with ayear left in their term moved from the IAB to the IESG

if the nomcom followed the above they would have not filled the 
rest of the IAB term but instead would have waited and used the
mid-term vacancy process for the IAB slot. (or am I misreading 
what Leslie is saying?)

Scott



From ietf-nomcom-errors@lists.elistx.com Fri Mar 14 22:05:13 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBR00804SAP8I@eListX.com>
 (original mail from galvin+ietf-nomcom@eListX.com); Fri,
 14 Mar 2003 21:59:13 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBR00801SAO8A@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Fri,
 14 Mar 2003 21:59:13 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBR00801SAO88@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Fri, 14 Mar 2003 21:59:12 -0500 (EST)
Received: from localhost (one.elistx.com [209.116.252.130])
 by eListX.com (PMDF V6.0-025 #44856)
 with ESMTP id <0HBR001FJSAM4Z@eListX.com>; Fri,
 14 Mar 2003 21:59:12 -0500 (EST)
Date: Fri, 14 Mar 2003 21:58:37 -0500 (Eastern Standard Time)
From: James M Galvin <galvin+ietf-nomcom@eListX.com>
Subject: Re: IAB request for clarifications in RFC2727bis
In-reply-to: <3E725190.6060400@thinkingcat.com>
To: Leslie Daigle <leslie@thinkingcat.com>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <Pine.WNT.4.51.0303142139110.2156@office.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
References: <3E6E5E89.7090205@thinkingcat.com>
 <Pine.WNT.4.51.0303131404470.1056@office.elistx.com>
 <3E70E0BA.1060704@thinkingcat.com>
 <Pine.WNT.4.51.0303140937540.3676@office.elistx.com>
 <3E725190.6060400@thinkingcat.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


On Fri, 14 Mar 2003, Leslie Daigle wrote:

    As I said -- the process you outlined seems reasonable; it's
    just not what appears to be documented.

I have always believed and defended that a fundamental tenet of the
NOMCOM document is to behave and execute "in the best interests of the
community."

So, to interpret the document as strictly as you are suggesting is not,
in my opinion of course, in the best interests of the community.

Further, the first rule of the operation of the NOMCOM is that the group
as a whole can make up rules (not otherwise covered) as it needs to
complete its responsibilities in a timely fashion.

In the scenario you lay out it is only the timing that is at issue.  You
are not inventing an end-game or a process that could not ordinarily be
covered by the current procedures.

Yes, you could wait to announce the resignation until the confirmed
candidates are announced, but to what end?  So the IESG/IAB has to
operate 1 person short waiting for a mid-term vacancy to be filled?  So
the NOMCOM has to work an extra 6 weeks to fill the mid-term vacancy?
So you don't breach confidentiality asking the Executive Director (and
whoever else you need to ask) to help you put together a job
description?

If the resignation is going to happen I believe you can use the "invent
rules as needed" clause to proceed as needed to make the most efficient
use of the resources available.

Jim

From ietf-nomcom-errors@lists.elistx.com Fri Mar 14 22:25:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBR00804TE0U2@eListX.com> (original mail from sob@newdev.harvard.edu)
 ; Fri, 14 Mar 2003 22:22:48 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBR00801TDZU0@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Fri,
 14 Mar 2003 22:22:48 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBR00801TDZTZ@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Fri, 14 Mar 2003 22:22:47 -0500 (EST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HBR001HKTDZ4Z@eListX.com>
 for ietf-nomcom@lists.elistx.com; Fri, 14 Mar 2003 22:22:47 -0500 (EST)
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h2F3LxkZ002900	for
 <ietf-nomcom@lists.elistx.com>; Fri, 14 Mar 2003 22:21:59 -0500 (EST)
Received: (from sob@localhost)	by newdev.harvard.edu (8.12.7/8.12.2/Submit)
 id h2F3Lxf2002899	for ietf-nomcom@lists.elistx.com; Fri,
 14 Mar 2003 22:21:59 -0500 (EST)
Date: Fri, 14 Mar 2003 22:21:59 -0500 (EST)
From: Scott Bradner <sob@harvard.edu>
Subject: Re: IAB request for clarifications in RFC2727bis
To: ietf-nomcom@lists.elistx.com
Message-id: <200303150321.h2F3Lxf2002899@newdev.harvard.edu>
Content-type: TEXT/PLAIN
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>



to expand further

case 1:
	sitting IAB member (in middle of term) moves to IESG

case 2:
	sitting IESG member (in middle of term) moves to IAB

I see little reason to do a new call for folk in case 1
	the nomcom already has a list of people its looking at for 
	the IAB - putting out a new call will not make
	much difference to the list the nomcom has - so I
	think the nomcom should just go ahead and fill the
	IAB slot with someone their list

but I do see a problem with case 2
	people who might be interested in the IESG slot
	but refrained from having their name in the pool
	for one reason or another related to the people
	in the AD slot(s) (e.g., 'I do not want to work with X'
	or 'I do not want to kick Y out') might be interested 
	after the sitting AD moves to the IAB

	it may be better in this case to do the new call for
	interested people.

Scott

From ietf-nomcom-errors@lists.elistx.com Fri Mar 21 14:05:03 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC400H024JSDE@eListX.com>
 (original mail from ietf-nomcom+moderator@lists.elistx.com); Fri,
 21 Mar 2003 13:55:04 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC400G01403SW@eListX.com> for ietf-nomcom+moderator@lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Fri, 21 Mar 2003 13:43:15 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HC400G01403SV@eListX.com> for
 ietf-nomcom+moderator@lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com)
 ; Fri, 21 Mar 2003 13:43:15 -0500 (EST)
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC400G04403SS@eListX.com> for ietf-nomcom+moderator@lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Fri, 21 Mar 2003 13:43:15 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HC400G01402SQ@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Fri,
 21 Mar 2003 13:43:14 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC400G01402SP@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Fri, 21 Mar 2003 13:43:14 -0500 (EST)
Received: from heron.mail.pas.earthlink.net
 (heron.mail.pas.earthlink.net [207.217.120.189])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HC400CCP401YA@eListX.com>
 for ietf-nomcom@lists.elistx.com; Fri, 21 Mar 2003 13:43:14 -0500 (EST)
Received: from wl-141-254.wireless.ietf56.ietf.org
 ([130.129.141.254] helo=STJOHNS-LAPTOP.mindspring.com)
 by heron.mail.pas.earthlink.net with asmtp (SSLv3:DES-CBC3-SHA:168)
 (Exim 3.33 #1)	id 18wRT9-00024B-00; Fri, 21 Mar 2003 10:42:19 -0800
Date: Fri, 21 Mar 2003 13:42:12 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Notes from one member of the IAB on the current draft
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: ietf-nomcom@lists.elistx.com
Cc: iab@ietf.org
Message-id: <5.1.0.14.2.20030321133351.030f5740@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: text/plain; charset=us-ascii; format=flowed
X-Spam-Status: No,
 hits=2.7 required=7.5 tests=DOUBLE_CAPSWORD,MSG_ID_ADDED_BY_MTA_2 version=2.31
X-Spam-Level: **
X-ELNK-Trace:
 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4defdc80e30b2531b89f09be39abb50a8b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Note: I do not subscribe to this list - please cc me on any relevant dialog.

The IAB encountered some issues with trying to follow RFC2727 during the 
confirmation process.  Without going into details inappropriate due to the 
confidentiality of that process, I would like to suggest some changes to 
the current draft.  While these changes originate mostly from me, other 
2002 IAB members have provided their input - e.g. input was not solicited 
from the new members of the IAB.

These suggested changes apply to 
draft 
http://www.ietf.org/internet-drafts/draft-ietf-nomcom-rfc2727bis-03.txt and 
are divided into two sections - procedure and policy.  Procedure deals with 
interpretations of existing rules, fixes ambiguities etc.  Policy delves 
into the realm of whys and wherefores.  The intent of the procedure 
comments is to eliminate some ambiguities in 2727 still not fixed in the 
referenced draft.  The intent of the policy comments is to place a stake 
where I personally believe certain interpretations should be taken.  Your 
mileage may vary.

Procedure:

 >> In Definitions add to the "sitting member" definition at the end:

"For the purposes of this document, the phrase 'sitting members of the IAB' 
excludes the Chair of the IETF.  The chair of the IETF is a sitting member 
of the IESG and is nominated and confirmed as such."

 >>In Definitions add the definitions of "qualified member"

"The term 'qualified members' means all the sitting members of a body minus 
any member who recuses him or herself for a particular question due to 
conflict of interest or for any other purpose. A sitting member MUST recuse 
or disqualify themselves from any question related to their own 
confirmation or tenure in office."

[NOTE:  The document should be reviewed and "qualified member" substituted 
for "sitting member" where appropriate]

 >>Replace in section 3, paragraph 5  paragraph beginning "Fourth, the 
term... " with:

"Fourth, the term of the confirmed candidate will be either:

1.  The remainder of the term if the vacancy occurs before or at the end of 
the First IETF.
2.  The remainder of the term plus a full term if the vacancy occurs after 
the First IETF."

 >>Section 3, paragraph 7, subparagraph 4 is deleted and replaced with"

"The confirming bodies decide their consent according to a mechanism of 
their own choosing, which must ensure that at least a majority of the 
qualified members confirm each nominee.

A majority of the qualified members of the confirming bodies must agree to 
confirm each individual nominee. The agreement must be decided within a 
reasonable time frame. The agreement may be decided by conducting a formal 
vote, by asserting consensus based on informal exchanges (email), or by 
whatever mechanism is used to conduct the normal business of the confirming 
body."

[The current language of half accepting or half rejecting can hang either 
by having half both accept and reject, or by not having either half accept 
or reject.  This language repairs that problem]

 >>Insert in section 3 as last paragraph -  8.

"With the exception of the IESG chair who is also, by rule, a member of the 
IAB, and except as provided in section 3 paragraph 4 (i.e. overlaps during 
the First IETF) a person may not simultaneously hold membership in both the 
IAB and the IESG. Any member of one body who is appointed to the other body 
as a result of the annual Nomcom process vacates their position on the 
first body no later than the end of the First IETF. Any member of one body 
who is appointed to the other as a result of a mid-term vacancy vacates 
their position on the first body immediately upon confirmation to the 
second body."



 >>Insert in section 3 as paragraph 6 and renumber all subsequent paragraphs:

"Nomcom-caused Mid-term Vacancies:

 From time to time the Nomcom may propose moving a serving Area Director or 
IAB member from one position to another. (E.g. moving a Transport AD to 
cover O&M). If the serving member is at the end of their normal term there 
is no change in procedures. Otherwise, this is treated as a mid-term 
vacancy and mid-term procedures are used with the following exceptions:

a) If the vacancy will occur on the IAB due to a move from the IAB to the 
IESG, the Nomcom may, upon confirmation of nominee/IAB member, submit for 
confirmation as part of the normal slate of candidates another nominee to 
complete the term of the departing IAB member. If the Nomcom declines to 
nominate a replacement as part of the annual process, the IAB may, at any 
time after the confirmation of the departing member, ask the Nomcom to fill 
the slot using mid-term procedures.

b) If the vacancy will occur on the IESG, either as a move to another IESG 
slot or as a move to the IAB, the Nomcom must use mid-term procedure rules. 
Most importantly, they must advertise the vacancy, and must consider all 
new candidates as equitably as any previously considered. The IESG chair is 
responsible for notifying the IETF Executive director of the vacancy and 
who in turn is responsible for asking the Nomcom select the replacement. 
The Nomcom is explicitly barred from proceeding without an explicit request 
from the IESG chair. The term of the nominee shall be for the remainder of 
the term of the vacated position."


 >>Insert at end of section 3 as paragraph 9:

[Note: the actual issue is that there is no succession plan or backup for 
the IETF chair unlike all other positions in the IETF.  It may be 
sufficient to say that the IESG selects an interim or that the position 
remains vacant, but it needs to be stated. The following paragraph builds 
on the current practice that the IAB confirms the IESG - it may not be 
appropriate for an interim appointment.]

If the IESG Chair position becomes vacant for any reason, the IAB shall 
appoint an acting IESG Chair from among those sitting members of the IESG 
who specifically remove themselves from consideration as a permanent 
replacement for the Chair and indicate a willingness to serve, or if none 
remove themselves or none indicate a willingness to serve, from the IESG as 
a whole. The IAB shall select the chair by simple majority vote of the 
qualified IAB members. If no candidate receives a majority of the votes, 
the selection will be repeated considering only those candidates who 
received the two highest number of votes. In the event no candidate 
receives a majority of votes, the candidate with the most number of votes 
shall be selected. In the event of a tie, the IAB chair shall direct who 
shall be selected from those candidates with the most number of votes. This 
selection shall be accomplished as expeditiously as possible, but not later 
than one week after the vacancy.

The acting Chair shall serve until the Nomcom completes the nomination 
process and until the IAB confirms the nominee.

 >>Policy:

[These relate to state of mind and intentions of the confirming bodies and 
may or may not be reasonable statements of the charge given to each 
confirming body for its part in the Nomcom process.  More than the 
procedure section, these mostly represent my stake in the ground rather 
than a coordinated position of the IAB]

 >>Add to end of Section 3, paragraph 7 subparagraph 4 as amended above:

"Each qualified member may base their decision on confirmation on any or 
all of: their own knowledge of the candidate; information provided by the 
Nomcom in support of the nomination; information provided by other members 
during discussion of the candidate; and their personal understanding of the 
requirements of the position. Confirmation should not be a rubber stamp of 
the Nomcom's selections, but a reasoned and reasonable consideration of the 
nominee's qualifications for the position. A vote to confirm is an 
affirmative action which should indicate the member's confidence in the 
ability of the nominee to accomplish the goals of the position and the work 
of the IETF."

 >>Replace section 3, paragraph 7 sub paragraph 3 paragraph beginning "If 
some or none..." with:

"The confirming body may ask for additional information about a nominee 
from the Nomcom to assist them in their deliberations. However, both the 
confirming body and Nomcom should refrain from discussions of the 
availability, qualification or characteristics of other possible candidates 
for the position."


From ietf-nomcom-errors@lists.elistx.com Sun Mar 23 14:15:06 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC700G04UMFN6@eListX.com> (original mail from harald@alvestrand.no); Sun,
 23 Mar 2003 14:11:03 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HC700G01UMEN4@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Sun,
 23 Mar 2003 14:11:02 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC700G01UMEN3@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Sun, 23 Mar 2003 14:11:02 -0500 (EST)
Received: from eikenes.alvestrand.no (nat.alvestrand.no [217.13.28.204])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HC700F49UMD3D@eListX.com>
 for ietf-nomcom@lists.elistx.com; Sun, 23 Mar 2003 14:11:02 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP	id 92F0D6238A; Sun,
 23 Mar 2003 20:10:03 +0100 (CET)
Date: Sat, 22 Mar 2003 20:57:58 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
Subject: Re: Notes from one member of the IAB on the current draft
In-reply-to: <5.1.0.14.2.20030321133351.030f5740@pop.mindspring.com>
To: Michael StJohns <mstjohns@mindspring.com>, ietf-nomcom@lists.elistx.com
Cc: iab@ietf.org
Message-id: <32440196.1048366678@localhost>
MIME-version: 1.0
X-Mailer: Mulberry/3.0.2 (Win32)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
References: <5.1.0.14.2.20030321133351.030f5740@pop.mindspring.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>



--On 21. mars 2003 13:42 -0500 Michael StJohns <mstjohns@mindspring.com> 
wrote:

> b) If the vacancy will occur on the IESG, either as a move to another
> IESG slot or as a move to the IAB, the Nomcom must use mid-term procedure
> rules. Most importantly, they must advertise the vacancy, and must
> consider all new candidates as equitably as any previously considered.
> The IESG chair is responsible for notifying the IETF Executive director
> of the vacancy and who in turn is responsible for asking the Nomcom
> select the replacement. The Nomcom is explicitly barred from proceeding
> without an explicit request from the IESG chair. The term of the nominee
> shall be for the remainder of the term of the vacated position."

Nit: All versions of the nomcom documents say that the Nomcom is notified 
by the IETF Executive Director, not the IETF Chair. (the position "IESG 
Chair" does not exist - the IETF Chair chairs the IESG).

It's always been presumed that the ExDir was instructed by the IESG and IAB 
through mechanisms not documented in the Nomcom documents.

                     Harald

From ietf-nomcom-errors@lists.elistx.com Sun Mar 23 20:15:07 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC800604B704X@eListX.com> (original mail from brian@hursley.ibm.com)
 ; Sun, 23 Mar 2003 20:09:00 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HC800601B6Z4V@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Sun,
 23 Mar 2003 20:08:59 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC800601B6Z4U@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Sun, 23 Mar 2003 20:08:59 -0500 (EST)
Received: from d12lmsgate.de.ibm.com (d12lmsgate.de.ibm.com [194.196.100.234])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HC80036HB6YC8@eListX.com>
 for ietf-nomcom@lists.elistx.com; Sun, 23 Mar 2003 20:08:59 -0500 (EST)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate.de.ibm.com (8.12.8/8.12.3) with ESMTP id h2O17vSo105358; Mon,
 24 Mar 2003 02:07:57 +0100
Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140])
	by d12relay02.de.ibm.com (8.12.8/NCO/VER6.5) with SMTP id h2O17uH4270922; Mon,
 24 Mar 2003 02:07:56 +0100
Received: from gsine06.us.sine.ibm.com by ochsehorn.zurich.ibm.com
 (AIX 4.3/UCB 5.64/4.03)          id AA21302 from <brian@hursley.ibm.com>; Mon,
 24 Mar 2003 02:07:47 +0100
Date: Mon, 24 Mar 2003 01:33:58 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Subject: Re: Notes from one member of the IAB on the current draft
To: Michael StJohns <mstjohns@mindspring.com>
Cc: ietf-nomcom@lists.elistx.com, iab@ietf.org
Message-id: <3E7E5276.3AA6925D@hursley.ibm.com>
Organization: IBM
MIME-version: 1.0
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en,fr,de
References: <5.1.0.14.2.20030321133351.030f5740@pop.mindspring.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Most of these suggestions seem fine, but...

Michael StJohns wrote:

...
>  >>Replace section 3, paragraph 7 sub paragraph 3 paragraph beginning "If 
> some or none..." with:
> 
> "The confirming body may ask for additional information about a nominee 
> from the Nomcom to assist them in their deliberations. However, both the 
> confirming body and Nomcom should refrain from discussions of the 
> availability, qualification or characteristics of other possible candidates 
> for the position."

I have no problem with this as *additional* text, but I would object
to removing the original "If some or none..." paragraph, which I
believe is very necessary in its present form.

   Brian



From ietf-nomcom-errors@lists.elistx.com Mon Mar 24 10:25:03 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC900F02ED340@eListX.com>
 (original mail from ietf-nomcom+moderator@lists.elistx.com); Mon,
 24 Mar 2003 10:15:03 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC900E01DN7FO@eListX.com> for ietf-nomcom+moderator@lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 24 Mar 2003 09:59:32 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HC900E01DN7FN@eListX.com> for
 ietf-nomcom+moderator@lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com)
 ; Mon, 24 Mar 2003 09:59:31 -0500 (EST)
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC900E04DN7FK@eListX.com> for ietf-nomcom+moderator@lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 24 Mar 2003 09:59:31 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HC900E01DN6FI@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 24 Mar 2003 09:59:30 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC900E01DN6FH@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 24 Mar 2003 09:59:30 -0500 (EST)
Received: from sentry.gw.tislabs.com (sentry.gw.tislabs.com [192.94.214.100])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HC900BHBDN5E9@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 24 Mar 2003 09:59:30 -0500 (EST)
Received: by sentry.gw.tislabs.com; id JAA28112; Mon,
 24 Mar 2003 09:59:25 -0500 (EST)
Received: from dyn083.gw.tislabs.com(10.33.10.83) by sentry.gw.tislabs.com via
 smap (V5.5)	id xma028103; Mon, 24 Mar 2003 09:58:49 -0500
Date: Mon, 24 Mar 2003 09:57:46 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Notes from one member of the IAB on the current draft
In-reply-to: <3E7E5276.3AA6925D@hursley.ibm.com>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: Brian E Carpenter <brian@hursley.ibm.com>
Cc: ietf-nomcom@lists.elistx.com, iab@ietf.org
Message-id: <5.1.0.14.2.20030323200907.00ab70d8@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: text/plain; charset=us-ascii; format=flowed
References: <5.1.0.14.2.20030321133351.030f5740@pop.mindspring.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

At 01:33 AM 3/24/2003 +0100, Brian E Carpenter wrote:
>Most of these suggestions seem fine, but...
>
>Michael StJohns wrote:
>
>...
> >  >>Replace section 3, paragraph 7 sub paragraph 3 paragraph beginning "If
> > some or none..." with:
> >
> > "The confirming body may ask for additional information about a nominee
> > from the Nomcom to assist them in their deliberations. However, both the
> > confirming body and Nomcom should refrain from discussions of the
> > availability, qualification or characteristics of other possible 
> candidates
> > for the position."
>
>I have no problem with this as *additional* text, but I would object
>to removing the original "If some or none..." paragraph, which I
>believe is very necessary in its present form.
>
>    Brian

Hi Brian -

The text removed was:

>If some or none of the candidates submitted to a confirming
>            body are confirmed, the confirming body continues to consult
>            with the nominating committee both to explain the reason why
>            all the candidates were not confirmed and to understand the
>            nominating committee's rationale for the slate.  During the
>            course of the consultation the nominating committee may
>            re-examine the slate of candidates and may change it in any
>            way.


I find this paragraph to be particularly problematic.  The paragraph as 
written would tend to make the confirming bodies adjuncts of the Nomcom 
rather bodies with their own purpose.

Both the Nomcom and the confirming body have distinct and separate duties 
in the nominating process.  Having an on-going discussion about the 
relative merits of individual candidates seems to me to be a problem with 
separation of powers. If a confirming body chooses to not confirm a 
candidate, the rationale should be clear - i.e. the confirming body was 
unable to find a majority of members who were willing to confirm.  The 
individual members rationale for deciding not to confirm are relevant to 
the discussions within the confirming body, but are inappropriate to be 
shared outside that body.  [The confirming bodies are not made privy to the 
Nomcom discussions on the candidates, they're just provided with the output 
of that discussion.  It seems inappropriate for discussions/debate to be 
shared back from the confirming bodies to the Nomcom.]

Also, allowing the Nomcom to re-shuffle the slate seems also to be 
problematic as candidates are confirmed or rejected as individuals.

The Nomcom should offer its best candidates, make its case, and permit the 
confirming bodies to do their due diligence.  If a confirming body chooses 
not to confirm a candidate,  there shouldn't be an argument or discussion 
between the confirming body and the Nomcom as to whether either the Nomcom 
selection or the confirming body rejection was the right answer - that 
would denigrate the integrity of both processes and tend to lead to enmity 
between the two bodies.  If a candidate fails of selection, the Nomcom 
should then provide its next candidate.  Its probably useful, but shouldn't 
be required, for a confirming body to provide some general guidance as to 
why a candidate failed - it may be the confirming body may not have 
consensus on the reasons they failed to confirm, just that the candidate 
was not deemed acceptable.



From ietf-nomcom-errors@lists.elistx.com Mon Mar 24 10:25:06 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC900F08ED340@eListX.com>
 (original mail from ietf-nomcom+moderator@lists.elistx.com); Mon,
 24 Mar 2003 10:15:03 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC900E01DS9K6@eListX.com> for ietf-nomcom+moderator@lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 24 Mar 2003 10:02:33 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HC900E01DS8K5@eListX.com> for
 ietf-nomcom+moderator@lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com)
 ; Mon, 24 Mar 2003 10:02:32 -0500 (EST)
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC900E04DS8K2@eListX.com> for ietf-nomcom+moderator@lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 24 Mar 2003 10:02:32 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HC900E01DS7K0@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 24 Mar 2003 10:02:31 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC900E01DS7JZ@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 24 Mar 2003 10:02:31 -0500 (EST)
Received: from sentry.gw.tislabs.com (sentry.gw.tislabs.com [192.94.214.100])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HC900BECDS6E8@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 24 Mar 2003 10:02:31 -0500 (EST)
Received: by sentry.gw.tislabs.com; id KAA28199; Mon,
 24 Mar 2003 10:02:27 -0500 (EST)
Received: from dyn083.gw.tislabs.com(10.33.10.83) by sentry.gw.tislabs.com via
 smap (V5.5)	id xma028191; Mon, 24 Mar 2003 10:02:24 -0500
Date: Mon, 24 Mar 2003 10:01:22 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Notes from one member of the IAB on the current draft
In-reply-to: <32440196.1048366678@localhost>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf-nomcom@lists.elistx.com
Cc: iab@ietf.org
Message-id: <5.1.0.14.2.20030324095801.031e2f98@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: text/plain; charset=us-ascii; format=flowed
References: <5.1.0.14.2.20030321133351.030f5740@pop.mindspring.com>
 <5.1.0.14.2.20030321133351.030f5740@pop.mindspring.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

*bleah*  I've got a version of this with edits all the way through fixing 
this (IESG Chair vs IETF Chair)... thought that was the one I submitted.


At 08:57 PM 3/22/2003 -0800, Harald Tveit Alvestrand wrote:


>--On 21. mars 2003 13:42 -0500 Michael StJohns <mstjohns@mindspring.com> 
>wrote:
>
>>b) If the vacancy will occur on the IESG, either as a move to another
>>IESG slot or as a move to the IAB, the Nomcom must use mid-term procedure
>>rules. Most importantly, they must advertise the vacancy, and must
>>consider all new candidates as equitably as any previously considered.
>>The IESG chair is responsible for notifying the IETF Executive director
>>of the vacancy and who in turn is responsible for asking the Nomcom
>>select the replacement. The Nomcom is explicitly barred from proceeding
>>without an explicit request from the IESG chair. The term of the nominee
>>shall be for the remainder of the term of the vacated position."
>
>Nit: All versions of the nomcom documents say that the Nomcom is notified 
>by the IETF Executive Director, not the IETF Chair. (the position "IESG 
>Chair" does not exist - the IETF Chair chairs the IESG).

Right... thought I'd captured that.  The specific statement "Nomcom is 
explicitly barred from proceeding  without an explicit request from the 
IESG chair" was meant to be read in context with the previous "IESG chair 
is responsible for notifying the IETF Executive director".  Would "explicit 
notification" as opposed to "explicit request" be better here?

>It's always been presumed that the ExDir was instructed by the IESG and 
>IAB through mechanisms not documented in the Nomcom documents.

Yup.


>                     Harald


From ietf-nomcom-errors@lists.elistx.com Mon Mar 24 11:45:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC900J04IAT05@eListX.com> (original mail from brian@hursley.ibm.com)
 ; Mon, 24 Mar 2003 11:40:05 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HC900J01IAT03@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 24 Mar 2003 11:40:05 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HC900J01IAT02@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 24 Mar 2003 11:40:05 -0500 (EST)
Received: from d12lmsgate-4.de.ibm.com
 (d12lmsgate-4.de.ibm.com [194.196.100.237])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HC900FGBIARZH@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 24 Mar 2003 11:40:04 -0500 (EST)
Received: from d12relay01.de.ibm.com (d12relay01.de.ibm.com [9.165.215.22])
	by d12lmsgate-4.de.ibm.com (8.12.3/8.12.3) with ESMTP id h2OGd2dk044810; Mon,
 24 Mar 2003 17:39:02 +0100
Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140])
	by d12relay01.de.ibm.com (8.12.8/NCO/VER6.5) with SMTP id h2OGd2xR234048; Mon,
 24 Mar 2003 17:39:02 +0100
Received: from gsine08.us.sine.ibm.com by ochsehorn.zurich.ibm.com
 (AIX 4.3/UCB 5.64/4.03)          id AA49950 from <brian@hursley.ibm.com>; Mon,
 24 Mar 2003 17:38:59 +0100
Date: Mon, 24 Mar 2003 17:37:54 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Subject: Re: Notes from one member of the IAB on the current draft
To: Michael StJohns <mstjohns@mindspring.com>
Cc: ietf-nomcom@lists.elistx.com, iab@ietf.org
Message-id: <3E7F3462.11783050@hursley.ibm.com>
Organization: IBM
MIME-version: 1.0
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en,fr,de
References: <5.1.0.14.2.20030321133351.030f5740@pop.mindspring.com>
 <5.1.0.14.2.20030323200907.00ab70d8@pop.mindspring.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Well, we plain disagree. I found this paragraph perfect when chairing
both the confirming bodies, and didn't have any issue of separation
of function.

   Brian

Michael StJohns wrote:
> 
> At 01:33 AM 3/24/2003 +0100, Brian E Carpenter wrote:
> >Most of these suggestions seem fine, but...
> >
> >Michael StJohns wrote:
> >
> >...
> > >  >>Replace section 3, paragraph 7 sub paragraph 3 paragraph beginning "If
> > > some or none..." with:
> > >
> > > "The confirming body may ask for additional information about a nominee
> > > from the Nomcom to assist them in their deliberations. However, both the
> > > confirming body and Nomcom should refrain from discussions of the
> > > availability, qualification or characteristics of other possible
> > candidates
> > > for the position."
> >
> >I have no problem with this as *additional* text, but I would object
> >to removing the original "If some or none..." paragraph, which I
> >believe is very necessary in its present form.
> >
> >    Brian
> 
> Hi Brian -
> 
> The text removed was:
> 
> >If some or none of the candidates submitted to a confirming
> >            body are confirmed, the confirming body continues to consult
> >            with the nominating committee both to explain the reason why
> >            all the candidates were not confirmed and to understand the
> >            nominating committee's rationale for the slate.  During the
> >            course of the consultation the nominating committee may
> >            re-examine the slate of candidates and may change it in any
> >            way.
> 
> I find this paragraph to be particularly problematic.  The paragraph as
> written would tend to make the confirming bodies adjuncts of the Nomcom
> rather bodies with their own purpose.
> 
> Both the Nomcom and the confirming body have distinct and separate duties
> in the nominating process.  Having an on-going discussion about the
> relative merits of individual candidates seems to me to be a problem with
> separation of powers. If a confirming body chooses to not confirm a
> candidate, the rationale should be clear - i.e. the confirming body was
> unable to find a majority of members who were willing to confirm.  The
> individual members rationale for deciding not to confirm are relevant to
> the discussions within the confirming body, but are inappropriate to be
> shared outside that body.  [The confirming bodies are not made privy to the
> Nomcom discussions on the candidates, they're just provided with the output
> of that discussion.  It seems inappropriate for discussions/debate to be
> shared back from the confirming bodies to the Nomcom.]
> 
> Also, allowing the Nomcom to re-shuffle the slate seems also to be
> problematic as candidates are confirmed or rejected as individuals.
> 
> The Nomcom should offer its best candidates, make its case, and permit the
> confirming bodies to do their due diligence.  If a confirming body chooses
> not to confirm a candidate,  there shouldn't be an argument or discussion
> between the confirming body and the Nomcom as to whether either the Nomcom
> selection or the confirming body rejection was the right answer - that
> would denigrate the integrity of both processes and tend to lead to enmity
> between the two bodies.  If a candidate fails of selection, the Nomcom
> should then provide its next candidate.  Its probably useful, but shouldn't
> be required, for a confirming body to provide some general guidance as to
> why a candidate failed - it may be the confirming body may not have
> consensus on the reasons they failed to confirm, just that the candidate
> was not deemed acceptable.

From ietf-nomcom-errors@lists.elistx.com Mon Mar 24 20:25:07 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCA00G046FOQM@eListX.com> (original mail from mstjohns@mindspring.com)
 ; Mon, 24 Mar 2003 20:21:24 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCA00G016FMQI@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 24 Mar 2003 20:21:24 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCA00G016FLQH@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 24 Mar 2003 20:21:21 -0500 (EST)
Received: from stork.mail.pas.earthlink.net
 (stork.mail.pas.earthlink.net [207.217.120.188])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCA00F4Q6FKFJ@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 24 Mar 2003 20:21:21 -0500 (EST)
Received: from pcp802197pcs.nrockv01.md.comcast.net
 ([68.48.86.43] helo=STJOHNS-LAPTOP.mindspring.com)
	by stork.mail.pas.earthlink.net with asmtp (SSLv3:DES-CBC3-SHA:168)
	(Exim 3.33 #1)	id 18xd6z-0004h3-00; Mon, 24 Mar 2003 17:20:21 -0800
Date: Mon, 24 Mar 2003 20:20:12 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Notes from one member of the IAB on the current draft
In-reply-to: <3E7F3462.11783050@hursley.ibm.com>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: Brian E Carpenter <brian@hursley.ibm.com>
Cc: ietf-nomcom@lists.elistx.com, iab@ietf.org
Message-id: <5.1.0.14.2.20030324183332.0348ea90@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: multipart/alternative;
 boundary="Boundary_(ID_0MsaszDghq1FXt/y/FDoEQ)"
X-ELNK-Trace:
 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4d5ed58109d57c330a606ab6b00d2bb2ff350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
References: <5.1.0.14.2.20030321133351.030f5740@pop.mindspring.com>
 <5.1.0.14.2.20030323200907.00ab70d8@pop.mindspring.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


--Boundary_(ID_0MsaszDghq1FXt/y/FDoEQ)
Content-type: text/plain; format=flowed; charset=us-ascii

Let me break this down into pieces as to why I think this paragraph is 
fraught with difficulties.

At 05:37 PM 3/24/2003 +0100, Brian E Carpenter wrote:
>Well, we plain disagree. I found this paragraph perfect when chairing
>both the confirming bodies, and didn't have any issue of separation
>of function.
>
>    Brian
>
>Michael StJohns wrote:
> >
> > >If some or none of the candidates submitted to a confirming
> > >            body are confirmed, the confirming body continues to consult
> > >            with the nominating committee both

"consult" has the definition "to ask the advice or opinion of" and neither 
are appropriate forms of interaction between bodies where some check or 
balance is desired.  Confirming body: "What do you think of our decision 
not to confirm foo? "  Nomcom: "Obviously you're mistaken and you really 
should consider these additional things that we forgot to tell you 
before."  Confirming body:  "But we've already rejected him/her so what's 
the point?"

Gleaning more information about candidates prior to the "vote" or whatever 
passes for the confirmation action by the confirming body seems to make 
sense.  E.g. Confirming body to Nomcom: "Could you give us more information 
about 'foo', specifically has 'foo' ever had experience doing X?"   Doing 
this after the fact for a candidate that's already been rejected seems to 
me to be a waste of time.  The paragraph immediately after this paragraph says

            The confirming body may reject individual candidates, in
            which case the nominating committee must select alternate
            candidates for the rejected candidates.

Which is pretty clear that once the candidate is rejected they may not be 
re-proposed.

The replacement text covering this is: ""The confirming body may ask for 
additional information about a nominee  from the Nomcom to assist them in 
their deliberations."

>  to explain the reason why
> > >            all the candidates were not confirmed and

There are a number of problems with this particular phrase.  As stated it 
implies there is a frameable consensus reason a candidate or candidates did 
not get confirmed.  In reality, each member of the confirming body may have 
their reasons why they voted for or against confirmation.  That argues 
against a consensus statement of the reason the confirming body didn't 
confirm.  Absent any other information,  the assumed reason should be "The 
confirming body was unable to find a majority who agreed the candidate was 
qualified for the position." which is a factual statement rather than an 
opinion.

The second problem is that the tone seems to suggest the confirming body 
have good reason for rejecting the candidate. I believe this needs to be 
reversed - that the confirming bodies have good reason to accept the 
candidates.   If you see the policy section of my original message I 
suggest some text related to the rationale for a members vote - specifically:
"Confirmation should not be a rubber stamp of the Nomcom's selections, but 
a reasoned and reasonable consideration of the nominee's qualifications for 
the position. A vote to confirm is an affirmative action which should 
indicate the member's confidence in the ability of the nominee to 
accomplish the goals of the position and the work of the IETF."

Each group has its strengths.  The Nomcom has the charge to form its slate 
based on the best knowledge it can glean from interviews, personal 
knowledge, discussion, resumes etc.  It brings a new point of view to the 
process of finding good people.  The confirming bodies have the advantage 
of continuity, longevity, and experience in the day to day operations of 
the IETF/IESG/IAB.  They provide a needed check on the Nomcom which might 
not have the benefit of the corporate memory, especially if random 
selection seeds the Nomcom with high proportions of relative newcomers.

>to understand the
> > >            nominating committee's rationale for the slate.

Confirming bodies confirm candidates, not the slate.  Again, this type of 
inquiry is better left to the discussion before the vote rather than after 
and should be part of the charge to the Nomcom.  Section 5 subsection 14 says

        " The nominating committee advises the confirming bodies of their
         candidates, specifying a single candidate for each open position
         and testifying as to how each candidate meets the qualifications
         of an open position.

         For each candidate, the testimony must include a brief statement
         of the qualifications for the position that is being filled,
         which may be exactly the qualifications that were requested.  If
         the qualifications differ from the desired qualifications
         originally requested a brief statement explaining the difference
         must be included.

         The testimony may include either or both a brief resume of the
         candidate or a brief summary of the deliberations of the
         nominating committee."

I'd modify the first paragraph of this section slightly to include a 
requirement the nomcom describe any external factors to the qualifications 
specific to a position- e.g. not more than X new people desired, some 
security clue in general, etc.  The confirming body can of course ask for 
more information, but ask BEFORE making its decision.

>During the
> > >            course of the consultation the nominating committee may
> > >            re-examine the slate of candidates and may change it in any
> > >            way.
> >


This implies that the candidates already confirmed by the confirming body 
could be withdrawn.  I think that's a *really really really* bad idea and 
unfair to the confirmed candidates.

However, it would seem to be permissible for the nomcom to take someone who 
was just confirmed (AFTER discussing it with the confirmed candidate) and 
offer him/her as a candidate for the slot where another candidate was 
rejected.  E.g. A candidate the Nomcom considers qualified either as a Area 
A AD or an Area B AD is proposed as Area A AD and confirmed, another 
candidate is proposed as Area B AD is rejected.  The Nomcom could ask the 
confirmed Area A AD if he/she was willing to be proposed as Area B AD, 
propose him/her and in addition propose a new Area A AD.

And no, I don't think the Nomcom can do this unilaterally - once the 
candidate is confirmed, the slot is filled and the Nomcom shouldn't get to 
say "we were just kidding, we didn't mean it" regardless of what happens 
with other slots.

--Boundary_(ID_0MsaszDghq1FXt/y/FDoEQ)
Content-type: text/html; charset=us-ascii

<html>
Let me break this down into pieces as to why I think this paragraph is
fraught with difficulties.<br><br>
At 05:37 PM 3/24/2003 +0100, Brian E Carpenter wrote:<br>
<blockquote type=cite class=cite cite>Well, we plain disagree. I found
this paragraph perfect when chairing<br>
both the confirming bodies, and didn't have any issue of separation<br>
of function.<br><br>
&nbsp;&nbsp; Brian<br><br>
Michael StJohns wrote:<br>
&gt; <br>
&gt; &gt;If some or none of the candidates submitted to a 
confirming<br>
&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
body are confirmed, the confirming body continues to consult<br>
&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
with the nominating committee both</blockquote><br>
&quot;consult&quot; has the definition &quot;to ask the advice or opinion
of&quot; and neither are appropriate forms of interaction between bodies
where some check or balance is desired.&nbsp; Confirming body: &quot;What
do you think of our decision not to confirm foo? &quot;&nbsp; Nomcom:
&quot;Obviously you're mistaken and you really should consider these
additional things that we forgot to tell you before.&quot;&nbsp;
Confirming body:&nbsp; &quot;But we've already rejected him/her so what's
the point?&quot;<br><br>
Gleaning more information about candidates prior to the &quot;vote&quot;
or whatever passes for the confirmation action by the confirming body
seems to make sense.&nbsp; E.g. Confirming body to Nomcom: &quot;Could
you give us more information about 'foo', specifically has 'foo' ever had
experience doing X?&quot;&nbsp;&nbsp; Doing this after the fact for a
candidate that's already been rejected seems to me to be a waste of
time.&nbsp; The paragraph immediately after this paragraph says 
<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The
confirming body may reject individual candidates, in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; which case
the nominating committee must select alternate<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; candidates
for the rejected candidates.<br><br>
Which is pretty clear that once the candidate is rejected they may not be
re-proposed.<br><br>
The replacement text covering this is: &quot;&quot;The confirming body
may ask for additional information about a nominee&nbsp; from the Nomcom
to assist them in their deliberations.&quot;&nbsp; <br><br>
<blockquote type=cite class=cite cite>&nbsp;to explain the reason
why<br>
&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
all the candidates were not confirmed and </blockquote><br>
There are a number of problems with this particular phrase.&nbsp; As
stated it implies there is a frameable consensus reason a candidate or
candidates did not get confirmed.&nbsp; In reality, each member of the
confirming body may have their reasons why they voted for or against
confirmation.&nbsp; That argues against a consensus statement of the
reason the confirming body didn't confirm.&nbsp; Absent any other
information,&nbsp; the assumed reason should be &quot;The confirming body
was unable to find a majority who agreed the candidate was qualified for
the position.&quot; which is a factual statement rather than an
opinion.<br><br>
The second problem is that the tone seems to suggest the confirming body
have good reason for rejecting the candidate. I believe this needs to be
reversed - that the confirming bodies have good reason to accept the
candidates.&nbsp;&nbsp; If you see the policy section of my original
message I suggest some text related to the rationale for a members vote -
specifically:<br>

<dl>
<dd>&quot;Confirmation should not be a rubber stamp of the Nomcom's
selections, but a reasoned and reasonable consideration of the nominee's
qualifications for the position. A vote to confirm is an affirmative
action which should indicate the member's confidence in the ability of
the nominee to accomplish the goals of the position and the work of the
IETF.&quot;<br><br>

</dl>Each group has its strengths.&nbsp; The Nomcom has the charge to
form its slate based on the best knowledge it can glean from interviews,
personal knowledge, discussion, resumes etc.&nbsp; It brings a new point
of view to the process of finding good people.&nbsp; The confirming
bodies have the advantage of continuity, longevity, and experience in the
day to day operations of the IETF/IESG/IAB.&nbsp; They provide a needed
check on the Nomcom which might not have the benefit of the corporate
memory, especially if random selection seeds the Nomcom with high
proportions of relative newcomers.<br><br>
<blockquote type=cite class=cite cite>to understand the<br>
&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
nominating committee's rationale for the slate.&nbsp; </blockquote><br>
Confirming bodies confirm candidates, not the slate.&nbsp; Again, this
type of inquiry is better left to the discussion before the vote rather
than after and should be part of the charge to the Nomcom.&nbsp; Section
5 subsection 14 says<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot; The nominating committee
advises the confirming bodies of their<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; candidates, specifying a
single candidate for each open position<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and testifying as to how each
candidate meets the qualifications<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of an open position.<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For each candidate, the
testimony must include a brief statement<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of the qualifications for the
position that is being filled,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; which may be exactly the
qualifications that were requested.&nbsp; If<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the qualifications differ from
the desired qualifications<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; originally requested a brief
statement explaining the difference<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must be included.<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The testimony may include
either or both a brief resume of the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; candidate or a brief summary
of the deliberations of the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; nominating
committee.&quot;<br><br>
I'd modify the first paragraph of this section slightly to include a
requirement the nomcom describe any external factors to the
qualifications specific to a position- e.g. not more than X new people
desired, some security clue in general, etc.&nbsp; The confirming body
can of course ask for more information, but ask BEFORE making its
decision.<br><br>
<blockquote type=cite class=cite cite>During the<br>
&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
course of the consultation the nominating committee may<br>
&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
re-examine the slate of candidates and may change it in any<br>
&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
way.<br>
&gt; </blockquote><br><br>
This implies that the candidates already confirmed by the confirming body
could be withdrawn.&nbsp; I think that's a *really really really* bad
idea and unfair to the confirmed candidates.&nbsp; <br><br>
However, it would seem to be permissible for the nomcom to take someone
who was just confirmed (AFTER discussing it with the confirmed candidate)
and offer him/her as a candidate for the slot where another candidate was
rejected.&nbsp; E.g. A candidate the Nomcom considers qualified either as
a Area A AD or an Area B AD is proposed as Area A AD and confirmed,
another candidate is proposed as Area B AD is rejected.&nbsp; The Nomcom
could ask the confirmed Area A AD if he/she was willing to be proposed as
Area B AD, propose him/her and in addition propose a new Area A AD.&nbsp;
<br><br>
And no, I don't think the Nomcom can do this unilaterally - once the
candidate is confirmed, the slot is filled and the Nomcom shouldn't get
to say &quot;we were just kidding, we didn't mean it&quot; regardless of
what happens with other slots.</html>

--Boundary_(ID_0MsaszDghq1FXt/y/FDoEQ)--

From ietf-nomcom-errors@lists.elistx.com Tue Mar 25 12:25:02 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCB00104ETPOD@eListX.com> (original mail from brian@hursley.ibm.com)
 ; Tue, 25 Mar 2003 12:20:13 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCB00101ETOOB@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Tue,
 25 Mar 2003 12:20:13 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCB00101ETOOA@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Tue, 25 Mar 2003 12:20:12 -0500 (EST)
Received: from d12lmsgate-2.de.ibm.com
 (d12lmsgate-2.de.ibm.com [194.196.100.235])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCB0004UETNV7@eListX.com>
 for ietf-nomcom@lists.elistx.com; Tue, 25 Mar 2003 12:20:12 -0500 (EST)
Received: from d12relay01.de.ibm.com (d12relay01.de.ibm.com [9.165.215.22])
	by d12lmsgate-2.de.ibm.com (8.12.8/8.12.8) with ESMTP id h2PHJB33024304; Tue,
 25 Mar 2003 18:19:11 +0100
Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140])
	by d12relay01.de.ibm.com (8.12.8/NCO/VER6.5) with SMTP id h2PHJ9WX229028; Tue,
 25 Mar 2003 18:19:10 +0100
Received: from [9.91.16.250] by ochsehorn.zurich.ibm.com
 (AIX 4.3/UCB 5.64/4.03)          id AA52042 from <brian@hursley.ibm.com>; Tue,
 25 Mar 2003 18:19:07 +0100
Date: Tue, 25 Mar 2003 18:18:01 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Subject: Re: Notes from one member of the IAB on the current draft
To: Michael StJohns <mstjohns@mindspring.com>
Cc: ietf-nomcom@lists.elistx.com, iab@ietf.org
Message-id: <3E808F49.5374DAA3@hursley.ibm.com>
Organization: IBM
MIME-version: 1.0
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en,fr,de
References: <5.1.0.14.2.20030321133351.030f5740@pop.mindspring.com>
 <5.1.0.14.2.20030323200907.00ab70d8@pop.mindspring.com>
 <5.1.0.14.2.20030324183332.0348ea90@pop.mindspring.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Mike, I can only repeat that I simply don't see any of these aspects as problems,
except for one logical issue you point out:

> During the
>   > >            course of the consultation the nominating committee may
>   > >            re-examine the slate of candidates and may change it in any
>   > >            way.
>   > 
> 
> 
> 
> This implies that the candidates already confirmed by the confirming body could be withdrawn.  I think that's a *really
> really really* bad idea and unfair to the confirmed candidates.  

Well, all this process remains under the seal of confidentiality, so
the confirmed candidates would never know. But I agree, it would be very
bizarre to withdraw a nomination at this stage, although I can imagine
an AD nominee being renominated to a different Area or even to IETF Chair,
after the confirming body rejected a nominee. So we need a sentence
that enables NomCom to react flexibly to a rejection, without endorsing
egregious actions.

   During the course of the consultation, the nominating committee may
   adjust the slate of candidates in response to the confirming body's
   partial confirmation, by replacing the nominees who were not already
   confirmed, and in the case of the IESG, possibly by changing the positions 
   to which already confirmed candidates are appointed.

     Brian

Michael StJohns wrote:
> 
> Let me break this down into pieces as to why I think this paragraph is fraught with difficulties.
> 
> At 05:37 PM 3/24/2003 +0100, Brian E Carpenter wrote:
> 
> > Well, we plain disagree. I found this paragraph perfect when chairing
> > both the confirming bodies, and didn't have any issue of separation
> > of function.
> >
> >    Brian
> >
> > Michael StJohns wrote:
> > >
> > > >If some or none of the candidates submitted to a confirming
> > > >            body are confirmed, the confirming body continues to consult
> > > >            with the nominating committee both
> 
> "consult" has the definition "to ask the advice or opinion of" and neither are appropriate forms of interaction between bodies
> where some check or balance is desired.  Confirming body: "What do you think of our decision not to confirm foo? "  Nomcom:
> "Obviously you're mistaken and you really should consider these additional things that we forgot to tell you before."
> Confirming body:  "But we've already rejected him/her so what's the point?"
> 
> Gleaning more information about candidates prior to the "vote" or whatever passes for the confirmation action by the
> confirming body seems to make sense.  E.g. Confirming body to Nomcom: "Could you give us more information about 'foo',
> specifically has 'foo' ever had experience doing X?"   Doing this after the fact for a candidate that's already been rejected
> seems to me to be a waste of time.  The paragraph immediately after this paragraph says
> 
>            The confirming body may reject individual candidates, in
>            which case the nominating committee must select alternate
>            candidates for the rejected candidates.
> 
> Which is pretty clear that once the candidate is rejected they may not be re-proposed.
> 
> The replacement text covering this is: ""The confirming body may ask for additional information about a nominee  from the
> Nomcom to assist them in their deliberations."
> 
> >  to explain the reason why
> > > >            all the candidates were not confirmed and
> 
> There are a number of problems with this particular phrase.  As stated it implies there is a frameable consensus reason a
> candidate or candidates did not get confirmed.  In reality, each member of the confirming body may have their reasons why they
> voted for or against confirmation.  That argues against a consensus statement of the reason the confirming body didn't
> confirm.  Absent any other information,  the assumed reason should be "The confirming body was unable to find a majority who
> agreed the candidate was qualified for the position." which is a factual statement rather than an opinion.
> 
> The second problem is that the tone seems to suggest the confirming body have good reason for rejecting the candidate. I
> believe this needs to be reversed - that the confirming bodies have good reason to accept the candidates.   If you see the
> policy section of my original message I suggest some text related to the rationale for a members vote - specifically:
> 
>      "Confirmation should not be a rubber stamp of the Nomcom's selections, but a reasoned and reasonable consideration of the
>      nominee's qualifications for the position. A vote to confirm is an affirmative action which should indicate the member's
>      confidence in the ability of the nominee to accomplish the goals of the position and the work of the IETF."
> 
> Each group has its strengths.  The Nomcom has the charge to form its slate based on the best knowledge it can glean from
> interviews, personal knowledge, discussion, resumes etc.  It brings a new point of view to the process of finding good
> people.  The confirming bodies have the advantage of continuity, longevity, and experience in the day to day operations of the
> IETF/IESG/IAB.  They provide a needed check on the Nomcom which might not have the benefit of the corporate memory, especially
> if random selection seeds the Nomcom with high proportions of relative newcomers.
> 
> > to understand the
> > > >            nominating committee's rationale for the slate.
> 
> Confirming bodies confirm candidates, not the slate.  Again, this type of inquiry is better left to the discussion before the
> vote rather than after and should be part of the charge to the Nomcom.  Section 5 subsection 14 says
> 
>        " The nominating committee advises the confirming bodies of their
>         candidates, specifying a single candidate for each open position
>         and testifying as to how each candidate meets the qualifications
>         of an open position.
> 
>         For each candidate, the testimony must include a brief statement
>         of the qualifications for the position that is being filled,
>         which may be exactly the qualifications that were requested.  If
>         the qualifications differ from the desired qualifications
>         originally requested a brief statement explaining the difference
>         must be included.
> 
>         The testimony may include either or both a brief resume of the
>         candidate or a brief summary of the deliberations of the
>         nominating committee."
> 
> I'd modify the first paragraph of this section slightly to include a requirement the nomcom describe any external factors to
> the qualifications specific to a position- e.g. not more than X new people desired, some security clue in general, etc.  The
> confirming body can of course ask for more information, but ask BEFORE making its decision.
> 
> > During the
> > > >            course of the consultation the nominating committee may
> > > >            re-examine the slate of candidates and may change it in any
> > > >            way.
> > >
> 
> This implies that the candidates already confirmed by the confirming body could be withdrawn.  I think that's a *really really
> really* bad idea and unfair to the confirmed candidates.
> 
> However, it would seem to be permissible for the nomcom to take someone who was just confirmed (AFTER discussing it with the
> confirmed candidate) and offer him/her as a candidate for the slot where another candidate was rejected.  E.g. A candidate the
> Nomcom considers qualified either as a Area A AD or an Area B AD is proposed as Area A AD and confirmed, another candidate is
> proposed as Area B AD is rejected.  The Nomcom could ask the confirmed Area A AD if he/she was willing to be proposed as Area
> B AD, propose him/her and in addition propose a new Area A AD.
> 
> And no, I don't think the Nomcom can do this unilaterally - once the candidate is confirmed, the slot is filled and the Nomcom
> shouldn't get to say "we were just kidding, we didn't mean it" regardless of what happens with other slots.

From ietf-nomcom-errors@lists.elistx.com Tue Mar 25 13:15:02 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCB00304HBDR7@eListX.com> (original mail from mstjohns@mindspring.com)
 ; Tue, 25 Mar 2003 13:14:01 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCB00301HBCR5@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Tue,
 25 Mar 2003 13:14:00 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCB00301HBCR4@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Tue, 25 Mar 2003 13:14:00 -0500 (EST)
Received: from blount.mail.mindspring.net
 (blount.mail.mindspring.net [207.69.200.226])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCB000GNHBBV7@eListX.com>
 for ietf-nomcom@lists.elistx.com; Tue, 25 Mar 2003 13:14:00 -0500 (EST)
Received: from [192.168.167.42] (helo=wamui04.slb.atl.earthlink.net)
	by blount.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 18xsv0-00061X-00; Tue, 25 Mar 2003 13:13:02 -0500
Received: from [192.168.167.60] by EarthlinkWAM via HTTP; Tue Mar 25 13:13:02
 EST 2003
Date: Tue, 25 Mar 2003 13:12:54 -0500 (GMT)
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Re: Notes from one member of the IAB on the current draft
To: Brian E Carpenter <brian@hursley.ibm.com>,
 Michael StJohns <mstjohns@mindspring.com>
Cc: ietf-nomcom@lists.elistx.com, iab@ietf.org
Message-id:
 <7309347.1048615982203.JavaMail.nobody@wamui04.slb.atl.earthlink.net>
MIME-version: 1.0
X-Mailer: Earthlink Web Access Mail version 3.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Hi Brian -

I appreciate that you disagree, but you haven't provided any reasoning
behind your thoughts so its difficult for me to make any further comment. 
I've supported my thoughts, it would be helpful to me and probably to others
if you would provide more detail than that you simply disagree.

See below for a comment on the specific item you commented on.

-------Original Message-------
From: Brian E Carpenter <brian@hursley.ibm.com>
Sent: 03/25/03 12:18 PM
To: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Notes from one member of the IAB on the current draft

> 
> Mike, I can only repeat that I simply don't see any of these aspects as
problems,
except for one logical issue you point out:

> During the
>   > >            course of the consultation the nominating committee may
>   > >            re-examine the slate of candidates and may change it in 

any
>   > >            way.
>   > 
> 
> 
> 
> This implies that the candidates already confirmed by the confirming
body could be withdrawn.  I think that's a *really
> really really* bad idea and unfair to the confirmed candidates.  

Well, all this process remains under the seal of confidentiality, so
the confirmed candidates would never know. But I agree, it would be very
bizarre to withdraw a nomination at this stage, although I can imagine
an AD nominee being renominated to a different Area or even to IETF Chair,
after the confirming body rejected a nominee. So we need a sentence
that enables NomCom to react flexibly to a rejection, without endorsing
egregious actions.

   During the course of the consultation, the nominating committee may
   adjust the slate of candidates in response to the confirming body's
   partial confirmation, by replacing the nominees who were not already
   confirmed, and in the case of the IESG, possibly by changing the
positions 
   to which already confirmed candidates are appointed.

     Brian


This is actually already in the text in other places - in fact in the
paragraph following the one referenced.  And I repeat - it is not and should
not be a consultive communication - the confirming body should be free to
deliberate without undue influence from the Nomcom.  The confirming body
should be free to seek information, it should not be soliciting opinion from the 
Nomcom past that implied by the submission of the particular candidate.

From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 01:25:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCL00D04O38WH@eListX.com> (original mail from brian@hursley.ibm.com)
 ; Mon, 31 Mar 2003 01:16:20 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCL00D01O37WD@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 01:16:19 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCL00D01O37WB@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 01:16:19 -0500 (EST)
Received: from d12lmsgate.de.ibm.com (d12lmsgate.de.ibm.com [194.196.100.234])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCL00LH6O366K@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 01:16:19 -0500 (EST)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate.de.ibm.com (8.12.8/8.12.3) with ESMTP id h2V6F8So129820; Mon,
 31 Mar 2003 08:15:08 +0200
Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140])
	by d12relay02.de.ibm.com (8.12.8/NCO/VER6.5) with SMTP id h2V6F8kp254236; Mon,
 31 Mar 2003 08:15:09 +0200
Received: from dhcp21-82.zurich.ibm.com by ochsehorn.zurich.ibm.com
 (AIX 4.3/UCB 5.64/4.03)          id AA29872 from <brian@hursley.ibm.com>; Mon,
 31 Mar 2003 08:15:08 +0200
Date: Fri, 28 Mar 2003 22:04:42 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Subject: Re: Notes from one member of the IAB on the current draft
To: Michael StJohns <mstjohns@mindspring.com>
Cc: ietf-nomcom@lists.elistx.com, iab@ietf.org
Message-id: <3E84B8EA.BE2908DB@hursley.ibm.com>
Organization: IBM
MIME-version: 1.0
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en,fr,de
References:
 <7309347.1048615982203.JavaMail.nobody@wamui04.slb.atl.earthlink.net>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

I took a few days off from this thread to pay attention to my day job...

Michael StJohns wrote:
> 
> Hi Brian -
> 
> I appreciate that you disagree, but you haven't provided any reasoning
> behind your thoughts so its difficult for me to make any further comment.
> I've supported my thoughts, it would be helpful to me and probably to others
> if you would provide more detail than that you simply disagree.
> 
> See below for a comment on the specific item you commented on.
> 
> -------Original Message-------
> From: Brian E Carpenter <brian@hursley.ibm.com>
> Sent: 03/25/03 12:18 PM
> To: Michael StJohns <mstjohns@mindspring.com>
> Subject: Re: Notes from one member of the IAB on the current draft
> 
> >
> > Mike, I can only repeat that I simply don't see any of these aspects as
> problems,
> except for one logical issue you point out:
> 
> > During the
> >   > >            course of the consultation the nominating committee may
> >   > >            re-examine the slate of candidates and may change it in
> 
> any
> >   > >            way.
> >   >
> >
> >
> >
> > This implies that the candidates already confirmed by the confirming
> body could be withdrawn.  I think that's a *really
> > really really* bad idea and unfair to the confirmed candidates.
> 
> Well, all this process remains under the seal of confidentiality, so
> the confirmed candidates would never know. But I agree, it would be very
> bizarre to withdraw a nomination at this stage, although I can imagine
> an AD nominee being renominated to a different Area or even to IETF Chair,
> after the confirming body rejected a nominee. So we need a sentence
> that enables NomCom to react flexibly to a rejection, without endorsing
> egregious actions.
> 
>    During the course of the consultation, the nominating committee may
>    adjust the slate of candidates in response to the confirming body's
>    partial confirmation, by replacing the nominees who were not already
>    confirmed, and in the case of the IESG, possibly by changing the
> positions
>    to which already confirmed candidates are appointed.
> 
>      Brian
> 
> This is actually already in the text in other places - in fact in the
> paragraph following the one referenced.  And I repeat - it is not and should
> not be a consultive communication - the confirming body should be free to
> deliberate without undue influence from the Nomcom.  The confirming body
> should be free to seek information, it should not be soliciting opinion from the
> Nomcom past that implied by the submission of the particular candidate.

OK, you are bothered by the word "consult" in a way that I'm not. I would
certainly agree to a more neutral word such as "communicate". In the cases 
where I've been involved, the communication has in fact been interrogatory
(i.e. the confirming body asks the NomCom "Did you consider issue X when 
choosing nominee Y?" or "Did you seek an opinion about nominee Y from 
source Z?").

Now let me try to be constructive. How would you find this as a 
replacement for section 3, paragraph 7 sub paragraph 3 paragraph 
beginning "If some or none..." ?

  If not all the candidates submitted to a confirming body are 
  rapidly confirmed, the confirming body continues to communicate
  with the nominating committee both to understand the committee's 
  rationale for the slate and, if appropriate, to explain the reason 
  why all the candidates were not confirmed.  

  The confirming body may ask the nominating committee for additional 
  information about a nominee, or about the nominating committee's procedure,
  to assist them in their deliberations. However, the confirming body 
  and the nominating committee must refrain from mutual communication
  about availability, qualification or characteristics of other possible
  candidates for the position.

Then extend the following paragraph to become:

  The confirming body may reject individual candidates, in
  which case the nominating committee must select alternate
  candidates for the rejected candidates, and in the case of 
  the IESG, may possibly change the positions to which already 
  confirmed candidates are appointed.

     Brian



From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 03:35:08 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCL00H04U7132@eListX.com> (original mail from jwkckid1@ix.netcom.com)
 ; Mon, 31 Mar 2003 03:28:13 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCL00H01U7030@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 03:28:12 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCL00H01U702Z@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 03:28:12 -0500 (EST)
Received: from mclean.mail.mindspring.net
 (mclean.mail.mindspring.net [207.69.200.57])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCL00LK0U6Z6K@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 03:28:12 -0500 (EST)
Received: from dialup-64.157.113.105.dial1.dallas1.level3.net
 ([64.157.113.105] helo=ix.netcom.com)	by mclean.mail.mindspring.net with esmtp
 (Exim 3.33 #1)	id 18zudI-0003cU-00; Mon, 31 Mar 2003 03:27:08 -0500
Date: Mon, 31 Mar 2003 02:26:32 -0800
From: Jeff Williams <jwkckid1@ix.netcom.com>
Subject: Re: Notes from one member of the IAB on the current draft
To: Brian E Carpenter <brian@hursley.ibm.com>
Cc: Michael StJohns <mstjohns@mindspring.com>, ietf-nomcom@lists.elistx.com,
 iab@ietf.org
Message-id: <3E8817D7.7DB6FCDD@ix.netcom.com>
Organization: INEGroup Spokesman
MIME-version: 1.0
X-Mailer: Mozilla 4.08 [en] (Win95; U; 16bit)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References:
 <7309347.1048615982203.JavaMail.nobody@wamui04.slb.atl.earthlink.net>
 <3E84B8EA.BE2908DB@hursley.ibm.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Brian and all,

  I also have a problem with the term "Consult" in the context in which it
was used.  I would also suggest that everyone ask themselves why
would source "z", as you use it here Brian, have any importance with
consideration "x" and/or "y" ?  And secondly, isn't the consideration
"x" or "y" the important thing, not the source of those or any other
consideration being brought up?

Brian E Carpenter wrote:

> I took a few days off from this thread to pay attention to my day job...
>
> Michael StJohns wrote:
> >
> > Hi Brian -
> >
> > I appreciate that you disagree, but you haven't provided any reasoning
> > behind your thoughts so its difficult for me to make any further comment.
> > I've supported my thoughts, it would be helpful to me and probably to others
> > if you would provide more detail than that you simply disagree.
> >
> > See below for a comment on the specific item you commented on.
> >
> > -------Original Message-------
> > From: Brian E Carpenter <brian@hursley.ibm.com>
> > Sent: 03/25/03 12:18 PM
> > To: Michael StJohns <mstjohns@mindspring.com>
> > Subject: Re: Notes from one member of the IAB on the current draft
> >
> > >
> > > Mike, I can only repeat that I simply don't see any of these aspects as
> > problems,
> > except for one logical issue you point out:
> >
> > > During the
> > >   > >            course of the consultation the nominating committee may
> > >   > >            re-examine the slate of candidates and may change it in
> >
> > any
> > >   > >            way.
> > >   >
> > >
> > >
> > >
> > > This implies that the candidates already confirmed by the confirming
> > body could be withdrawn.  I think that's a *really
> > > really really* bad idea and unfair to the confirmed candidates.
> >
> > Well, all this process remains under the seal of confidentiality, so
> > the confirmed candidates would never know. But I agree, it would be very
> > bizarre to withdraw a nomination at this stage, although I can imagine
> > an AD nominee being renominated to a different Area or even to IETF Chair,
> > after the confirming body rejected a nominee. So we need a sentence
> > that enables NomCom to react flexibly to a rejection, without endorsing
> > egregious actions.
> >
> >    During the course of the consultation, the nominating committee may
> >    adjust the slate of candidates in response to the confirming body's
> >    partial confirmation, by replacing the nominees who were not already
> >    confirmed, and in the case of the IESG, possibly by changing the
> > positions
> >    to which already confirmed candidates are appointed.
> >
> >      Brian
> >
> > This is actually already in the text in other places - in fact in the
> > paragraph following the one referenced.  And I repeat - it is not and should
> > not be a consultive communication - the confirming body should be free to
> > deliberate without undue influence from the Nomcom.  The confirming body
> > should be free to seek information, it should not be soliciting opinion from the
> > Nomcom past that implied by the submission of the particular candidate.
>
> OK, you are bothered by the word "consult" in a way that I'm not. I would
> certainly agree to a more neutral word such as "communicate". In the cases
> where I've been involved, the communication has in fact been interrogatory
> (i.e. the confirming body asks the NomCom "Did you consider issue X when
> choosing nominee Y?" or "Did you seek an opinion about nominee Y from
> source Z?").
>
> Now let me try to be constructive. How would you find this as a
> replacement for section 3, paragraph 7 sub paragraph 3 paragraph
> beginning "If some or none..." ?
>
>   If not all the candidates submitted to a confirming body are
>   rapidly confirmed, the confirming body continues to communicate
>   with the nominating committee both to understand the committee's
>   rationale for the slate and, if appropriate, to explain the reason
>   why all the candidates were not confirmed.
>
>   The confirming body may ask the nominating committee for additional
>   information about a nominee, or about the nominating committee's procedure,
>   to assist them in their deliberations. However, the confirming body
>   and the nominating committee must refrain from mutual communication
>   about availability, qualification or characteristics of other possible
>   candidates for the position.
>
> Then extend the following paragraph to become:
>
>   The confirming body may reject individual candidates, in
>   which case the nominating committee must select alternate
>   candidates for the rejected candidates, and in the case of
>   the IESG, may possibly change the positions to which already
>   confirmed candidates are appointed.
>
>      Brian
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.elistx.com/subscribe>

Regards,
--
Jeffrey A. Williams
Spokesman for INEGroup LLA. - (Over 129k members/stakeholders strong!)
================================================================
CEO/DIR. Internet Network Eng. SR. Eng. Network data security
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number: 214-244-4827 or 214-244-3801



From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 10:25:17 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCM00604D6PNU@eListX.com> (original mail from mstjohns@mindspring.com)
 ; Mon, 31 Mar 2003 10:18:25 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCM00601D6NNQ@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 10:18:25 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCM00601D6NNP@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 10:18:23 -0500 (EST)
Received: from sentry.gw.tislabs.com (sentry.gw.tislabs.com [192.94.214.100])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCM003CQD6MDF@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 10:18:22 -0500 (EST)
Received: by sentry.gw.tislabs.com; id KAA22454; Mon,
 31 Mar 2003 10:18:14 -0500 (EST)
Received: from dyn083.gw.tislabs.com(10.33.10.83) by sentry.gw.tislabs.com via
 smap (V5.5)	id xma022449; Mon, 31 Mar 2003 10:17:17 -0500
Date: Mon, 31 Mar 2003 10:16:09 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Notes from one member of the IAB on the current draft
In-reply-to: <3E84B8EA.BE2908DB@hursley.ibm.com>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: Brian E Carpenter <brian@hursley.ibm.com>
Cc: ietf-nomcom@lists.elistx.com, iab@ietf.org
Message-id: <5.1.0.14.2.20030331093500.05d65680@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: multipart/alternative;
 boundary="Boundary_(ID_X08sjDbw6asYPoqv4XNcyQ)"
References:
 <7309347.1048615982203.JavaMail.nobody@wamui04.slb.atl.earthlink.net>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


--Boundary_(ID_X08sjDbw6asYPoqv4XNcyQ)
Content-type: text/plain; format=flowed; charset=us-ascii

At 10:04 PM 3/28/2003 +0100, Brian E Carpenter wrote:
>I took a few days off from this thread to pay attention to my day job...
>
>Michael StJohns wrote:
> > >
> > > This implies that the candidates already confirmed by the confirming
> > body could be withdrawn.  I think that's a *really
> > > really really* bad idea and unfair to the confirmed candidates.
> >
> > Well, all this process remains under the seal of confidentiality, so
> > the confirmed candidates would never know.

Sorry to go back to this, but should have commented before.  Its actually 
important to your current submission.

"... confirmed candidates would never know." Except in the case that the 
IAB is considering an IESG where a current IAB member has been 
submitted.  The IAB member is disqualified from participating in their own 
confirmation, but not in others. Current practice generally has the 
confirmation or rejection of the IAB IESG candidate first, and then 
bringing in that IAB member to consider the rest of the candidates and 
positions.  There are other reasons related to process deadlock why this is 
a bad idea which we can get in to if necessary.


>But I agree, it would be very
> > bizarre to withdraw a nomination at this stage, although I can imagine
> > an AD nominee being renominated to a different Area or even to IETF Chair,
> > after the confirming body rejected a nominee.

As can I, but I stress that its not the Nomcom's choice to summarily 
reverse a previous confirmation.  See my previous comments on how to 
equitably handle this issue.  It shouldn't take more than a day for the 
Nomcom to ASK the confirmee if they're willing to be moved once they've 
been confirmed.

>So we need a sentence
> > that enables NomCom to react flexibly to a rejection, without endorsing
> > egregious actions.
> >
> >    During the course of the consultation, the nominating committee may
> >    adjust the slate of candidates in response to the confirming body's
> >    partial confirmation, by replacing the nominees who were not already
> >    confirmed, and in the case of the IESG, possibly by changing the
> > positions
> >    to which already confirmed candidates are appointed.
> >
> >      Brian
> >
> > This is actually already in the text in other places - in fact in the
> > paragraph following the one referenced.  And I repeat - it is not and 
> should
> > not be a consultive communication - the confirming body should be free to
> > deliberate without undue influence from the Nomcom.  The confirming body
> > should be free to seek information, it should not be soliciting opinion 
> from the
> > Nomcom past that implied by the submission of the particular candidate.
>
>OK, you are bothered by the word "consult" in a way that I'm not. I would
>certainly agree to a more neutral word such as "communicate". In the cases
>where I've been involved, the communication has in fact been interrogatory
>(i.e. the confirming body asks the NomCom "Did you consider issue X when
>choosing nominee Y?" or "Did you seek an opinion about nominee Y from
>source Z?").

And those are questions of fact, not of opinion.   Also, I'm not looking 
for neutral, I'm looking for accurate.  "Communicate" is at least 
non-egregious, and probably accurate enough for this.

>Now let me try to be constructive. How would you find this as a
>replacement for section 3, paragraph 7 sub paragraph 3 paragraph
>beginning "If some or none..." ?
>
>   If not all the candidates submitted to a confirming body are
>   rapidly

Where did "rapidly" come from?  Remove.  Once the slate is handed to the 
confirming body, the Nomcom is out of the loop until the confirming body 
responds.  As stated, implies that the Nomcom gets to start prodding the 
confirming body.  The prodding if any should probably come from the IESG 
Secretary?

Also, the type of communication we're talking about more appropriately 
happens BEFORE the confirming body actually makes a decision.



>confirmed, the confirming body



>  continues to communicate

"may communicate" - continues to communicate implies that it was already 
having a dialog, and also that such communication is mandatory on the part 
of the confirming body.  The confirming body may believe, with good 
justification, that it has all necessary information it needs.

>   with the nominating committee both to understand the committee's
>   rationale for the slate

See below.

>  and, if appropriate, to explain the reason
>   why all the candidates were not confirmed.



So replace this with
"During the course of its deliberations, the confirming body may 
communicate with the nominating committee to understand the committee's 
rationale for the slate, and the rationale for any specific nominee.  If 
the confirming body chooses not to confirm one or more candidates, it is 
appropriate and helpful, but not mandatory,  for the confirming body to 
provide a brief explanation to the nominating committee of the reasoning 
behind the failure to confirm to assist the nominating committee in its 
selection of an alternate."



>   The confirming body may ask the nominating committee for additional
>   information about a nominee, or about the nominating committee's procedure,
>   to assist them in their deliberations. However, the confirming body
>   and the nominating committee must refrain from mutual communication
>   about availability, qualification or characteristics of other possible
>   candidates for the position.

Yup.

>Then extend the following paragraph to become:



>   The confirming body may reject individual candidates, in
>   which case the nominating committee must select alternate
>   candidates for the rejected candidates,

Yup.

>and in the case of
>   the IESG, may possibly change the positions to which already
>   confirmed candidates are appointed.

NO.  For all the reasons I've stated before.  There is no reason the Nomcom 
can't ASK a selectee if they'll give up their position, but they don't get 
to do it unilaterally.   Also, as stated implies that the nomcom can take 
any confirmee and stick them in any slot without further reference to the 
confirming body.



>      Brian


Obviously, if any of this makes it in its going to require at least one 
editing pass to make sure it all works together.

Later, Mike


--Boundary_(ID_X08sjDbw6asYPoqv4XNcyQ)
Content-type: text/html; charset=us-ascii

<html>
At 10:04 PM 3/28/2003 +0100, Brian E Carpenter wrote:<br>
<blockquote type=cite class=cite cite>I took a few days off from this
thread to pay attention to my day job...<br><br>
Michael StJohns wrote:<br>
&gt; &gt;<br>
&gt; &gt; This implies that the candidates already confirmed by the
confirming<br>
&gt; body could be withdrawn.&nbsp; I think that's a *really<br>
&gt; &gt; really really* bad idea and unfair to the confirmed
candidates.<br>
&gt; <br>
&gt; Well, all this process remains under the seal of confidentiality,
so<br>
&gt; the confirmed candidates would never know. </blockquote><br>
Sorry to go back to this, but should have commented before.&nbsp; Its
actually important to your current submission.<br><br>
&quot;... confirmed candidates would never know.&quot; Except in the case
that the IAB is considering an IESG where a current IAB member has been
submitted.&nbsp; The IAB member is disqualified from participating in
their own confirmation, but not in others. Current practice generally has
the confirmation or rejection of the IAB IESG candidate first, and then
bringing in that IAB member to consider the rest of the candidates and
positions.&nbsp; There are other reasons related to process deadlock why
this is a bad idea which we can get in to if necessary.<br><br>
<br>
<blockquote type=cite class=cite cite>But I agree, it would be very<br>
&gt; bizarre to withdraw a nomination at this stage, although I can
imagine<br>
&gt; an AD nominee being renominated to a different Area or even to IETF
Chair,<br>
&gt; after the confirming body rejected a nominee.</blockquote><br>
As can I, but I stress that its not the Nomcom's choice to summarily
reverse a previous confirmation.&nbsp; See my previous comments on how to
equitably handle this issue.&nbsp; It shouldn't take more than a day for
the Nomcom to ASK the confirmee if they're willing to be moved once
they've been confirmed.<br><br>
<blockquote type=cite class=cite cite>So we need a sentence<br>
&gt; that enables NomCom to react flexibly to a rejection, without
endorsing<br>
&gt; egregious actions.<br>
&gt; <br>
&gt;&nbsp;&nbsp;&nbsp; During the course of the consultation, the
nominating committee may<br>
&gt;&nbsp;&nbsp;&nbsp; adjust the slate of candidates in response to the
confirming body's<br>
&gt;&nbsp;&nbsp;&nbsp; partial confirmation, by replacing the nominees
who were not already<br>
&gt;&nbsp;&nbsp;&nbsp; confirmed, and in the case of the IESG, possibly
by changing the<br>
&gt; positions<br>
&gt;&nbsp;&nbsp;&nbsp; to which already confirmed candidates are
appointed.<br>
&gt; <br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Brian<br>
&gt; <br>
&gt; This is actually already in the text in other places - in fact in
the<br>
&gt; paragraph following the one referenced.&nbsp; And I repeat - it is
not and should<br>
&gt; not be a consultive communication - the confirming body should be
free to<br>
&gt; deliberate without undue influence from the Nomcom.&nbsp; The
confirming body<br>
&gt; should be free to seek information, it should not be soliciting
opinion from the<br>
&gt; Nomcom past that implied by the submission of the particular
candidate.<br><br>
OK, you are bothered by the word &quot;consult&quot; in a way that I'm
not. I would<br>
certainly agree to a more neutral word such as &quot;communicate&quot;.
In the cases <br>
where I've been involved, the communication has in fact been
interrogatory<br>
(i.e. the confirming body asks the NomCom &quot;Did you consider issue X
when <br>
choosing nominee Y?&quot; or &quot;Did you seek an opinion about nominee
Y from <br>
source Z?&quot;).</blockquote><br>
And those are questions of fact, not of opinion.&nbsp;&nbsp; Also, I'm
not looking for neutral, I'm looking for accurate.&nbsp;
&quot;Communicate&quot; is at least non-egregious, and probably accurate
enough for this.<br><br>
<blockquote type=cite class=cite cite>Now let me try to be constructive.
How would you find this as a <br>
replacement for section 3, paragraph 7 sub paragraph 3 paragraph <br>
beginning &quot;If some or none...&quot; ?<br><br>
&nbsp; If not all the candidates submitted to a confirming body are 
<br>
&nbsp; rapidly </blockquote><br>
Where did &quot;rapidly&quot; come from?&nbsp; Remove.&nbsp; Once the
slate is handed to the confirming body, the Nomcom is out of the loop
until the confirming body responds.&nbsp; As stated, implies that the
Nomcom gets to start prodding the confirming body.&nbsp; The prodding if
any should probably come from the IESG Secretary?<br><br>
Also, the type of communication we're talking about more appropriately
happens BEFORE the confirming body actually makes a decision.&nbsp;
<br><br>
<br><br>
<blockquote type=cite class=cite cite>confirmed, the confirming
body</blockquote><br><br>
<br>
<blockquote type=cite class=cite cite>&nbsp;continues to
communicate</blockquote><br>
&quot;may communicate&quot; - continues to communicate implies that it
was already having a dialog, and also that such communication is
mandatory on the part of the confirming body.&nbsp; The confirming body
may believe, with good justification, that it has all necessary
information it needs.<br><br>
<blockquote type=cite class=cite cite>&nbsp; with the nominating
committee both to understand the committee's <br>
&nbsp; rationale for the slate</blockquote><br>
See below.<br><br>
<blockquote type=cite class=cite cite>&nbsp;and, if appropriate, to
explain the reason <br>
&nbsp; why all the candidates were not confirmed.&nbsp;
</blockquote><br><br>
<br>
So replace this with <br>

<dl>
<dd>&quot;During the course of its deliberations, the confirming body may
communicate with the nominating committee to understand the committee's
rationale for the slate, and the rationale for any specific
nominee.&nbsp; If the confirming body chooses not to confirm one or more
candidates, it is appropriate and helpful, but not mandatory,&nbsp; for
the confirming body to provide a brief explanation to the nominating
committee of the reasoning behind the failure to confirm to assist the
nominating committee in its selection of an alternate.&quot;<br><br>
<br><br>
<blockquote type=cite class=cite cite>
</dl>&nbsp; The confirming body may ask the nominating committee for
additional <br>
&nbsp; information about a nominee, or about the nominating committee's
procedure,<br>
&nbsp; to assist them in their deliberations. However, the confirming
body <br>
&nbsp; and the nominating committee must refrain from mutual
communication<br>
&nbsp; about availability, qualification or characteristics of other
possible<br>
&nbsp; candidates for the position.</blockquote><br>
Yup.<br><br>
<blockquote type=cite class=cite cite>Then extend the following paragraph
to become:</blockquote><br><br>
<br>
<blockquote type=cite class=cite cite>&nbsp; The confirming body may
reject individual candidates, in<br>
&nbsp; which case the nominating committee must select alternate<br>
&nbsp; candidates for the rejected candidates, </blockquote><br>
Yup.<br><br>
<blockquote type=cite class=cite cite>and in the case of <br>
&nbsp; the IESG, may possibly change the positions to which already 
<br>
&nbsp; confirmed candidates are appointed.</blockquote><br>
NO.&nbsp; For all the reasons I've stated before.&nbsp; There is no
reason the Nomcom can't ASK a selectee if they'll give up their position,
but they don't get to do it unilaterally.&nbsp;&nbsp; Also, as stated
implies that the nomcom can take any confirmee and stick them in any slot
without further reference to the confirming body.&nbsp; <br><br>
<br><br>
<blockquote type=cite class=cite cite>&nbsp;&nbsp;&nbsp;&nbsp;
Brian</blockquote><br><br>
Obviously, if any of this makes it in its going to require at least one
editing pass to make sure it all works together.<br><br>
Later, Mike<br><br>
</html>

--Boundary_(ID_X08sjDbw6asYPoqv4XNcyQ)--

From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 10:35:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCM00704DNO5L@eListX.com> (original mail from mstjohns@mindspring.com)
 ; Mon, 31 Mar 2003 10:28:36 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCM00701DNN5D@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 10:28:35 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCM00701DNM55@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 10:28:34 -0500 (EST)
Received: from sentry.gw.tislabs.com (sentry.gw.tislabs.com [192.94.214.100])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCM003EMDNKDF@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 10:28:33 -0500 (EST)
Received: by sentry.gw.tislabs.com; id KAA22760; Mon,
 31 Mar 2003 10:28:25 -0500 (EST)
Received: from dyn083.gw.tislabs.com(10.33.10.83) by sentry.gw.tislabs.com via
 smap (V5.5)	id xma022728; Mon, 31 Mar 2003 10:28:10 -0500
Date: Mon, 31 Mar 2003 10:27:03 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Notes from one member of the IAB on the current draft
In-reply-to: <3E8817D7.7DB6FCDD@ix.netcom.com>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: Jeff Williams <jwkckid1@ix.netcom.com>,
 Brian E Carpenter <brian@hursley.ibm.com>
Cc: ietf-nomcom@lists.elistx.com, iab@ietf.org
Message-id: <5.1.0.14.2.20030331101629.05d499e8@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: text/plain; format=flowed; charset=us-ascii
References:
 <7309347.1048615982203.JavaMail.nobody@wamui04.slb.atl.earthlink.net>
 <3E84B8EA.BE2908DB@hursley.ibm.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

At 02:26 AM 3/31/2003 -0800, Jeff Williams wrote:
>Brian and all,
>
>   I also have a problem with the term "Consult" in the context in which it
>was used.  I would also suggest that everyone ask themselves why
>would source "z", as you use it here Brian, have any importance with
>consideration "x" and/or "y" ?  And secondly, isn't the consideration
>"x" or "y" the important thing, not the source of those or any other
>consideration being brought up?

Hi Jeff -

Actually, questions of the form "Did you ask the co-area AD about this 
candidate who could become the other area AD?" are common and actually 
useful.   The ADs have to work together and, in most cases, have a pretty 
good understanding of the area, the job requirements, and the qualification 
of reasonable candidates. Other similar questions get asked of folks in the 
area, or in key working groups within the area.  Understanding that the 
nomcom did do these inquiries is a reasonable way of validating the process 
as described actually happened.

Questions of the form "did you consider issue x when nominating y" mostly 
take the form of "Does y have any experience dealing with x?" where x might 
be security, wireless, multicast, operations, etc.  E.g. "You were told to 
look for a security AD with operational clue, but it wasn't clear from the 
resume that your selectee had such clue - could you elaborate on Y's 
experience in operations?"  Again helpful if the written materials aren't 
clear.

Note - these are just example questions, and aren't representative of what 
actually happened this year or any other.

Mike


From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 11:25:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCM00904G6N7U@eListX.com> (original mail from PRoberts@MEGISTO.com); Mon,
 31 Mar 2003 11:23:12 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCM00901G6L7Q@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 11:23:11 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCM00901G6L7P@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 11:23:09 -0500 (EST)
Received: from megisto-sql1.megisto.com ([63.113.114.132])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCM003MJG6KDF@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 11:23:09 -0500 (EST)
Received: by megisto-sql1 with Internet Mail Service (5.5.2653.19)
	id <H5RMT1GD>; Mon, 31 Mar 2003 11:16:12 -0500
Content-return: allowed
Date: Mon, 31 Mar 2003 11:16:11 -0500
From: Phil Roberts <PRoberts@MEGISTO.com>
Subject: RE: Notes from one member of the IAB on the current draft
To: 'Michael StJohns' <mstjohns@mindspring.com>,
 Brian E Carpenter <brian@hursley.ibm.com>
Cc: ietf-nomcom@lists.elistx.com, iab@ietf.org
Message-id: <C3F7A1AD0781F84784B5528466CA09DD7DD598@megisto-sql1>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_2ct7y0gYa6aB4jFdNIAT+A)"
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--Boundary_(ID_2ct7y0gYa6aB4jFdNIAT+A)
Content-type: text/plain


Michael StJohns wrote:
> >
> > This implies that the candidates already confirmed by the confirming
> body could be withdrawn.  I think that's a *really
> > really really* bad idea and unfair to the confirmed candidates.
> 
> Well, all this process remains under the seal of confidentiality, so
> the confirmed candidates would never know. 


Sorry to go back to this, but should have commented before.  Its actually
important to your current submission.

"... confirmed candidates would never know." Except in the case that the IAB
is considering an IESG where a current IAB member has been submitted.  The
IAB member is disqualified from participating in their own confirmation, but
not in others. Current practice generally has the confirmation or rejection
of the IAB IESG candidate first, and then bringing in that IAB member to
consider the rest of the candidates and positions.  There are other reasons
related to process deadlock why this is a bad idea which we can get in to if
necessary.




But I agree, it would be very
> bizarre to withdraw a nomination at this stage, although I can imagine
> an AD nominee being renominated to a different Area or even to IETF Chair,
> after the confirming body rejected a nominee.


As can I, but I stress that its not the Nomcom's choice to summarily reverse
a previous confirmation.  See my previous comments on how to equitably
handle this issue.  It shouldn't take more than a day for the Nomcom to ASK
the confirmee if they're willing to be moved once they've been confirmed.


[Phil Roberts] It might be the case though that the nomcom trying to balance
between difficult choices would like to have back one of the
candidates the confirming body confirmed if another is candidate is
rejected.  One might be in a situation for example where there is a large
turnover and the nomcom has determined that such a large turnover could be
enough of a disruption to the community, that the nomcom, on
the community's behalf, is unwilling to change a large number and by being
constrained with the already confirmed candidates has to make one change
more than it is otherwise willing to do.  This would hardly be a summary
reversal, but something quite considered.  The process would
be helped by allowing such an interaction.
 
Phil
 


--Boundary_(ID_2ct7y0gYa6aB4jFdNIAT+A)
Content-type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2722.900" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2></FONT><BR>Michael StJohns 
wrote:<BR>&gt; &gt;<BR>&gt; &gt; This implies that the candidates already 
confirmed by the confirming<BR>&gt; body could be withdrawn.&nbsp; I think 
that's a *really<BR>&gt; &gt; really really* bad idea and unfair to the 
confirmed candidates.<BR>&gt; <BR>&gt; Well, all this process remains under the 
seal of confidentiality, so<BR>&gt; the confirmed candidates would never know. 
</DIV>
<BLOCKQUOTE 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px"><BR>Sorry 
  to go back to this, but should have commented before.&nbsp; Its actually 
  important to your current submission.<BR><BR>"... confirmed candidates would 
  never know." Except in the case that the IAB is considering an IESG where a 
  current IAB member has been submitted.&nbsp; The IAB member is disqualified 
  from participating in their own confirmation, but not in others. Current 
  practice generally has the confirmation or rejection of the IAB IESG candidate 
  first, and then bringing in that IAB member to consider the rest of the 
  candidates and positions.&nbsp; There are other reasons related to process 
  deadlock why this is a bad idea which we can get in to if 
  necessary.<BR><BR><BR>
  <BLOCKQUOTE class=cite cite="" type="cite">But I agree, it would be 
    very<BR>&gt; bizarre to withdraw a nomination at this stage, although I can 
    imagine<BR>&gt; an AD nominee being renominated to a different Area or even 
    to IETF Chair,<BR>&gt; after the confirming body rejected a 
  nominee.</BLOCKQUOTE>
  <DIV><BR>As can I, but I stress that its not the Nomcom's choice to summarily 
  reverse a previous confirmation.&nbsp; See my previous comments on how to 
  equitably handle this issue.&nbsp; It shouldn't take more than a day for the 
  Nomcom to ASK the confirmee if they're willing to be moved once they've been 
  confirmed.<BR><BR><BR><SPAN class=951041516-31032003><FONT face=Arial 
  color=#0000ff size=2>[Phil Roberts]&nbsp;It might be the case though that the 
  nomcom trying to balance between difficult choices would like to have back one 
  of the</FONT></SPAN></DIV>
  <DIV><SPAN class=951041516-31032003><FONT face=Arial color=#0000ff 
  size=2>candidates the confirming body confirmed if&nbsp;another is candidate 
  is rejected.&nbsp; One might be in a situation for example where there is a 
  large</FONT></SPAN></DIV>
  <DIV><SPAN class=951041516-31032003><FONT face=Arial color=#0000ff 
  size=2>turnover&nbsp;and the nomcom has determined that such a large turnover 
  could be enough of a disruption to the community, that&nbsp;the nomcom, 
  on</FONT></SPAN></DIV>
  <DIV><SPAN class=951041516-31032003><FONT face=Arial color=#0000ff size=2>the 
  community's behalf, is&nbsp;unwilling to change a large number and by 
  being&nbsp;constrained with the already confirmed candidates&nbsp;has 
  to&nbsp;make one change more than it is otherwise willing to 
  do.&nbsp;&nbsp;This would hardly be a summary reversal, but something quite 
  considered.&nbsp;&nbsp;The process&nbsp;would</FONT></SPAN></DIV>
  <DIV><SPAN class=951041516-31032003><FONT face=Arial color=#0000ff size=2>be 
  helped by allowing such an interaction.</FONT></SPAN></DIV>
  <DIV><SPAN class=951041516-31032003></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=951041516-31032003><FONT face=Arial color=#0000ff 
  size=2>Phil</FONT></SPAN></DIV>
  <DIV><SPAN class=951041516-31032003></SPAN><SPAN 
  class=951041516-31032003>&nbsp;</SPAN></DIV></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_2ct7y0gYa6aB4jFdNIAT+A)--

From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 13:15:10 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCM00D04L2YQ4@eListX.com> (original mail from mstjohns@mindspring.com)
 ; Mon, 31 Mar 2003 13:08:59 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCM00D01L2YQ0@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 13:08:58 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCM00D01L2YPY@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 13:08:58 -0500 (EST)
Received: from sentry.gw.tislabs.com (sentry.gw.tislabs.com [192.94.214.100])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCM00ABFL2X2C@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 13:08:57 -0500 (EST)
Received: by sentry.gw.tislabs.com; id NAA27000; Mon,
 31 Mar 2003 13:08:51 -0500 (EST)
Received: from dyn083.gw.tislabs.com(10.33.10.83) by sentry.gw.tislabs.com via
 smap (V5.5)	id xma026965; Mon, 31 Mar 2003 13:08:04 -0500
Date: Mon, 31 Mar 2003 13:06:56 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Notes from one member of the IAB on the current draft
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: Phil Roberts <PRoberts@MEGISTO.com>
Cc: ietf-nomcom@lists.elistx.com, iab@ietf.org
Message-id: <5.1.0.14.2.20030331121058.05bf84d8@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: text/plain; format=flowed; charset=us-ascii
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


>  As can I, but I stress that its not the Nomcom's choice to summarily 
> reverse a previous confirmation.  See my previous comments on how to 
> equitably handle this issue.  It shouldn't take more than a day for the 
> Nomcom to ASK the confirmee if they're willing to be moved once they've 
> been confirmed.
>
>
>[Phil Roberts] It might be the case though that the nomcom trying to 
>balance between difficult choices would like to have back one of the
>candidates the confirming body confirmed if another is candidate is 
>rejected.  One might be in a situation for example where there is a large
>turnover and the nomcom has determined that such a large turnover could be 
>enough of a disruption to the community, that the nomcom, on
>the community's behalf, is unwilling to change a large number and by being 
>constrained with the already confirmed candidates has to make one change 
>more than it is otherwise willing to do.  This would hardly be a summary 
>reversal, but something quite considered.  The process would
>be helped by allowing such an interaction.


Let me try and follow this.  I think what you're saying is that for example 
you've got 6 positions to fill.  Of the 6 you nominate 3 incumbents and 3 
new folks.  The confirming body confirms the three new folks, 2 of the 
incumbents, and rejects 1 incumbent.  You would then want to withdraw one 
of the newly confirmed new folk, and replace them with the incumbent and 
the same time you're sending another new person to replace the rejected 
incumbent because otherwise you'd have "too many changes".

Umm...this is wrong is so many ways that I don't even know how to begin.


The guideline of "try not to make too many changes" is exactly that, a 
guideline and is helpful for selecting between otherwise relatively equally 
qualified candidates.  Its not a suicide pact.  If you had six failing 
incumbents you would be derelict in your duty if you failed to replace them 
all.  Period.  If the nomcom at first pass decided that a new person was 
better qualified than the incumbent, and the confirming body agreed, there 
literally is no fair and equitable way of invalidating that confirmation 
without involving the confirmee.

The nomcom should do the best it can and select the best candidates it can 
and not worry overly much about secondary considerations after the first pass.




From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 13:25:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCM00E04LP8AF@eListX.com> (original mail from PRoberts@MEGISTO.com); Mon,
 31 Mar 2003 13:22:20 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCM00E01LP7AD@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 13:22:20 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCM00E01LP7AC@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 13:22:19 -0500 (EST)
Received: from megisto-sql1.megisto.com ([63.113.114.132])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCM00ADTLP62C@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 13:22:19 -0500 (EST)
Received: by megisto-sql1 with Internet Mail Service (5.5.2653.19)
	id <H5RMT1N8>; Mon, 31 Mar 2003 13:15:23 -0500
Content-return: allowed
Date: Mon, 31 Mar 2003 13:15:22 -0500
From: Phil Roberts <PRoberts@MEGISTO.com>
Subject: RE: Notes from one member of the IAB on the current draft
To: 'Michael StJohns' <mstjohns@mindspring.com>,
 Phil Roberts <PRoberts@MEGISTO.com>
Cc: ietf-nomcom@lists.elistx.com, iab@ietf.org
Message-id: <C3F7A1AD0781F84784B5528466CA09DD7DD59A@megisto-sql1>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: text/plain
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


> 
> Let me try and follow this.  I think what you're saying is 
> that for example 
> you've got 6 positions to fill.  Of the 6 you nominate 3 
> incumbents and 3 
> new folks.  The confirming body confirms the three new folks, 
> 2 of the 
> incumbents, and rejects 1 incumbent.  You would then want to 
> withdraw one 
> of the newly confirmed new folk, and replace them with the 
> incumbent and 
> the same time you're sending another new person to replace 
> the rejected 
> incumbent because otherwise you'd have "too many changes".

Right.

> 
> Umm...this is wrong is so many ways that I don't even know 
> how to begin.

Seems all too right to me.

> 
> 
> The guideline of "try not to make too many changes" is 
> exactly that, a 
> guideline and is helpful for selecting between otherwise 
> relatively equally 
> qualified candidates.  Its not a suicide pact.  If you had 
> six failing 
> incumbents you would be derelict in your duty if you failed 
> to replace them 
> all.  Period.  If the nomcom at first pass decided that a new 
> person was 
> better qualified than the incumbent, and the confirming body 
> agreed, there 
> literally is no fair and equitable way of invalidating that 
> confirmation 
> without involving the confirmee.

It might make sense to have the confirming body confirm or reject
a slate with reasons for rejecting a slate that include "candidate
x is not acceptable."  It might just be the case that an alternate
slate that didn't include x didn't include y as well, who the confirming
body would be willing to confirm.  It might not always be the case
that a bunch of individuals outweighs the value of a group.


> 
> The nomcom should do the best it can and select the best 
> candidates it can 
> and not worry overly much about secondary considerations 
> after the first pass.

Well, I agree, but perhaps based on our separate experiences we differ
about what are primary and secondary considerations?

Phil

> 
> 
> 

From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 17:15:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCM00104W5WK9@eListX.com> (original mail from avri@acm.org); Mon,
 31 Mar 2003 17:08:21 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCM00101W5WK7@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 17:08:20 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCM00101W5WK6@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 17:08:20 -0500 (EST)
Received: from lakecm2mtao03.coxmail.com
 (lakecm2mtao03.coxmail.com [68.99.120.70])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCM00M7TW5VF5@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 17:08:19 -0500 (EST)
Received: from acm.org ([68.15.42.104]) by lakecm2mtao03.coxmail.com
 (InterMail vM.5.01.04.05 201-253-122-122-105-20011231)
 with ESMTP          id <20030331220714.FZBW20485.lakecm2mtao03.coxmail.com@acm.org>          for
 <ietf-nomcom@lists.elistx.com>; Mon, 31 Mar 2003 17:07:14 -0500
Date: Mon, 31 Mar 2003 17:05:27 -0500
From: Avri Doria <avri@acm.org>
Subject: Recommendations for closing open issues.
To: ietf-nomcom@lists.elistx.com
Message-id: <3E88BBA7.4050602@acm.org>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2)
 Gecko/20021120 Netscape/7.01
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

This is a report of of the discussion and recommendations
that came out of the 24 March of NomCom Design Team chat.

As always these recommendations are subject to rough
consensus in the Working Group.  Since we are now in hurry
to finish so that the new rules for NomCom can be in place
before the new NomCom chair is selected - which is scheduled
to happen before the Vienna meeting - the recommended
changes are being made in the document simultaneously with
this announcement and subsequent WG discussion.

While I have grouped these all together as they represent
the output of one meeting, I ask that folks wishing to discuss
any of these recommendations start a separate email thread.

----

Re: Discretion of the IAB or IESG over whether a midterm
vacancies must be filled.

2727bis allegedly removed discretion for whether a mid-term
vacancy should be filled by the NomCom.

Note:  In rereading the document, I am not sure this is
        the case.  We certainly removed the discretion of
        which NomCom picks if a position is to be filled.
        Since a NomCom only fills position on instruction
        from the ExDir and since the I* notifies the ExDir
        of which positions to fill and since midterm vacancies
        are filled under all standing rules other then those
        having to do with which NomCom does the choosing, it
        is not clear to me that we actually ever made the
        change we think we made.

The recommendation of the DT is that the discretion should remain
with the body that looses a member.  This means that the language for
mid term vacancies should be clarified to indicate this.
Essentially, from the NomCom point of view, a vacancy exists only
when the ExDir informs it of a vacancy.  The resignation per se
does not constitute such notification.

----

Re: Poaching rules

It has been the practice of NomCom to not only choose candidates
from members of the other sitting body, but to nominate replacements
for that person at the same time.

For several reasons, the DT believes this is inappropriate:

- As a vacancy does not exist until a resignation occurs, there
is no vacancy until the candidate is confirmed.
- Further, it can be argued that since there is no rule against
serving on both bodies at the same time (though there is advice
against this practice), the position is not vacant until the
confirmed candidates resigns the prior position.
- As stated in the document and in the recommendation above, a
vacancy does not exist until the ExDir notifies the NomCom that
it does exist.

There is, however, interest in keeping the process efficient.
the DT therefore decided to recommend a 2 stage process:

1. The candidate is confirmed and is advised to immediately
resign from the prior post.  This resignation does not need to
be made public immediately, nor does it need to take effect
until a later time.  The NomCom is notified of the pending
resignation by the ExDir.
2. The NomCom then nominates a candidate for the 'to be vacant'
post.  Since the NomCom can predict this vacancy, it can be
ready with a candidate.

An aside:  We also do not have any rule against someone
            holding 2 AD spots.  I think this rule will also
            cover the case of someone being nominated for a
            different AD spot then they currently hold. As
            to what happens if someone wishes to hold
            both spots - that is not in the NomCom purview.

----

Re: Question of whether someone can be a member of both the IAB and
the IESG  (or hold 2 AD spots)

This was discussed earlier in this WG process and the consensus
was that while this is inadvisable, it should not be prohibited
by rule. Advise was therefore inserted in the advice section.

---

Re. Question of whether the confirming body, CB,  is limited
to reviewing only for process irregularities or can do a full
review of candidates.

The recommendation of the DT is that the CB has both the right
and responsibility to perform full diligence in reviewing
candidates before confirmation.  It is the CB's responsibility
to make sure any decision is for the good of the IETF.

It was recommended that the document editor craft language
specifying this explicitly.  It was further recommended that
this explication be based on MSJ's recommended text.

----

Re: the question of reviewing a slate as whole or as individual
candidates.

While more often the case in selecting the IAB then IESG, though
it does occur in the IESG as well, a slate is often picked for its
balance of talents.  The recommendation of the DT is that a slate
is sent to the CB as a whole and must be accepted as a whole.  In
rejecting a slate, the CB is certainly encouraged to indicate what
parts of the slate it finds unacceptable, but the NomCom can
reconsider the entire slate and resubmit a slate with different
candidates, even if some of the replaced candidates were acceptable
to the CB during its prior review.  It is in keeping with this
recommendation for the NomCom to submit a slate to the CB that does
not fill all open roles.  In this case, the presented slate counts
as a unit and its approval is not affected by any later submissions.
To reiterate, a slate can only be accepted in its entirety, but t
here is no rule stating that a slate must fill every vacancy - a
slate is defined as being a single list of names and positions
presented to the CB for approval.
It is considered approved and unchangeable once the CB notifies the
NomCom that it has been accepted.

----

Re. The rules under which the CB decides to accept or not
accept a slate. I.e. should 2727bis require a majority.

It is the recommendation of the DT that it is not in the NomCom's
purview to decide how the CB makes it decisions.  The recommendation
is that 2727bis remove the requirement that at least 1/2 the CB
approve a slate.  NomCom rules are for the NomCom, not the CBs, they
make their decisions by whatever process their charters or practice
dictate.

---
Re: Is the IETF chair a sitting member of the IAB

The DT recommends that it is not in the NomCom's purview to
decide whether IETF chair is a sitting member of IAB or not.
This decision is part of the IAB charter and should be determined
there.

It is recommended, however, the advice go into the oral tradition
indicating that past history indicates a practice of the IETF chair
recusing him/herself from IAB confirming votes of the IESG.


----

Re: Issue of succession rules for IETF Chair

The recommendation of the DT is that this is not in the NomCom
purview.  If a rule is required, it should be part of the IESG
charter.

----

Assuming these issues reach the rough consensus annealing point,
I plan to initiate the WG last call shortly after the new version
of the document is announced.

a.





From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 21:15:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00B047KHKA@eListX.com> (original mail from mstjohns@mindspring.com)
 ; Mon, 31 Mar 2003 21:14:41 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00B017KHK8@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 21:14:41 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00B017KGK7@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 21:14:41 -0500 (EST)
Received: from bluejay.mail.pas.earthlink.net
 (bluejay.mail.pas.earthlink.net [207.217.120.218])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006G87KGQM@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 21:14:40 -0500 (EST)
Received: from pcp802197pcs.nrockv01.md.comcast.net
 ([68.48.86.43] helo=STJOHNS-LAPTOP.mindspring.com)
	by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:DES-CBC3-SHA:168)
	(Exim 3.33 #1)	id 190BHL-0006A1-00; Mon, 31 Mar 2003 18:13:35 -0800
Date: Mon, 31 Mar 2003 21:13:17 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Recommendations for closing open issues.
In-reply-to: <3E88BBA7.4050602@acm.org>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: Avri Doria <avri@acm.org>, ietf-nomcom@lists.elistx.com
Message-id: <5.1.0.14.2.20030331204443.035237e8@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: text/plain; format=flowed; charset=us-ascii
X-ELNK-Trace:
 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4d6adaa2e2d755d50657f2cb043d12d673350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Hi Avri -

I hate to say this, but if you were designing a protocol, you would have 
ensured non-interoperability.

For those of us coming late - who exactly are the members of the design team?


At 05:05 PM 3/31/2003 -0500, Avri Doria wrote:
>This is a report of of the discussion and recommendations
>that came out of the 24 March of NomCom Design Team chat.
>
>As always these recommendations are subject to rough
>consensus in the Working Group.  Since we are now in hurry
>to finish so that the new rules for NomCom can be in place
>before the new NomCom chair is selected - which is scheduled
>to happen before the Vienna meeting - the recommended
>changes are being made in the document simultaneously with
>this announcement and subsequent WG discussion.
>
>While I have grouped these all together as they represent
>the output of one meeting, I ask that folks wishing to discuss
>any of these recommendations start a separate email thread.
>
>----
>
>Re: Discretion of the IAB or IESG over whether a midterm
>vacancies must be filled.
>
>2727bis allegedly removed discretion for whether a mid-term
>vacancy should be filled by the NomCom.
>
>Note:  In rereading the document, I am not sure this is
>        the case.  We certainly removed the discretion of
>        which NomCom picks if a position is to be filled.
>        Since a NomCom only fills position on instruction
>        from the ExDir and since the I* notifies the ExDir
>        of which positions to fill and since midterm vacancies
>        are filled under all standing rules other then those
>        having to do with which NomCom does the choosing, it
>        is not clear to me that we actually ever made the
>        change we think we made.
>
>The recommendation of the DT is that the discretion should remain
>with the body that looses a member.  This means that the language for
>mid term vacancies should be clarified to indicate this.
>Essentially, from the NomCom point of view, a vacancy exists only
>when the ExDir informs it of a vacancy.  The resignation per se
>does not constitute such notification.
>
>----
>
>Re: Poaching rules
>
>It has been the practice of NomCom to not only choose candidates
>from members of the other sitting body, but to nominate replacements
>for that person at the same time.
>
>For several reasons, the DT believes this is inappropriate:
>
>- As a vacancy does not exist until a resignation occurs, there
>is no vacancy until the candidate is confirmed.
>- Further, it can be argued that since there is no rule against
>serving on both bodies at the same time (though there is advice
>against this practice), the position is not vacant until the
>confirmed candidates resigns the prior position.
>- As stated in the document and in the recommendation above, a
>vacancy does not exist until the ExDir notifies the NomCom that
>it does exist.
>
>There is, however, interest in keeping the process efficient.
>the DT therefore decided to recommend a 2 stage process:
>
>1. The candidate is confirmed and is advised to immediately
>resign from the prior post.  This resignation does not need to
>be made public immediately, nor does it need to take effect
>until a later time.  The NomCom is notified of the pending
>resignation by the ExDir.
>2. The NomCom then nominates a candidate for the 'to be vacant'
>post.  Since the NomCom can predict this vacancy, it can be
>ready with a candidate.
>
>An aside:  We also do not have any rule against someone
>            holding 2 AD spots.  I think this rule will also
>            cover the case of someone being nominated for a
>            different AD spot then they currently hold. As
>            to what happens if someone wishes to hold
>            both spots - that is not in the NomCom purview.
>
>----
>
>Re: Question of whether someone can be a member of both the IAB and
>the IESG  (or hold 2 AD spots)
>
>This was discussed earlier in this WG process and the consensus
>was that while this is inadvisable, it should not be prohibited
>by rule. Advise was therefore inserted in the advice section.


The above three items interact poorly.  Because a) there's no rule 
prohibiting being on both IAB and IESG, then b) there's no requirement that 
a person appointed to the IESG resign from the IAB, then c) the Nomcom 
shouldn't a priori nominate an IAB replacement.  This actually happened 
this time around and caused more than a little consternation and 
confusion.  Either being a member on both is prohibited - in which case the 
Nomcom can act to do the replacement as part of the confirmation process; 
or its not prohibited, which suggest its a very separate action from the 
normal replacement process.  Pick one - PLEASE don't leave this to chance 
and good will.  For example, what happens if IAB member A is nominated and 
confirmed for a position on the IESG, but refuses to resign from the IAB????

Please simplify this by explicitly prohibiting dual membership - there is 
no real reason not to.


>Re. Question of whether the confirming body, CB,  is limited
>to reviewing only for process irregularities or can do a full
>review of candidates.
>
>The recommendation of the DT is that the CB has both the right
>and responsibility to perform full diligence in reviewing
>candidates before confirmation.  It is the CB's responsibility
>to make sure any decision is for the good of the IETF.
>
>It was recommended that the document editor craft language
>specifying this explicitly.  It was further recommended that
>this explication be based on MSJ's recommended text.
>
>----

Agreed.


>Re: the question of reviewing a slate as whole or as individual
>candidates.
>
>While more often the case in selecting the IAB then IESG, though
>it does occur in the IESG as well, a slate is often picked for its
>balance of talents.  The recommendation of the DT is that a slate
>is sent to the CB as a whole and must be accepted as a whole.  In
>rejecting a slate, the CB is certainly encouraged to indicate what
>parts of the slate it finds unacceptable, but the NomCom can
>reconsider the entire slate and resubmit a slate with different
>candidates, even if some of the replaced candidates were acceptable
>to the CB during its prior review.  It is in keeping with this
>recommendation for the NomCom to submit a slate to the CB that does
>not fill all open roles.  In this case, the presented slate counts
>as a unit and its approval is not affected by any later submissions.
>To reiterate, a slate can only be accepted in its entirety, but t
>here is no rule stating that a slate must fill every vacancy - a
>slate is defined as being a single list of names and positions
>presented to the CB for approval.
>It is considered approved and unchangeable once the CB notifies the
>NomCom that it has been accepted.


No.  Just no.  Its unfair and unreasonable to expect the CB to be able to 
balance individuals against a complete slate.  The slate represents no more 
than 1/2 of the sitting members of the body being appointed, the change of 
one or two individuals based on a rejection should not be considered to 
cause that much perturbation.  In any event, any imbalance can be fixed in 
the following year.

Confirmations are discussed and decided upon based on the qualifications of 
an individual, not on the ability of the slate as a whole to succeed or 
fail.   If I were managing the confirmation process for the IAB 
(fortunately, that's Leslie's job), I wouldn't know how to frame the 
question of whether to accept or reject a slate based on whether one or 
more individuals were bad enough to prevent us from accepting the rest.  It 
may be possible to frame this for a single rejection, but you start getting 
interesting combinatorial problems when you start thinking about more than 
one unacceptable person.

Please, leave this as a confirmation of individuals.  If an individual 
fails of confirmation, it shouldn't be that traumatic to suggest an 
alternative, even if the balance among the whole slate isn't exactly what 
the Nomcom hoped it would be.  Think of it this way: if changing 1 or 2 
fully qualified candidates (out of 12 or 18 total members) causes so much 
perturbation,  there's a lot more wrong than the Nomcom can actually fix.

The suggestion that partial slates could go forward also fails.  It 
needlessly extends the process without actually adding to the quality of 
the result.


>Re. The rules under which the CB decides to accept or not
>accept a slate. I.e. should 2727bis require a majority.
>
>It is the recommendation of the DT that it is not in the NomCom's
>purview to decide how the CB makes it decisions.  The recommendation
>is that 2727bis remove the requirement that at least 1/2 the CB
>approve a slate.  NomCom rules are for the NomCom, not the CBs, they
>make their decisions by whatever process their charters or practice
>dictate.

Again, please don't leave this in the hands of the CB.  The process at 
which the CB reaches a majority can safely be left there, but, if this is 
not externally specified, its not a given that the CB will establish rules 
to deal with the edge cases.

Please specify at least the minimum required to let the CBs come to a 
conclusion.

>---
>Re: Is the IETF chair a sitting member of the IAB
>
>The DT recommends that it is not in the NomCom's purview to
>decide whether IETF chair is a sitting member of IAB or not.
>This decision is part of the IAB charter and should be determined
>there.

Sorry, wrong.  Its clear its not in the Nomcom's purview, but it certainly 
is in this document's purview to indicate this.  The IETF chair does not 
vote and should not vote on the composition of the IESG.

>It is recommended, however, the advice go into the oral tradition
>indicating that past history indicates a practice of the IETF chair
>recusing him/herself from IAB confirming votes of the IESG.
>
>
>----
>
>Re: Issue of succession rules for IETF Chair
>
>The recommendation of the DT is that this is not in the NomCom
>purview.  If a rule is required, it should be part of the IESG
>charter.

Fair - but there is a requirement that this be addressed by someone.

>----
>
>Assuming these issues reach the rough consensus annealing point,
>I plan to initiate the WG last call shortly after the new version
>of the document is announced.
>
>a.
>
>
>
>
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.elistx.com/subscribe>


From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 21:45:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00C048XQGV@eListX.com> (original mail from avri@acm.org); Mon,
 31 Mar 2003 21:44:15 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00C018XQGT@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 21:44:14 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00C018XQGS@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 21:44:14 -0500 (EST)
Received: from lakecm2mtao02.coxmail.com
 (lakecm2mtao02.coxmail.com [68.99.120.69])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006IH8XPQM@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 21:44:13 -0500 (EST)
Received: from acm.org ([68.15.42.104]) by lakecm2mtao02.coxmail.com
 (InterMail vM.5.01.04.05 201-253-122-122-105-20011231)
 with ESMTP          id <20030401024307.HDVK22991.lakecm2mtao02.coxmail.com@acm.org>          for
 <ietf-nomcom@lists.elistx.com>; Mon, 31 Mar 2003 21:43:07 -0500
Date: Mon, 31 Mar 2003 21:41:19 -0500
From: Avri Doria <avri@acm.org>
Subject: NomCom DT was Re: Recommendations for closing open issues.
To: ietf-nomcom@lists.elistx.com
Message-id: <3E88FC4F.6070400@acm.org>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2)
 Gecko/20021120 Netscape/7.01
References: <5.1.0.14.2.20030331204443.035237e8@pop.mindspring.com>
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>



Michael StJohns wrote:

> 
> For those of us coming late - who exactly are the members of the design 
> team?

Bernard Aboba
Harald Alverstrand
Leslie Daigle
Joel Halpern
James Galvin
Thomas Narten

and me.


I have acceded to my own request and am breaking the rest of
your comments out into separate threads.

a.





From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 21:55:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00C0496NO7@eListX.com> (original mail from avri@acm.org); Mon,
 31 Mar 2003 21:49:35 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00C0196MO5@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 21:49:34 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00C0196MO4@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 21:49:34 -0500 (EST)
Received: from lakecm2mtao03.coxmail.com
 (lakecm2mtao03.coxmail.com [68.99.120.70])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006KW96LJT@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 21:49:34 -0500 (EST)
Received: from acm.org ([68.15.42.104]) by lakecm2mtao03.coxmail.com
 (InterMail vM.5.01.04.05 201-253-122-122-105-20011231)
 with ESMTP          id <20030401024829.GXVP20485.lakecm2mtao03.coxmail.com@acm.org>          for
 <ietf-nomcom@lists.elistx.com>; Mon, 31 Mar 2003 21:48:29 -0500
Date: Mon, 31 Mar 2003 21:46:40 -0500
From: Avri Doria <avri@acm.org>
Subject: Should someone be prohibited from serving in 2 roles?
To: ietf-nomcom@lists.elistx.com
Message-id: <3E88FD90.7020003@acm.org>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2)
 Gecko/20021120 Netscape/7.01
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Michael StJohns wrote:

 > At 05:05 PM 3/31/2003 -0500, Avri Doria wrote:
---
 >>
 >> Re: Discretion of the IAB or IESG over whether a midterm
 >> vacancies must be filled.
 >>
 >> 2727bis allegedly removed discretion for whether a mid-term
 >> vacancy should be filled by the NomCom.
 >>
 >> Note:  In rereading the document, I am not sure this is
 >>        the case.  We certainly removed the discretion of
 >>        which NomCom picks if a position is to be filled.
 >>        Since a NomCom only fills position on instruction
 >>        from the ExDir and since the I* notifies the ExDir
 >>        of which positions to fill and since midterm vacancies
 >>        are filled under all standing rules other then those
 >>        having to do with which NomCom does the choosing, it
 >>        is not clear to me that we actually ever made the
 >>        change we think we made.
 >>
 >> The recommendation of the DT is that the discretion should remain
 >> with the body that looses a member.  This means that the language for
 >> mid term vacancies should be clarified to indicate this.
 >> Essentially, from the NomCom point of view, a vacancy exists only
 >> when the ExDir informs it of a vacancy.  The resignation per se
 >> does not constitute such notification.
 >>
 >> ----
 >>
 >> Re: Poaching rules
 >>
 >> It has been the practice of NomCom to not only choose candidates
 >> from members of the other sitting body, but to nominate replacements
 >> for that person at the same time.
 >>
 >> For several reasons, the DT believes this is inappropriate:
 >>
 >> - As a vacancy does not exist until a resignation occurs, there
 >> is no vacancy until the candidate is confirmed.
 >> - Further, it can be argued that since there is no rule against
 >> serving on both bodies at the same time (though there is advice
 >> against this practice), the position is not vacant until the
 >> confirmed candidates resigns the prior position.
 >> - As stated in the document and in the recommendation above, a
 >> vacancy does not exist until the ExDir notifies the NomCom that
 >> it does exist.
 >>
 >> There is, however, interest in keeping the process efficient.
 >> the DT therefore decided to recommend a 2 stage process:
 >>
 >> 1. The candidate is confirmed and is advised to immediately
 >> resign from the prior post.  This resignation does not need to
 >> be made public immediately, nor does it need to take effect
 >> until a later time.  The NomCom is notified of the pending
 >> resignation by the ExDir.
 >> 2. The NomCom then nominates a candidate for the 'to be vacant'
 >> post.  Since the NomCom can predict this vacancy, it can be
 >> ready with a candidate.
 >>
 >> An aside:  We also do not have any rule against someone
 >>            holding 2 AD spots.  I think this rule will also
 >>            cover the case of someone being nominated for a
 >>            different AD spot then they currently hold. As
 >>            to what happens if someone wishes to hold
 >>            both spots - that is not in the NomCom purview.
 >>
 >> ----
 >>
 >> Re: Question of whether someone can be a member of both the IAB and
 >> the IESG  (or hold 2 AD spots)
 >>
 >> This was discussed earlier in this WG process and the consensus
 >> was that while this is inadvisable, it should not be prohibited
 >> by rule. Advise was therefore inserted in the advice section.
 >
 >
 >
 > The above three items interact poorly.  Because a) there's no rule
 > prohibiting being on both IAB and IESG, then b) there's no requirement
 > that a person appointed to the IESG resign from the IAB, then c) the
 > Nomcom shouldn't a priori nominate an IAB replacement.  This actually
 > happened this time around and caused more than a little consternation
 > and confusion.  Either being a member on both is prohibited - in which
 > case the Nomcom can act to do the replacement as part of the
 > confirmation process; or its not prohibited, which suggest its a very
 > separate action from the normal replacement process.  Pick one - PLEASE
 > don't leave this to chance and good will.  For example, what happens if
 > IAB member A is nominated and confirmed for a position on the IESG, but
 > refuses to resign from the IAB????

Then he or she would end up serving on both.
this was discussed at length and I believe that
the consensus was that while this is not to be
recommended, it should not be prohibited and
thus is advised against, but not prohibited.

 >
 > Please simplify this by explicitly prohibiting dual membership - there
 > is no real reason not to.

I think there was an assumption that there was not an
absolute reason for forbidding it and therefore there
was no consensus for forbidding it.  There was consensus
for recommending against it.


a.



From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 21:55:05 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00C049FKR0@eListX.com> (original mail from avri@acm.org); Mon,
 31 Mar 2003 21:54:56 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00C019FKQY@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 21:54:56 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00C019FKQX@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 21:54:56 -0500 (EST)
Received: from lakecm2mtao02.coxmail.com
 (lakecm2mtao02.coxmail.com [68.99.120.69])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006J89FJQM@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 21:54:55 -0500 (EST)
Received: from acm.org ([68.15.42.104]) by lakecm2mtao02.coxmail.com
 (InterMail vM.5.01.04.05 201-253-122-122-105-20011231)
 with ESMTP          id <20030401025349.HEJA22991.lakecm2mtao02.coxmail.com@acm.org>          for
 <ietf-nomcom@lists.elistx.com>; Mon, 31 Mar 2003 21:53:49 -0500
Date: Mon, 31 Mar 2003 21:52:01 -0500
From: Avri Doria <avri@acm.org>
Subject: Should a CB approve a slate or individuals?
To: ietf-nomcom@lists.elistx.com
Message-id: <3E88FED1.8020107@acm.org>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2)
 Gecko/20021120 Netscape/7.01
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

Michael StJohns wrote:

 > At 05:05 PM 3/31/2003 -0500, Avri Doria wrote:
 >
 >> Re: the question of reviewing a slate as whole or as individual
 >> candidates.
 >>
 >> While more often the case in selecting the IAB then IESG, though
 >> it does occur in the IESG as well, a slate is often picked for its
 >> balance of talents.  The recommendation of the DT is that a slate
 >> is sent to the CB as a whole and must be accepted as a whole.  In
 >> rejecting a slate, the CB is certainly encouraged to indicate what
 >> parts of the slate it finds unacceptable, but the NomCom can
 >> reconsider the entire slate and resubmit a slate with different
 >> candidates, even if some of the replaced candidates were acceptable
 >> to the CB during its prior review.  It is in keeping with this
 >> recommendation for the NomCom to submit a slate to the CB that does
 >> not fill all open roles.  In this case, the presented slate counts
 >> as a unit and its approval is not affected by any later submissions.
 >> To reiterate, a slate can only be accepted in its entirety, but t
 >> here is no rule stating that a slate must fill every vacancy - a
 >> slate is defined as being a single list of names and positions
 >> presented to the CB for approval.
 >> It is considered approved and unchangeable once the CB notifies the
 >> NomCom that it has been accepted.
 >
 >
 >
 > No.  Just no.  Its unfair and unreasonable to expect the CB to be able
 > to balance individuals against a complete slate.  The slate represents
 > no more than 1/2 of the sitting members of the body being appointed, the
 > change of one or two individuals based on a rejection should not be
 > considered to cause that much perturbation.  In any event, any imbalance
 > can be fixed in the following year.
 >
 > Confirmations are discussed and decided upon based on the qualifications
 > of an individual, not on the ability of the slate as a whole to succeed
 > or fail.   If I were managing the confirmation process for the IAB
 > (fortunately, that's Leslie's job), I wouldn't know how to frame the
 > question of whether to accept or reject a slate based on whether one or
 > more individuals were bad enough to prevent us from accepting the rest.
 > It may be possible to frame this for a single rejection, but you start
 > getting interesting combinatorial problems when you start thinking about
 > more than one unacceptable person.
 >
 > Please, leave this as a confirmation of individuals.  If an individual
 > fails of confirmation, it shouldn't be that traumatic to suggest an
 > alternative, even if the balance among the whole slate isn't exactly
 > what the Nomcom hoped it would be.  Think of it this way: if changing 1
 > or 2 fully qualified candidates (out of 12 or 18 total members) causes
 > so much perturbation,  there's a lot more wrong than the Nomcom can
 > actually fix.
 >
 > The suggestion that partial slates could go forward also fails.  It
 > needlessly extends the process without actually adding to the quality of
 > the result.
 >


I am curious to hear some discussion of the list on this issue.
So far I think there have been only a few voices.  While I need
to review the list again, I think I have heard one voice for
voting as a slate and one against.

As for RFC2727, I think it was ambiguous on the notion of a slate
of candidates versus single candidates.


a.




From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 22:05:16 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D049TQ2N@eListX.com> (original mail from avri@acm.org); Mon,
 31 Mar 2003 22:03:26 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00D019TP2L@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 22:03:26 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D019TP2K@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 22:03:25 -0500 (EST)
Received: from lakecm2mtao02.coxmail.com
 (lakecm2mtao02.coxmail.com [68.99.120.69])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006JX9TPQM@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 22:03:25 -0500 (EST)
Received: from acm.org ([68.15.42.104]) by lakecm2mtao02.coxmail.com
 (InterMail vM.5.01.04.05 201-253-122-122-105-20011231)
 with ESMTP          id <20030401030219.HEOI22991.lakecm2mtao02.coxmail.com@acm.org>          for
 <ietf-nomcom@lists.elistx.com>; Mon, 31 Mar 2003 22:02:19 -0500
Date: Mon, 31 Mar 2003 22:00:31 -0500
From: Avri Doria <avri@acm.org>
Subject: Should NomCom rules define who has CB voting rights
To: ietf-nomcom@lists.elistx.com
Message-id: <3E8900CF.7060406@acm.org>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2)
 Gecko/20021120 Netscape/7.01
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


Michael StJohns wrote:

 > At 05:05 PM 3/31/2003 -0500, Avri Doria wrote:

 >> ---
 >> Re: Is the IETF chair a sitting member of the IAB
 >>
 >> The DT recommends that it is not in the NomCom's purview to
 >> decide whether IETF chair is a sitting member of IAB or not.
 >> This decision is part of the IAB charter and should be determined
 >> there.
 >
 >
 > Sorry, wrong.  Its clear its not in the Nomcom's purview, but it
 > certainly is in this document's purview to indicate this.  The IETF
 > chair does not vote and should not vote on the composition of the IESG.
 >
 >> It is recommended, however, the advice go into the oral tradition
 >> indicating that past history indicates a practice of the IETF chair
 >> recusing him/herself from IAB confirming votes of the IESG.
 >>
 >>




From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 22:05:20 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D049UW41@eListX.com> (original mail from avri@acm.org); Mon,
 31 Mar 2003 22:04:08 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00D019UW3W@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 22:04:08 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D019UV3V@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 22:04:07 -0500 (EST)
Received: from lakecm2mtao02.coxmail.com
 (lakecm2mtao02.coxmail.com [68.99.120.69])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006K69UVQM@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 22:04:07 -0500 (EST)
Received: from acm.org ([68.15.42.104]) by lakecm2mtao02.coxmail.com
 (InterMail vM.5.01.04.05 201-253-122-122-105-20011231)
 with ESMTP          id <20030401030301.HEPL22991.lakecm2mtao02.coxmail.com@acm.org>          for
 <ietf-nomcom@lists.elistx.com>; Mon, 31 Mar 2003 22:03:01 -0500
Date: Mon, 31 Mar 2003 22:01:13 -0500
From: Avri Doria <avri@acm.org>
Subject: Should the NomCom rules define CB voting behavior
To: ietf-nomcom@lists.elistx.com
Message-id: <3E8900F9.1070102@acm.org>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2)
 Gecko/20021120 Netscape/7.01
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


Michael StJohns wrote:

 > At 05:05 PM 3/31/2003 -0500, Avri Doria wrote:
 >
 >> Re. The rules under which the CB decides to accept or not
 >> accept a slate. I.e. should 2727bis require a majority.
 >>
 >> It is the recommendation of the DT that it is not in the NomCom's
 >> purview to decide how the CB makes it decisions.  The recommendation
 >> is that 2727bis remove the requirement that at least 1/2 the CB
 >> approve a slate.  NomCom rules are for the NomCom, not the CBs, they
 >> make their decisions by whatever process their charters or practice
 >> dictate.
 >
 >
 > Again, please don't leave this in the hands of the CB.  The process at
 > which the CB reaches a majority can safely be left there, but, if this
 > is not externally specified, its not a given that the CB will establish
 > rules to deal with the edge cases.
 >
 > Please specify at least the minimum required to let the CBs come to a
 > conclusion.
 >

discussion?



From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 22:05:23 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D049V75C@eListX.com> (original mail from gih@telstra.net); Mon,
 31 Mar 2003 22:04:20 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00D019V75A@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 22:04:19 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D019V759@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 22:04:19 -0500 (EST)
Received: from kahuna.telstra.net (kahuna.telstra.net [203.50.0.6])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006KC9V5QM@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 22:04:18 -0500 (EST)
Received: from gih505.telstra.net (rsdhcp13.telstra.net [203.50.0.207])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id h31337MK059680; Tue,
 01 Apr 2003 13:03:08 +1000 (EST envelope-from gih@telstra.net)
Date: Tue, 01 Apr 2003 13:02:29 +1000
From: Geoff Huston <gih@telstra.net>
Subject: Re: Should a CB approve a slate or individuals?
In-reply-to: <3E88FED1.8020107@acm.org>
X-Sender: gih@kahuna.telstra.net
To: Avri Doria <avri@acm.org>, ietf-nomcom@lists.elistx.com
Message-id: <5.1.0.14.2.20030401125736.017a14b0@kahuna.telstra.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: text/plain; format=flowed; charset=us-ascii
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


> > Confirmations are discussed and decided upon based on the qualifications
> > of an individual, not on the ability of the slate as a whole to succeed
> > or fail.   If I were managing the confirmation process for the IAB
> > (fortunately, that's Leslie's job), I wouldn't know how to frame the
> > question of whether to accept or reject a slate based on whether one or
> > more individuals were bad enough to prevent us from accepting the rest.
> > It may be possible to frame this for a single rejection, but you start
> > getting interesting combinatorial problems when you start thinking about
> > more than one unacceptable person.
> >
> > Please, leave this as a confirmation of individuals.  If an individual
> > fails of confirmation, it shouldn't be that traumatic to suggest an
> > alternative, even if the balance among the whole slate isn't exactly
> > what the Nomcom hoped it would be.  Think of it this way: if changing 1
> > or 2 fully qualified candidates (out of 12 or 18 total members) causes
> > so much perturbation,  there's a lot more wrong than the Nomcom can
> > actually fix.
> >
> > The suggestion that partial slates could go forward also fails.  It
> > needlessly extends the process without actually adding to the quality of
> > the result.
> >
>
>
>I am curious to hear some discussion of the list on this issue.
>So far I think there have been only a few voices.  While I need
>to review the list again, I think I have heard one voice for
>voting as a slate and one against.
>
>As for RFC2727, I think it was ambiguous on the notion of a slate
>of candidates versus single candidates.


I am of the view that the most effective process is one of individual 
confirmation
or rejection , rather than confirmation or rejection of the entire slate of 
names.

The task here is to pick the best qualified individuals for each open position,
and the focus should be on the attributes of the individual to the requirements
of the open position. Treating this as a slate tends to make the entire 
confirmation
process tougher.

    Geoff






From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 22:15:09 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D04A4KGS@eListX.com> (original mail from mstjohns@mindspring.com)
 ; Mon, 31 Mar 2003 22:09:56 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00D01A4IGG@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 22:09:56 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D01A4IGE@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 22:09:54 -0500 (EST)
Received: from heron.mail.pas.earthlink.net
 (heron.mail.pas.earthlink.net [207.217.120.189])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006MXA4HJT@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 22:09:53 -0500 (EST)
Received: from pcp802197pcs.nrockv01.md.comcast.net
 ([68.48.86.43] helo=STJOHNS-LAPTOP.mindspring.com)
	by heron.mail.pas.earthlink.net with asmtp (SSLv3:DES-CBC3-SHA:168)
	(Exim 3.33 #1)	id 190C8n-0000No-00; Mon, 31 Mar 2003 19:08:49 -0800
Date: Mon, 31 Mar 2003 22:07:34 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Should a CB approve a slate or individuals?
In-reply-to: <3E88FED1.8020107@acm.org>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: Avri Doria <avri@acm.org>, ietf-nomcom@lists.elistx.com
Message-id: <5.1.0.14.2.20030331220517.05ca94e0@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: multipart/alternative;
 boundary="Boundary_(ID_q286sxmOd3o5hZLbjpF0zQ)"
X-ELNK-Trace:
 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4d260c6974661428f1b91e0e3e3ff5b25e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


--Boundary_(ID_q286sxmOd3o5hZLbjpF0zQ)
Content-type: text/plain; format=flowed; charset=us-ascii

At 09:52 PM 3/31/2003 -0500, Avri Doria wrote:
>Michael StJohns wrote:
>
>As for RFC2727, I think it was ambiguous on the notion of a slate
>of candidates versus single candidates.


2727 was explicitly non-ambiguous.  Applicable language was:
  c. The sitting IAB members review the IESG candidates, consenting to
       some, all, or none.

       If all of the candidates are confirmed, the job of the nominating
       committee with respect to reviewing the open IESG positions is
       considered complete.  If some or none of the candidates are
       confirmed, the nominating committee must reconvene to select
       alternate candidates for the rejected candidates.  Any additional
       time required by the nominating committee should not exceed its
       maximum time allotment.

--Boundary_(ID_q286sxmOd3o5hZLbjpF0zQ)
Content-type: text/html; charset=us-ascii

<html>
At 09:52 PM 3/31/2003 -0500, Avri Doria wrote:<br>
<blockquote type=cite class=cite cite>Michael StJohns wrote:<br><br>
As for RFC2727, I think it was ambiguous on the notion of a slate<br>
of candidates versus single candidates.<br>
</blockquote><br><br>
2727 was explicitly non-ambiguous.&nbsp; Applicable language was:<br>

<dl>
<dd>&nbsp;c. The sitting IAB members review the IESG candidates,
consenting to
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; some, all, or none.<br><br>

<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If all of the candidates are
confirmed, the job of the nominating
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; committee with respect to reviewing
the open IESG positions is
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; considered complete.&nbsp; If some or
none of the candidates are
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; confirmed, the nominating committee
must reconvene to select
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; alternate candidates for the rejected
candidates.&nbsp; Any additional
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; time required by the nominating
committee should not exceed its
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; maximum time allotment.
</dl></html>

--Boundary_(ID_q286sxmOd3o5hZLbjpF0zQ)--

From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 22:15:13 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D04A82KL@eListX.com> (original mail from sob@newdev.harvard.edu)
 ; Mon, 31 Mar 2003 22:12:02 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00D01A81KJ@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 22:12:01 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D01A81KI@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 22:12:01 -0500 (EST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006LAA80QM@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 22:12:01 -0500 (EST)
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h313AvkZ003063; Mon,
 31 Mar 2003 22:10:57 -0500 (EST)
Received: (from sob@localhost)	by newdev.harvard.edu (8.12.7/8.12.2/Submit)
 id h313Avrq003062; Mon, 31 Mar 2003 22:10:57 -0500 (EST)
Date: Mon, 31 Mar 2003 22:10:57 -0500 (EST)
From: Scott Bradner <sob@harvard.edu>
Subject: Re: Should a CB approve a slate or individuals?
In-reply-to: <3E88FED1.8020107@acm.org>
To: avri@acm.org, ietf-nomcom@lists.elistx.com
Message-id: <200304010310.h313Avrq003062@newdev.harvard.edu>
Content-type: TEXT/PLAIN
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

in my opinion it should be a a confirmation of individuals

I understand that this could upset a carefully balanced slate but
that seems to be less of a risk than having the CB feel that they can not
tell a nomcom that a particular individual is a non-starter for reasons a
nomcom may have chosen to ignore or did not know just because the
CB might feel that such a message about one individual might push the 
reset button on the whole nonmcom cycle


Scott

From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 22:25:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D04ADGPC@eListX.com> (original mail from sob@newdev.harvard.edu)
 ; Mon, 31 Mar 2003 22:15:16 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00D01ADGP4@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 22:15:16 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D01ADFP3@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 22:15:15 -0500 (EST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006LJADFQM@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 22:15:15 -0500 (EST)
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h313ECkZ003074; Mon,
 31 Mar 2003 22:14:12 -0500 (EST)
Received: (from sob@localhost)	by newdev.harvard.edu (8.12.7/8.12.2/Submit)
 id h313ECf2003073; Mon, 31 Mar 2003 22:14:12 -0500 (EST)
Date: Mon, 31 Mar 2003 22:14:12 -0500 (EST)
From: Scott Bradner <sob@harvard.edu>
Subject: Re: Should someone be prohibited from serving in 2 roles?
In-reply-to: <3E88FD90.7020003@acm.org>
To: avri@acm.org, ietf-nomcom@lists.elistx.com
Message-id: <200304010314.h313ECf2003073@newdev.harvard.edu>
Content-type: TEXT/PLAIN
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

> Then he or she would end up serving on both.

I think this is a quite bad idea - a person should be on only one of
the two bodies (IESG & IAB) (modulo the questions about the IAB membership 
of the IETF chair and the IESG membership of the IAB chair (fwiw 
I think they should both be "non-voting" ex-officio members) )

Scott

From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 22:25:06 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D04AFISW@eListX.com> (original mail from mstjohns@mindspring.com)
 ; Mon, 31 Mar 2003 22:16:30 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00D01AFGSS@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 22:16:30 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D01AFGSR@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 22:16:28 -0500 (EST)
Received: from bluejay.mail.pas.earthlink.net
 (bluejay.mail.pas.earthlink.net [207.217.120.218])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006LVAFFQM@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 22:16:28 -0500 (EST)
Received: from pcp802197pcs.nrockv01.md.comcast.net
 ([68.48.86.43] helo=STJOHNS-LAPTOP.mindspring.com)
	by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:DES-CBC3-SHA:168)
	(Exim 3.33 #1)	id 190CF8-0007QL-00; Mon, 31 Mar 2003 19:15:22 -0800
Date: Mon, 31 Mar 2003 22:15:09 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Should the NomCom rules define CB voting behavior
In-reply-to: <3E8900F9.1070102@acm.org>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: Avri Doria <avri@acm.org>, ietf-nomcom@lists.elistx.com
Message-id: <5.1.0.14.2.20030331221056.05d7b348@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: multipart/alternative;
 boundary="Boundary_(ID_jztMPrF3J15RD1QMK+WNtg)"
X-ELNK-Trace:
 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4d1588cfd03aa5e00232435a8644e7db4a350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>


--Boundary_(ID_jztMPrF3J15RD1QMK+WNtg)
Content-type: text/plain; format=flowed; charset=us-ascii

At 10:01 PM 3/31/2003 -0500, Avri Doria wrote:

>Michael StJohns wrote:
>
> > At 05:05 PM 3/31/2003 -0500, Avri Doria wrote:
> >
> >> Re. The rules under which the CB decides to accept or not
> >> accept a slate. I.e. should 2727bis require a majority.
> >>
> >> It is the recommendation of the DT that it is not in the NomCom's
> >> purview to decide how the CB makes it decisions.  The recommendation
> >> is that 2727bis remove the requirement that at least 1/2 the CB
> >> approve a slate.  NomCom rules are for the NomCom, not the CBs, they
> >> make their decisions by whatever process their charters or practice
> >> dictate.
> >
> >
> > Again, please don't leave this in the hands of the CB.  The process at
> > which the CB reaches a majority can safely be left there, but, if this
> > is not externally specified, its not a given that the CB will establish
> > rules to deal with the edge cases.
> >

Sorry, above should have read "...establish rules to deal with edge cases 
prior to encountering such edge cases."

> > Please specify at least the minimum required to let the CBs come to a
> > conclusion.
> >
>
>discussion?
>
>
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.elistx.com/subscribe>

--Boundary_(ID_jztMPrF3J15RD1QMK+WNtg)
Content-type: text/html; charset=us-ascii

<html>
At 10:01 PM 3/31/2003 -0500, Avri Doria wrote:<br><br>
<blockquote type=cite class=cite cite>Michael StJohns wrote:<br><br>
&gt; At 05:05 PM 3/31/2003 -0500, Avri Doria wrote:<br>
&gt;<br>
&gt;&gt; Re. The rules under which the CB decides to accept or not<br>
&gt;&gt; accept a slate. I.e. should 2727bis require a majority.<br>
&gt;&gt;<br>
&gt;&gt; It is the recommendation of the DT that it is not in the
NomCom's<br>
&gt;&gt; purview to decide how the CB makes it decisions.&nbsp; The
recommendation<br>
&gt;&gt; is that 2727bis remove the requirement that at least 1/2 the
CB<br>
&gt;&gt; approve a slate.&nbsp; NomCom rules are for the NomCom, not the
CBs, they<br>
&gt;&gt; make their decisions by whatever process their charters or
practice<br>
&gt;&gt; dictate.<br>
&gt;<br>
&gt;<br>
&gt; Again, please don't leave this in the hands of the CB.&nbsp; The
process at<br>
&gt; which the CB reaches a majority can safely be left there, but, if
this<br>
&gt; is not externally specified, its not a given that the CB will
establish<br>
&gt; rules to deal with the edge cases.<br>
&gt;</blockquote><br>
Sorry, above should have read &quot;...establish rules to deal with edge
cases <b>prior to encountering such edge cases.</b>&quot;<br><br>
<blockquote type=cite class=cite cite>&gt; Please specify at least the
minimum required to let the CBs come to a<br>
&gt; conclusion.<br>
&gt;<br>
<br>
discussion?<br><br>
<br><br>
----------------------------------------------------------------<br>
To subscribe or unsubscribe from this elist use the subscription<br>
manager:
&lt;<a href="http://lists.elistx.com/subscribe" eudora="autourl">http://lists.elistx.com/subscribe</a>&gt;</blockquote></html>

--Boundary_(ID_jztMPrF3J15RD1QMK+WNtg)--

From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 22:25:09 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D04AI9VB@eListX.com> (original mail from sob@newdev.harvard.edu)
 ; Mon, 31 Mar 2003 22:18:09 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00D01AI9V9@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 22:18:09 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00D01AI9V8@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 22:18:09 -0500 (EST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN00D05AI8UF@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 22:18:08 -0500 (EST)
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h313H6kZ003102; Mon,
 31 Mar 2003 22:17:06 -0500 (EST)
Received: (from sob@localhost)	by newdev.harvard.edu (8.12.7/8.12.2/Submit)
 id h313H6gs003101; Mon, 31 Mar 2003 22:17:06 -0500 (EST)
Date: Mon, 31 Mar 2003 22:17:06 -0500 (EST)
From: Scott Bradner <sob@harvard.edu>
Subject: Re: Should NomCom rules define who has CB voting rights
In-reply-to: <3E8900CF.7060406@acm.org>
To: avri@acm.org, ietf-nomcom@lists.elistx.com
Message-id: <200304010317.h313H6gs003101@newdev.harvard.edu>
Content-type: TEXT/PLAIN
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

I agree with Mike - the IETF chair should not vote on the IESG
slate (and should not "vote" in any IAB process)

Scott


----

Date: Mon, 31 Mar 2003 22:00:31 -0500
From: Avri Doria <avri@acm.org>
Subject: Should NomCom rules define who has CB voting rights
To: ietf-nomcom@lists.elistx.com

Michael StJohns wrote:

 > At 05:05 PM 3/31/2003 -0500, Avri Doria wrote:

 >> ---
 >> Re: Is the IETF chair a sitting member of the IAB
 >>
 >> The DT recommends that it is not in the NomCom's purview to
 >> decide whether IETF chair is a sitting member of IAB or not.
 >> This decision is part of the IAB charter and should be determined
 >> there.
 >
 >
 > Sorry, wrong.  Its clear its not in the Nomcom's purview, but it
 > certainly is in this document's purview to indicate this.  The IETF
 > chair does not vote and should not vote on the composition of the IESG.
 >
 >> It is recommended, however, the advice go into the oral tradition
 >> indicating that past history indicates a practice of the IETF chair
 >> recusing him/herself from IAB confirming votes of the IESG.
 >>
 >>




----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription

From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 22:25:12 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00E04AQ80E@eListX.com> (original mail from sob@newdev.harvard.edu)
 ; Mon, 31 Mar 2003 22:22:57 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00E01AQ80C@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 22:22:56 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00E01AQ80B@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 22:22:56 -0500 (EST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006MPAQ7QM@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 22:22:55 -0500 (EST)
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h313LqkZ003118; Mon,
 31 Mar 2003 22:21:52 -0500 (EST)
Received: (from sob@localhost)	by newdev.harvard.edu (8.12.7/8.12.2/Submit)
 id h313Lq0s003117; Mon, 31 Mar 2003 22:21:52 -0500 (EST)
Date: Mon, 31 Mar 2003 22:21:52 -0500 (EST)
From: Scott Bradner <sob@harvard.edu>
Subject: Re: Should the NomCom rules define CB voting behavior
In-reply-to: <3E8900F9.1070102@acm.org>
To: avri@acm.org, ietf-nomcom@lists.elistx.com
Message-id: <200304010321.h313Lq0s003117@newdev.harvard.edu>
Content-type: TEXT/PLAIN
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

I disagree with the DT - 
I think it is in the IETF's scope to say that the CB has to have majority 
support and say what that majority is of (those voiting or those 
able to vote - I'd rather the latter)

specfically, I think it is in the IETF's scope to say how serious the
CB needs to be - implying that if one person says "yes" and no one
else says anything a set of nominees gets OKed (or not OKed) is
not serious enough in my book

Scott

From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 22:45:01 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00E04BGXIG@eListX.com> (original mail from mstjohns@mindspring.com)
 ; Mon, 31 Mar 2003 22:38:57 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00E01BGXIE@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 22:38:57 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00E01BGXID@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 22:38:57 -0500 (EST)
Received: from bluejay.mail.pas.earthlink.net
 (bluejay.mail.pas.earthlink.net [207.217.120.218])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN006OCBGWQM@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 22:38:56 -0500 (EST)
Received: from pcp802197pcs.nrockv01.md.comcast.net
 ([68.48.86.43] helo=STJOHNS-LAPTOP.mindspring.com)
	by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:DES-CBC3-SHA:168)
	(Exim 3.33 #1)	id 190Cat-0002gK-00; Mon, 31 Mar 2003 19:37:51 -0800
Date: Mon, 31 Mar 2003 22:37:39 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Should someone be prohibited from serving in 2 roles?
In-reply-to: <3E88FD90.7020003@acm.org>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: Avri Doria <avri@acm.org>, ietf-nomcom@lists.elistx.com
Message-id: <5.1.0.14.2.20030331222115.05db8de8@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: text/plain; format=flowed; charset=us-ascii
X-ELNK-Trace:
 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4d3fa9f37896fa694b25adc6def1a7bd10350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

At 09:46 PM 3/31/2003 -0500, Avri Doria wrote:
>Michael StJohns wrote:
>Either being a member on both is prohibited - in which
> > case the Nomcom can act to do the replacement as part of the
> > confirmation process; or its not prohibited, which suggest its a very
> > separate action from the normal replacement process.  Pick one - PLEASE
> > don't leave this to chance and good will.  For example, what happens if
> > IAB member A is nominated and confirmed for a position on the IESG, but
> > refuses to resign from the IAB????
>
>Then he or she would end up serving on both.
>this was discussed at length and I believe that
>the consensus was that while this is not to be
>recommended, it should not be prohibited and
>thus is advised against, but not prohibited.
>
> >
> > Please simplify this by explicitly prohibiting dual membership - there
> > is no real reason not to.
>
>I think there was an assumption that there was not an
>absolute reason for forbidding it and therefore there
>was no consensus for forbidding it.  There was consensus
>for recommending against it.

This is actually two different threads which have some interaction.

The first thread is the interaction between the question of whether or not 
someone should serve on both boards with the question of when the Nomcom 
should act to replace someone who's on one board who is then confirmed on 
the other.

The result here is either a member should be prohibited from being on both 
bodies, OR the Nomcom should be enjoined from filling a vacancy until 
actually asked.   Mechanically, as long as either of these conditions is 
explicitly specified I think things will work.  The DT specifies the latter 
as the preferred approach and mechanically, I don't have any strong objections.

The second thread is a more basic one of whether or not its appropriate for 
someone to serve on both boards, and while you note discussion of this 
topic, you don't elaborate.

Given that the IAB acts as a check and balance on the IESG process, it 
seems to me to be a bit  inappropriate for an IESG member to also be an IAB 
member.  Without a perceived benefit, I see no great reason for not 
prohibiting this particular cross-membership.  Could one of the DT 
elaborate on why they think this might ever be useful to the 
community?  And whether or not that usefulness outweighs the possible 
perception of loss of independence of the two bodies?

Thanks - Mike




From ietf-nomcom-errors@lists.elistx.com Mon Mar 31 23:05:15 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00F04CNW2T@eListX.com> (original mail from mstjohns@mindspring.com)
 ; Mon, 31 Mar 2003 23:04:44 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HCN00F01CNW2R@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Mon,
 31 Mar 2003 23:04:44 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HCN00F01CNV2Q@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Mon, 31 Mar 2003 23:04:43 -0500 (EST)
Received: from bluejay.mail.pas.earthlink.net
 (bluejay.mail.pas.earthlink.net [207.217.120.218])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HCN00E1DCNVL2@eListX.com>
 for ietf-nomcom@lists.elistx.com; Mon, 31 Mar 2003 23:04:43 -0500 (EST)
Received: from pcp802197pcs.nrockv01.md.comcast.net
 ([68.48.86.43] helo=STJOHNS-LAPTOP.mindspring.com)
	by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:DES-CBC3-SHA:168)
	(Exim 3.33 #1)	id 190Czs-0006Di-00	for ietf-nomcom@lists.elistx.com; Mon,
 31 Mar 2003 20:03:40 -0800
Date: Mon, 31 Mar 2003 23:03:28 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Meta note on the nomcom-wg process
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: ietf-nomcom@lists.elistx.com
Message-id: <5.1.0.14.2.20030331225544.05dc7190@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Content-type: text/plain; format=flowed; charset=us-ascii
X-ELNK-Trace:
 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4da3ed3de26d102ea182dc1b1054a1ebd8350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
List-Owner: <mailto:ietf-nomcom-help@lists.elistx.com>
List-Post: <mailto:ietf-nomcom@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-nomcom/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>,
 <mailto:ietf-nomcom-request@lists.elistx.com?body=help>
List-Id: <ietf-nomcom.lists.elistx.com>

This is excerpted from a private response I made to a comment about my 
comment about non-interoperable protocols - my response at the end. - Mike

>Anyway, this is not a protocol but an evolving social process.
>It used to be light weight and trust to the rules of the
>reasonable participant.  Now, each time it gets reviewed it
>gets more commanding and less flexible.

Actually, look up the definition of "protocol".  A protocol is an 
agreement, nothing more or less.  A good agreement leaves all involved 
convinced of the fairness of the process, provides a framework for 
proceeding, and eliminates ambiguities that cause misunderstandings.  My 
comments are aimed at doing all of the above.  The Nomcom document IS a 
protocol and we should understand that as we work on fixing it.

