From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 03:56: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 <0HNX001049VIWO@eListX.com> (original mail from avri@acm.org); Thu,
 06 Nov 2003 03:50:07 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNX001019VIWL@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 03:50:06 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNX001019VHWK@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 03:50:05 -0500 (EST)
Received: from psg.com (psg.com [147.28.0.62])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNX00J9Q9VF30@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 03:50:05 -0500 (EST)
Received: from [147.28.0.62] (helo=acm.org)
	by psg.com with esmtp (Exim 4.24; FreeBSD 4.9)
	id 1AHfpL-00043D-Re	for ietf-nomcom@lists.elistx.com; Thu,
 06 Nov 2003 08:49:16 +0000
Date: Thu, 06 Nov 2003 17:49:09 +0900
From: Avri Doria <avri@acm.org>
Subject: Proposals for closing open issues
To: ietf-nomcom@lists.elistx.com
Message-id: <1676720E-1036-11D8-817E-000393CC2112@acm.org>
MIME-version: 1.0 (Apple Message framework v552)
X-Mailer: Apple Mail (2.552)
Content-type: text/plain; format=flowed; charset=US-ASCII; delsp=yes
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>

The following are proposal for ways to close the Issues remaining open  
from the last call: 1, 2, 3, 10, 17, 24

In cases where there was a proposal made at some point in the process,  
that proposal has been brought forward.  In a few cases where there was  
no specific proposal, one is suggested.

These proposals, and any issues with those proposal that come on the  
list, will be discussed as part of the WG meeting in Minneapolis.

thanks

a.




------------------
IESG Issue 1:
------------------

> The first 2 substantive issue was raised by Margaret Wasserman:
> -------------------------------------------------------------
>> In section 2:
>>      The nominating committee will be given the title of the positions
>>      to be reviewed and a brief description of the desirable set of
>>      qualifications of the candidate that is nominated to fill each
>>      position.
>
> Is this information sent publicly or privately?  There are two issues
> here:
>
> 1) I think that the "description of the desirable set of  
> qualifications"
>  should be posted publicly, along with the list of open positions when
>  the call for nominations is sent.
>
> 2) The IESG and IAB should know, unambiguously, whether or not the
>  information will be publicly disseminated before providing it.
>

History: This issue was not discussed

Questions:

Should it be mandatory that the required qualifications list be made  
public?

  If not, should the required qualifications list be confidential?

DISCUSSION SO FAR:   5 comments

The information should not be confidential.  It should be published.

Recommended wording change submitted on the list:

OLD NEW:

    14.  The Chair obtains the list of IESG and IAB positions to be
	  reviewed and a description of the desirable qualifications for

         those positions. This information is announced, along with a
         solicitation for names of volunteers from the IETF community
         willing to serve on the nominating committee.

NEW:

    14.  The Chair obtains the list of IESG and IAB positions to be
	  reviewed and a description of the desirable qualifications for
            those positions. This information is announced on
            ietf-announce@ietf.org, along with a solicitation for names
            of volunteers from the IETF community willing to serve on
           the nominating committee.


Is this wording acceptable?

***********
Proposal:
***********

Accept wording change originally proposed

> ------------------------------------------------------------------

-----------------
IESG Issue 2
-----------------
> raised by Margaret Wasserman:

>> From section 3, subsection 8:
>>      It is consistent with these rules for the announcements of a
>>      resignation, of the existence of a mid-term vacancy, and of the
>>      confirmed candidates to all occur at the same time as long as the
>>      actual sequence of events that occurred did so in the following
>>      order.
>>
>>      *  The nominating committee completes the advice and consent
>>        process for the candidate already sitting on another body.
>>
>>      *  The newly confirmed candidate resigns from their current
>>        position.
>>
>>      *  The body with the new mid-term vacancy requests that the
>>        nominating committee fill the position.
>>
>>      *  The Executive Director of the IETF informs the nominating
>>        committee of the mid-term vacancy.
>>
>>      *  The nominating committee acts on the request to fill the
>>        mid-term vacancy
>
> This section indicates that a position may be vacated and filled
> without the community being notified that a position is open.  IMO, no
> position should be filled without public notice that the position is
> open and a public call for nominations.
>
> I understand one shool of thought that says that this is okay for IAB
> positions during the normal selection cycle.  Because IAB members
> don't have separate responsibilities, it _might_ be okay to pick 6 IAB
> members from a candidate pool for 5 open positions, for example.
> However, even in this case, the community might want to know if a
> person with a particular specialty/area of expertise was moving, so
> that folks with that type of expertise could be nominated.
>
> This section would also be problematic for IESG positions.  This could
> arise in any case where one IESG position is filled by a sitting IESG
> member who is not up for renewal.  For example, consider a situation
> where the IESG chair does not volunteer for another term and is
> replaced by a sitting IESG member who is not up for renewal.  Even
> though there are two ADs for most areas, the ADs often divide up the
> area into logical sections, requiring different expertise for each
> position.
>
> There are also issues with filling any postition according to this
> section if it is applied to interim vacancies.  For example, the
> nomcom should not be empowered to move an IAB member to the IESG to
> fill and interim vacancy and replace the IAB member without making a
> public call for nominations for the open IAB position.

Background:

The issue was first brought up
     http://lists.elistx.com/archives/ietf-nomcom/200303/msg00020.html

>>>
>>>> >>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."


The recommended text change was never discussed on the list.

The issue surrounding the 'poaching' issue was discussed but the  
discussion centered on the serialization described in 2727bis-07.    
However, none of the discussions were about the result of moving  
someone from a non open seat on the IESG to fill an IAB slot and thus  
having to fill an unannounced IESG slot.

Questions:

Does the document need to be explicit about treating the replacement of  
an IESG member in an non open chair differently the the replacement of  
an IAB member in a non open seat?

Do full mid term replacement rules, including public announcement apply  
to this case?


DISCUSSION SO FAR:  8 messages

The existing text has been interpreted differently by different  
commentaries.  This is an indication that no matter what the resolution  
on the substantive issue, the text needs to clarified.

Several agree that the vacancy should be treated as a mid-term vacancy  
with announcement of the vacancy.

There is an indication that the case filling an incomplete term IAB  
seat is different from filling an incomplete term IESG seat.

There is an argument that it should not be difficult to move people  
into different positions and therefore the procedure should allow  
quasi-simultaneous filling of created openings.


Several fixes were suggested:

A. It is consistent with these rules for the Nominating Committee
to nominate a sitting Area Director to a different Area and  
simultaneously
nominate a new Area Director to the position thus vacated, or to
nominate a sitting IAB member to an Area Director position and
simultaneously nominate a new IAB member to the position thus vacated.
Any other moves between positions must be treated as resignations
that create mid-term vacancies.

B. Fix:  If the type of position (e.g. security AD) was advertised, the  
Nomcom
can take action to fill it from the set of candidates it already has for
that type of slot.  If the type of position was not advertised (e.g.
because it was an off year and there was only one of that type) it must  
not
take action to fill it and it must treat it as a mid-term
vacancy.  However, once the candidate has accepted appointment to the  
new
position and once the IAB has confirmed them and the announcement has  
been
made, the Nomcom can immediately begin the process of selection for
replacement.

C. Other fix:  Dual Membership on both the IAB and IESG is prohibited.   
A
nominee who accepts appointment to one body automatically vacates their
position on the other body not later than noon on the last of the First
IETF meeting.  As long as the to-be-vacated position type has been
advertised, the Nomcom shall take action to fill it.

Note: the issue of prohibiting dual membership was discussed previously  
in
the WG and a decision was made to discourage but not prohibit.

Status:  This issue has not yet been resolved

**********
Proposal
**********

Accept language originally proposed.  Specifically:


"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."

> ----------------------------------------------------------------

------------------
IESG Issue 3;
------------------
> The third substantive issue was raised by Thomas Narten:
>
>>        Liaisons from the IESG, IAB, and Internet Society Board of
>>        Trustees are expected to review the operation and executing
>>        process of the nominating committee and to report any concerns
>>        or issues to the Chair of the nominating committee immediately.
>>        If they can not resolve the issue between themselves liaisons
>>        must report the issue to their respective bodies.  If their
>>        respective body agrees that there is an issue the liaison must
>>        report it according to the dispute resolution process stated
>>        elsewhere in this document.
>
> I worry that there will be problems with the above in practice. In
> particular, the text requires that a liaison report problems back to
> their respective group (i.e., IESG or IAB) before invoking the formal
> dispute resolution mechanism. But confidentiality rules rather limit
> what the liaison can say to their body, and in the case where dispute
> resolution may need invoking, it seems like details will be
> important. I worry that this will create problems in practice, with it
> being unclear what can be said. And if that is the case, it is unclear
> what value the discussion within the respective I* would actually
> have. This is perhaps more a problem for the IESG, since it has no
> confirming role, but it seems like a general issue.
>
> There are ways of dealing with this, but I'm not sure what is best or
> what the WG might think. Some initial thoughts:
>
> - I note that the current wording doesn't mention the obvious, i.e.,
>  have the liaisons and previous chair get together and discuss
>  before escalating. One could also have the liaison (independently)
>  decide whether to formally appeal after such a consultation. This
>  avoids the confidentiality issue and would seem like a necessary
>  check as part of escalating issues.
>
> - add some wording saying that confidentiality rules allow sharing of
>  info as needed to assess whether to file a formal complaint.

Background:

This particular issue was never discussed, but the issue of  
confidentiality was frequently discussed in many different contexts.   
Section 10, Security, discusses the extension of confidentiality to  
those outside the Nomcom when necessary, though it is not explicit that  
this extension would also apply to the IAB, IESG or ISOC in the case of  
Nomcom operational issues.

I also note that in the text Thomas quoted, it does state that after  
reporting the Issues to the chair or committee they only escalate if '  
they cannot resolve the issue between themselves'.  It is, perhaps,  
implicit in this that they can and should discuss with the past chair.

Questions:

Does content need to be added to the text to  allow extension of  
confidentiality to the Liaison in the case of reporting issues having  
to do with the internal operations of the Nomcom?

Does content need to be added to explicitly state that liaisons should  
consult among themselves and with the past chair before escalating an  
issue to their respective I-groups?


DISCUSSION SO FAR:  1 comment

Doing so would blur the lines in confidentiality.  Recommendation that  
the clarification mentioned above be added to the text.

**********
Proposal:
**********

Old Text

        Liaisons from the IESG, IAB, and Internet Society Board of
         Trustees (if one was appointed) are expected to review the
         operation and executing process of the nominating committee and
         to report any concerns or issues to the Chair of the nominating
         committee immediately.  If they can not resolve the issue
         between themselves, liaisons must report the issue to their
         respective bodies.  If their respective body agrees that there
         is an issue the liaison must report it according to the dispute
         resolution process stated elsewhere in this document.

New Text

         Liaisons from the IESG, IAB, and Internet Society Board of
         Trustees (if one was appointed) are expected to review the
         operation and executing process of the nominating committee and
         to report any concerns or issues to the Chair of the nominating
         committee immediately.  If the Chair in consultation with a  
sub-group
         composed of the liaisons cannot resolve
         the issue, then the Chair must report it according to the  
dispute
         resolution process stated elsewhere in this document.

> ----------------------------------------------------------------------- 
> ---

Issue 4-26 are not considered 'showstoppers' but should be addressed  
before sending the document back to the IESG


-----------------
IESG Issue 10
-----------------

>
>>        conducted.  A member may recalled if at least a quorum of all
>>        committee members agree, including the vote of the member being
>>        recalled.
>
> What does this mean? simple majority if there is a quorum? (I ask
> because in most cases this document doesn't proscribe rules, leaving
> that to the nomcom to decide.)

Background:  While the document discusses the quorum that must be  
present for a vote, the actual voting mechanisms are to be be  
determined by the Nomcom itself.

Question: should text be added making an explicit rule for the voting  
in a Nomcom recall be specified in the document.

DISCUSSION SO FAR:  2 comments

2 answers of yes.
- suggestion of 2/3 or majority
- comment that 2/3 was too stringent.


***********
Proposal:
***********


Old Text

         Regardless of the circumstances, if individual committee members
         can not work out their differences between themselves, the
         entire committee may be called upon to discuss and review the
         circumstances.  If a resolution is not forthcoming a vote may be
         conducted.  A member may recalled if at least a quorum of all
         committee members agree, including the vote of the member being
         recalled.

New Text

        Regardless of the circumstances, if individual committee members
         can not work out their differences between themselves, the
         entire committee may be called upon to discuss and review the
         circumstances.  If a resolution is not forthcoming a vote may be
         conducted.  A member may recalled if 2/3  of all
         committee members agree to the recall



-----------------
IESG Issue 17
-----------------

>
>>        The confirmation process must be completed at least one month
>>        prior to the First IETF.
>
> s/must/should/ other parts of the document imply should on this topic.

Questions;

Is this an editorial or content change?

Is the change accepted?

Answers so far: 2

- both answers:  It is content not editorial

- 1 answer: without change leaves situation open
- 1 answer: intentionally left open

Further discussion ?


***********
Proposal:
***********

Leave text as written.


-----------------
IESG Issue 24
-----------------

>
>>      A term may begin or end no sooner than the
>>      first day of the meeting and no later than the last day of the
>>      meeting as determined by the mutual agreement of the currently
>>      sitting member and the confirmed candidate. The confirmed
>>      candidate's term may overlap the sitting member's term during the
>>      meeting as determined by their mutual agreement.
>
> How does this apply to IAB terms?  In the case where there is
> more than one new IAB member, I don't think that it is
> defined which IAB member each new member is replacing.

Questions:

Should the question of starting time for IAB be separated from the  
question of IESG?

Should it be pointed out that since IAB members do not replace specific  
IAB members, it is consistent that new IAB members may overlap with  
retiring IAB members?

DISCUSSION SO FAR: 2 comments

- 1 that the IAB should be a separate case and should happen at the end  
of the week
- 1 that the current, flexible, "during the week" handoff be retained


***********
Proposal:
***********

Suggested change, also fixing the grammar nit:

OLD:

                  A member may recalled if at least a quorum of all
        committee members agree, including the vote of the member being
        recalled.

NEW:

        A member may be recalled if at least a quorum of all committee
        members (defined above as 75%) vote for the recall.




From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 03:57:30 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNX00204A1G3Y@eListX.com> (original mail from avri@acm.org); Thu,
 06 Nov 2003 03:53:40 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNX00201A1F3W@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 03:53:39 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNX00201A1F3V@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 03:53:39 -0500 (EST)
Received: from psg.com (psg.com [147.28.0.62])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNX00J9YA1632@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 03:53:39 -0500 (EST)
Received: from [147.28.0.62] (helo=acm.org)
	by psg.com with esmtp (Exim 4.24; FreeBSD 4.9)	id 1AHfsf-0004Us-Hh; Thu,
 06 Nov 2003 08:52:41 +0000
Date: Thu, 06 Nov 2003 17:52:36 +0900
From: Avri Doria <avri@acm.org>
Subject: Agenda for Nomcom WG
To: ietf-nomcom@lists.elistx.com
Cc: agenda@ietf.org
Message-id: <91ED74D0-1036-11D8-817E-000393CC2112@acm.org>
MIME-version: 1.0 (Apple Message framework v552)
X-Mailer: Apple Mail (2.552)
Content-type: text/plain; format=flowed; 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>


- Agenda Review

- Review of changes made in draft-ietf-nomcom-2727bis-08.txt

- Review of proposals for closing open issues

- Discussion of issue of when 2727bis becomes normative


From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 11:35:04 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNX00704UZPNJ@eListX.com> (original mail from brc@zurich.ibm.com); Thu,
 06 Nov 2003 11:26:13 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNX00701UZONH@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 11:26:12 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNX00701UZONG@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 11:26:12 -0500 (EST)
Received: from d12lmsgate.de.ibm.com
 (d12lmsgate-4.de.ibm.com [194.196.100.237]) by eListX.com
 (PMDF V6.0-025 #44856) with ESMTP id <0HNX002JFUZNEP@eListX.com> for
 ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 11:26:11 -0500 (EST)
Received: from d12relay01.megacenter.de.ibm.com
 (d12relay01.megacenter.de.ibm.com [9.149.165.180])
	by d12lmsgate.de.ibm.com (8.12.10/8.12.8) with ESMTP id hA6GPJo0105276; Thu,
 06 Nov 2003 17:25:20 +0100
Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140])
	by d12relay01.megacenter.de.ibm.com (8.12.9/NCO/VER6.6)
 with ESMTP id hA6GPKqI214946; Thu, 06 Nov 2003 17:25:20 +0100
Received: from zurich.ibm.com ([9.145.246.63])	by ochsehorn.zurich.ibm.com
 (AIX4.3/8.9.3p2/8.9.3) with ESMTP id RAA73792; Thu, 06 Nov 2003 17:25:18 +0100
Date: Thu, 06 Nov 2003 17:24:43 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Subject: Re: Proposals for closing open issues
To: Avri Doria <avri@acm.org>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <3FAA75CB.EDFDA5F8@zurich.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: <1676720E-1036-11D8-817E-000393CC2112@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 the interests of closure, I am happy to accept all Avri's suggested resolutions.

    Brian

Avri Doria wrote:
> 
> The following are proposal for ways to close the Issues remaining open
> from the last call: 1, 2, 3, 10, 17, 24
> 
> In cases where there was a proposal made at some point in the process,
> that proposal has been brought forward.  In a few cases where there was
> no specific proposal, one is suggested.

<snip>

From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 11:55: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 <0HNX00904VWA8K@eListX.com> (original mail from mstjohns@mindspring.com)
 ; Thu, 06 Nov 2003 11:45:46 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNX00901VW98I@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 11:45:45 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNX00901VW98B@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 11:45:45 -0500 (EST)
Received: from firecrest.mail.pas.earthlink.net
 (firecrest.mail.pas.earthlink.net [207.217.121.247])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNX002P8VW8EP@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 11:45:44 -0500 (EST)
Received: from pcp06939638pcs.nrockv01.md.comcast.net
 ([69.138.17.182] helo=STJOHNS-LAPTOP2.mindspring.com)
	by firecrest.mail.pas.earthlink.net with asmtp (TLSv1:RC4-SHA:128)
	(Exim 3.33 #1)	id 1AHnFd-000134-00; Thu, 06 Nov 2003 08:44:53 -0800
Date: Thu, 06 Nov 2003 11:44:54 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Proposals for closing open issues
In-reply-to: <1676720E-1036-11D8-817E-000393CC2112@acm.org>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: Avri Doria <avri@acm.org>, ietf-nomcom@lists.elistx.com
Message-id: <6.0.0.22.2.20031106112812.035fff48@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Content-type: text/plain; format=flowed; charset=us-ascii
X-ELNK-Trace:
 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4dbdefe13d0e20f05e354ed10999f681aa350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
References: <1676720E-1036-11D8-817E-000393CC2112@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>

At 03:49 AM 11/6/2003, Avri Doria wrote:
>The following are proposal for ways to close the Issues remaining open
>from the last call: 1, 2, 3, 10, 17, 24
>
>In cases where there was a proposal made at some point in the process,
>that proposal has been brought forward.  In a few cases where there was
>no specific proposal, one is suggested.
>
>These proposals, and any issues with those proposal that come on the
>list, will be discussed as part of the WG meeting in Minneapolis.
>
>thanks
>
>a.
>
>
>
>
>------------------
>IESG Issue 1:
>------------------
>
>>The first 2 substantive issue was raised by Margaret Wasserman:
>>-------------------------------------------------------------
>>>In section 2:
>>>      The nominating committee will be given the title of the positions
>>>      to be reviewed and a brief description of the desirable set of
>>>      qualifications of the candidate that is nominated to fill each
>>>      position.
>>
>>Is this information sent publicly or privately?  There are two issues
>>here:
>>
>>1) I think that the "description of the desirable set of
>>qualifications"
>>  should be posted publicly, along with the list of open positions when
>>  the call for nominations is sent.
>>
>>2) The IESG and IAB should know, unambiguously, whether or not the
>>  information will be publicly disseminated before providing it.
>
>History: This issue was not discussed
>
>Questions:
>
>Should it be mandatory that the required qualifications list be made
>public?
>
>  If not, should the required qualifications list be confidential?
>
>DISCUSSION SO FAR:   5 comments
>
>The information should not be confidential.  It should be published.

Specifically, it should be published as part of the announcement 
information, rather than as part of the solicitation for nominations.

Rationale:  While the information is important for the IETF participants to 
understand the choices, publishing it prior to the nomcom making a choice 
may result less than useful public discussion of that criteria and 
thrashing (as in "page thrashing") of the process.


>Recommended wording change submitted on the list:
>
>OLD NEW:
>
>    14.  The Chair obtains the list of IESG and IAB positions to be
>           reviewed and a description of the desirable qualifications for
>
>         those positions. This information is announced, along with a
>         solicitation for names of volunteers from the IETF community
>         willing to serve on the nominating committee.
>
>NEW:
>
>    14.  The Chair obtains the list of IESG and IAB positions to be
>           reviewed and a description of the desirable qualifications for
>            those positions. This information is announced on
>            ietf-announce@ietf.org, along with a solicitation for names
>            of volunteers from the IETF community willing to serve on
>           the nominating committee.
>
>
>Is this wording acceptable?

No - see above.


>***********
>Proposal:
>***********
>
>Accept wording change originally proposed
>
>>------------------------------------------------------------------
>
>-----------------
>IESG Issue 2
>-----------------
>>raised by Margaret Wasserman:
>
>>> From section 3, subsection 8:
>>>      It is consistent with these rules for the announcements of a
>>>      resignation, of the existence of a mid-term vacancy, and of the
>>>      confirmed candidates to all occur at the same time as long as the
>>>      actual sequence of events that occurred did so in the following
>>>      order.
>>>
>>>      *  The nominating committee completes the advice and consent
>>>        process for the candidate already sitting on another body.
>>>
>>>      *  The newly confirmed candidate resigns from their current
>>>        position.
>>>
>>>      *  The body with the new mid-term vacancy requests that the
>>>        nominating committee fill the position.
>>>
>>>      *  The Executive Director of the IETF informs the nominating
>>>        committee of the mid-term vacancy.
>>>
>>>      *  The nominating committee acts on the request to fill the
>>>        mid-term vacancy
>>
>>This section indicates that a position may be vacated and filled
>>without the community being notified that a position is open.  IMO, no
>>position should be filled without public notice that the position is
>>open and a public call for nominations.
>>
>>I understand one shool of thought that says that this is okay for IAB
>>positions during the normal selection cycle.  Because IAB members
>>don't have separate responsibilities, it _might_ be okay to pick 6 IAB
>>members from a candidate pool for 5 open positions, for example.
>>However, even in this case, the community might want to know if a
>>person with a particular specialty/area of expertise was moving, so
>>that folks with that type of expertise could be nominated.
>>
>>This section would also be problematic for IESG positions.  This could
>>arise in any case where one IESG position is filled by a sitting IESG
>>member who is not up for renewal.  For example, consider a situation
>>where the IESG chair does not volunteer for another term and is
>>replaced by a sitting IESG member who is not up for renewal.  Even
>>though there are two ADs for most areas, the ADs often divide up the
>>area into logical sections, requiring different expertise for each
>>position.
>>
>>There are also issues with filling any postition according to this
>>section if it is applied to interim vacancies.  For example, the
>>nomcom should not be empowered to move an IAB member to the IESG to
>>fill and interim vacancy and replace the IAB member without making a
>>public call for nominations for the open IAB position.
>
>Background:
>
>The issue was first brought up
>     http://lists.elistx.com/archives/ietf-nomcom/200303/msg00020.html
>
>>>>
>>>>> >>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."
>
>
>The recommended text change was never discussed on the list.
>
>The issue surrounding the 'poaching' issue was discussed but the
>discussion centered on the serialization described in 2727bis-07.
>However, none of the discussions were about the result of moving
>someone from a non open seat on the IESG to fill an IAB slot and thus
>having to fill an unannounced IESG slot.
>
>Questions:
>
>Does the document need to be explicit about treating the replacement of
>an IESG member in an non open chair differently the the replacement of
>an IAB member in a non open seat?
>
>Do full mid term replacement rules, including public announcement apply
>to this case?
>
>
>DISCUSSION SO FAR:  8 messages
>
>The existing text has been interpreted differently by different
>commentaries.  This is an indication that no matter what the resolution
>on the substantive issue, the text needs to clarified.
>
>Several agree that the vacancy should be treated as a mid-term vacancy
>with announcement of the vacancy.
>
>There is an indication that the case filling an incomplete term IAB
>seat is different from filling an incomplete term IESG seat.
>
>There is an argument that it should not be difficult to move people
>into different positions and therefore the procedure should allow
>quasi-simultaneous filling of created openings.
>
>
>Several fixes were suggested:
>
>A. It is consistent with these rules for the Nominating Committee
>to nominate a sitting Area Director to a different Area and
>simultaneously
>nominate a new Area Director to the position thus vacated, or to
>nominate a sitting IAB member to an Area Director position and
>simultaneously nominate a new IAB member to the position thus vacated.
>Any other moves between positions must be treated as resignations
>that create mid-term vacancies.
>
>B. Fix:  If the type of position (e.g. security AD) was advertised, the
>Nomcom
>can take action to fill it from the set of candidates it already has for
>that type of slot.  If the type of position was not advertised (e.g.
>because it was an off year and there was only one of that type) it must
>not
>take action to fill it and it must treat it as a mid-term
>vacancy.  However, once the candidate has accepted appointment to the
>new
>position and once the IAB has confirmed them and the announcement has
>been
>made, the Nomcom can immediately begin the process of selection for
>replacement.
>
>C. Other fix:  Dual Membership on both the IAB and IESG is prohibited.
>A
>nominee who accepts appointment to one body automatically vacates their
>position on the other body not later than noon on the last of the First
>IETF meeting.  As long as the to-be-vacated position type has been
>advertised, the Nomcom shall take action to fill it.
>
>Note: the issue of prohibiting dual membership was discussed previously
>in
>the WG and a decision was made to discourage but not prohibit.
>
>Status:  This issue has not yet been resolved
>
>**********
>Proposal
>**********
>
>Accept language originally proposed.  Specifically:
>
>
>"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."
>
>>----------------------------------------------------------------

OK.


>------------------
>IESG Issue 3;
>------------------
>>The third substantive issue was raised by Thomas Narten:
>>
>>>        Liaisons from the IESG, IAB, and Internet Society Board of
>>>        Trustees are expected to review the operation and executing
>>>        process of the nominating committee and to report any concerns
>>>        or issues to the Chair of the nominating committee immediately.
>>>        If they can not resolve the issue between themselves liaisons
>>>        must report the issue to their respective bodies.  If their
>>>        respective body agrees that there is an issue the liaison must
>>>        report it according to the dispute resolution process stated
>>>        elsewhere in this document.
>>
>>I worry that there will be problems with the above in practice. In
>>particular, the text requires that a liaison report problems back to
>>their respective group (i.e., IESG or IAB) before invoking the formal
>>dispute resolution mechanism. But confidentiality rules rather limit
>>what the liaison can say to their body, and in the case where dispute
>>resolution may need invoking, it seems like details will be
>>important. I worry that this will create problems in practice, with it
>>being unclear what can be said. And if that is the case, it is unclear
>>what value the discussion within the respective I* would actually
>>have. This is perhaps more a problem for the IESG, since it has no
>>confirming role, but it seems like a general issue.
>>
>>There are ways of dealing with this, but I'm not sure what is best or
>>what the WG might think. Some initial thoughts:
>>
>>- I note that the current wording doesn't mention the obvious, i.e.,
>>  have the liaisons and previous chair get together and discuss
>>  before escalating. One could also have the liaison (independently)
>>  decide whether to formally appeal after such a consultation. This
>>  avoids the confidentiality issue and would seem like a necessary
>>  check as part of escalating issues.
>>
>>- add some wording saying that confidentiality rules allow sharing of
>>  info as needed to assess whether to file a formal complaint.
>
>Background:
>
>This particular issue was never discussed, but the issue of
>confidentiality was frequently discussed in many different contexts.
>Section 10, Security, discusses the extension of confidentiality to
>those outside the Nomcom when necessary, though it is not explicit that
>this extension would also apply to the IAB, IESG or ISOC in the case of
>Nomcom operational issues.
>
>I also note that in the text Thomas quoted, it does state that after
>reporting the Issues to the chair or committee they only escalate if '
>they cannot resolve the issue between themselves'.  It is, perhaps,
>implicit in this that they can and should discuss with the past chair.
>
>Questions:
>
>Does content need to be added to the text to  allow extension of
>confidentiality to the Liaison in the case of reporting issues having
>to do with the internal operations of the Nomcom?
>
>Does content need to be added to explicitly state that liaisons should
>consult among themselves and with the past chair before escalating an
>issue to their respective I-groups?
>
>
>DISCUSSION SO FAR:  1 comment
>
>Doing so would blur the lines in confidentiality.  Recommendation that
>the clarification mentioned above be added to the text.
>
>**********
>Proposal:
>**********
>
>Old Text
>
>        Liaisons from the IESG, IAB, and Internet Society Board of
>         Trustees (if one was appointed) are expected to review the
>         operation and executing process of the nominating committee and
>         to report any concerns or issues to the Chair of the nominating
>         committee immediately.  If they can not resolve the issue
>         between themselves, liaisons must report the issue to their
>         respective bodies.  If their respective body agrees that there
>         is an issue the liaison must report it according to the dispute
>         resolution process stated elsewhere in this document.
>
>New Text
>
>         Liaisons from the IESG, IAB, and Internet Society Board of
>         Trustees (if one was appointed) are expected to review the
>         operation and executing process of the nominating committee and
>         to report any concerns or issues to the Chair of the nominating
>         committee immediately.  If the Chair in consultation with a
>sub-group
>         composed of the liaisons cannot resolve
>         the issue, then the Chair must report it according to the
>dispute
>         resolution process stated elsewhere in this document.
>
>>----------------------------------------------------------------------- ---
>
>Issue 4-26 are not considered 'showstoppers' but should be addressed
>before sending the document back to the IESG
>
>
>-----------------
>IESG Issue 10
>-----------------
>
>>
>>>        conducted.  A member may recalled if at least a quorum of all
>>>        committee members agree, including the vote of the member being
>>>        recalled.
>>
>>What does this mean? simple majority if there is a quorum? (I ask
>>because in most cases this document doesn't proscribe rules, leaving
>>that to the nomcom to decide.)
>
>Background:  While the document discusses the quorum that must be
>present for a vote, the actual voting mechanisms are to be be
>determined by the Nomcom itself.
>
>Question: should text be added making an explicit rule for the voting
>in a Nomcom recall be specified in the document.
>
>DISCUSSION SO FAR:  2 comments
>
>2 answers of yes.
>- suggestion of 2/3 or majority
>- comment that 2/3 was too stringent.
>
>
>***********
>Proposal:
>***********
>
>
>Old Text
>
>         Regardless of the circumstances, if individual committee members
>         can not work out their differences between themselves, the
>         entire committee may be called upon to discuss and review the
>         circumstances.  If a resolution is not forthcoming a vote may be
>         conducted.  A member may recalled if at least a quorum of all
>         committee members agree, including the vote of the member being
>         recalled.
>
>New Text
>
>        Regardless of the circumstances, if individual committee members
>         can not work out their differences between themselves, the
>         entire committee may be called upon to discuss and review the
>         circumstances.  If a resolution is not forthcoming a vote may be
>         conducted.  A member may recalled if 2/3  of all
>         committee members agree to the recall
>
>
>
>-----------------
>IESG Issue 17
>-----------------
>
>>
>>>        The confirmation process must be completed at least one month
>>>        prior to the First IETF.
>>
>>s/must/should/ other parts of the document imply should on this topic.
>
>Questions;
>
>Is this an editorial or content change?
>
>Is the change accepted?
>
>Answers so far: 2
>
>- both answers:  It is content not editorial
>
>- 1 answer: without change leaves situation open
>- 1 answer: intentionally left open
>
>Further discussion ?
>
>
>***********
>Proposal:
>***********
>
>Leave text as written.
>
>
>-----------------
>IESG Issue 24
>-----------------
>
>>
>>>      A term may begin or end no sooner than the
>>>      first day of the meeting and no later than the last day of the
>>>      meeting as determined by the mutual agreement of the currently
>>>      sitting member and the confirmed candidate. The confirmed
>>>      candidate's term may overlap the sitting member's term during the
>>>      meeting as determined by their mutual agreement.
>>
>>How does this apply to IAB terms?  In the case where there is
>>more than one new IAB member, I don't think that it is
>>defined which IAB member each new member is replacing.
>
>Questions:
>
>Should the question of starting time for IAB be separated from the
>question of IESG?
>
>Should it be pointed out that since IAB members do not replace specific
>IAB members, it is consistent that new IAB members may overlap with
>retiring IAB members?
>
>DISCUSSION SO FAR: 2 comments
>
>- 1 that the IAB should be a separate case and should happen at the end
>of the week
>- 1 that the current, flexible, "during the week" handoff be retained
>
>
>***********
>Proposal:
>***********
>
>Suggested change, also fixing the grammar nit:
>
>OLD:
>
>                  A member may recalled if at least a quorum of all
>        committee members agree, including the vote of the member being
>        recalled.
>
>NEW:
>
>        A member may be recalled if at least a quorum of all committee
>        members (defined above as 75%) vote for the recall.

*sigh*  Still too ambiguous.

"A member may be recalled if at least 2/3 of the mandated members (i.e. the 
voting members, chair, past chair representative, IESG and IAB liaisons) 
minus the member under consideration for recall concur."

This gets around the case of trying to decide whether an invited attendee 
(e.g. this years ISOC liaison) gets a vote or not.  3/4 of 13 (10 + 4 -1) 
is 10 - that seems a bit high.  2/3 of 13 is going to be 9 - that's 
probably more reasonable.






>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.elistx.com/subscribe>



From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 14:45: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 <0HNY00K043X1RS@eListX.com>
 (original mail from Margaret.Wasserman@nokia.com); Thu,
 06 Nov 2003 14:39:01 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00K013X0RQ@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 14:39:01 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00K013X0RP@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 14:39:00 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNY00K2Z3WZ9A@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 14:39:00 -0500 (EST)
Received: from esvir01nok.ntc.nokia.com
 (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hA6JcAY16198	for
 <ietf-nomcom@lists.elistx.com>; Thu, 06 Nov 2003 21:38:10 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5)
 with ESMTP id <T65bf63d357ac158f21082@esvir01nok.ntc.nokia.com>; Thu,
 06 Nov 2003 21:38:07 +0200
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13])
 by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Thu,
 06 Nov 2003 11:37:46 -0800
Date: Thu, 06 Nov 2003 14:37:43 -0500
From: Margaret.Wasserman@nokia.com
Subject: RE: Proposals for closing open issues
To: mstjohns@mindspring.com, avri@acm.org, ietf-nomcom@lists.elistx.com
Message-id:
 <E320A8529CF07E4C967ECC2F380B0CF902443F85@bsebe001.americas.nokia.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: QUOTED-PRINTABLE
Thread-Topic: Proposals for closing open issues
Thread-Index: AcOkhVlOStv8rI9+T7uDePoSAfpXMAAF2uRw
content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
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>
X-OriginalArrivalTime: 06 Nov 2003 19:37:46.0023 (UTC)
 FILETIME=[740B6370:01C3A49D]



Posting as an interested individual:

> >The information should not be confidential.  It should be publishe=
d.
>=20
> Specifically, it should be published as part of the announcement=
=20
> information, rather than as part of the solicitation for nomination=
s.

I disagree.  I think that the qualifications should be posted as part
of the call for nominations.
=20
> Rationale:  While the information is important for the IETF=20
> participants to understand the choices, publishing it prior to the=
=20
> nomcom making a choice may result less than useful public discussio=
n=20
> of that criteria and thrashing (as in "page thrashing") of the proc=
ess.

Rationale: I believe that it would valuable for the community to=20
provide feedback on the qualifications required for leadership=20
positions _before_ the leaders are chosen to fill them.  I also=20
think that posting the qualifications might help the community
to identify and represent qualified nominees.

Margaret

From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 14:55: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 <0HNY00L044DTIR@eListX.com>
 (original mail from Margaret.Wasserman@nokia.com); Thu,
 06 Nov 2003 14:49:05 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00L014DSIP@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 14:49:05 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00L014DSIO@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 14:49:04 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNY00FJA4DRUI@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 14:49:04 -0500 (EST)
Received: from esvir05nok.ntc.nokia.com
 (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hA6JmFY25351	for
 <ietf-nomcom@lists.elistx.com>; Thu, 06 Nov 2003 21:48:15 +0200 (EET)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5)
 with ESMTP id <T65bf6d1637ac158f256d0@esvir05nok.ntc.nokia.com>; Thu,
 06 Nov 2003 21:48:14 +0200
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13])
 by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Thu,
 06 Nov 2003 13:47:42 -0600
Date: Thu, 06 Nov 2003 14:47:41 -0500
From: Margaret.Wasserman@nokia.com
Subject: RE: Proposals for closing open issues
To: avri@acm.org, ietf-nomcom@lists.elistx.com
Message-id:
 <E320A8529CF07E4C967ECC2F380B0CF902443F86@bsebe001.americas.nokia.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: QUOTED-PRINTABLE
Thread-Topic: Proposals for closing open issues
Thread-Index: AcOkRZW8A/9iJAcXQ3yR6/tjAZgpqAAWAEUQ
content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
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>
X-OriginalArrivalTime: 06 Nov 2003 19:47:42.0300 (UTC)
 FILETIME=[D77409C0:01C3A49E]


Hi All,

The proposed solutions would satisfy my blocking issues,
except for one remaining question:

> "Nomcom-caused Mid-term Vacancies:
>=20
> From time to time the Nomcom may propose moving a serving Area =
=20
> 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=20
> end of their normal term there is no change in procedures. Otherwis=
e,=20
> this is treated as a mid-term vacancy and mid-term procedures are=
=20
> used with the following exceptions:
>=20
> a) If the vacancy will occur on the IAB due to a move from=20
> the IAB to the IESG, the Nomcom may, upon confirmation of nominee/I=
AB=20
> member, submit for confirmation as part of the normal slate of=20
> candidates another nominee to complete the term of the departing=
=20
> IAB member. If the Nomcom declines to nominate a replacement as=
=20
> part of the annual process, the IAB may, at any time after the=20
> confirmation of the departing member, ask the Nomcom to  fill
> the slot using mid-term procedures.

Is this whole section only intended to apply during the annual
process?  If so, I think that should be more explicit.

If not, then exception (a) should probably indicate that it only
applies during the annual process and/or when more than N IAB
positions are simultaneously being filled.

Otherwise, it is still ambiguous what procedure should be used
if an IAB member is moved to the IESG to fill an interim vacancy.
I _think_ that the WG intends that the IAB position thus vacated
would be filled using the full interim vacancy process...

Margaret

From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 17:45: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 <0HNY00B04CGKCX@eListX.com> (original mail from david.putzolu@intel.com)
 ; Thu, 06 Nov 2003 17:43:32 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00B01CGJCV@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 17:43:32 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00B01CGJCU@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 17:43:31 -0500 (EST)
Received: from hermes.py.intel.com (hermes.py.intel.com [146.152.216.3])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNY006IRCGJY0@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 17:43:31 -0500 (EST)
Received: from petasus.py.intel.com (petasus.py.intel.com [146.152.221.4])
	by hermes.py.intel.com
 (8.12.9-20030918-01/8.12.9/d: outer.mc,v 1.66 2003/05/22 21:17:36 rfjohns1 Exp
 $) with ESMTP id hA6MggVi026574	for <ietf-nomcom@lists.elistx.com>; Thu,
 06 Nov 2003 22:42:42 +0000 (GMT)
Received: from orsmsxvs040.jf.intel.com
 (orsmsxvs040.jf.intel.com [192.168.65.206])
	by petasus.py.intel.com (8.12.9-20030918-01/8.11.6/d: large-inner.mc,v 1.5
 2003/10/14 21:47:05 root Exp $) with SMTP id hA6Mfm0g019872	for
 <ietf-nomcom@lists.elistx.com>; Thu, 06 Nov 2003 22:42:05 +0000 (GMT)
Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56])
 by orsmsxvs040.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2003110614424026563
 ; Thu, 06 Nov 2003 14:42:40 -0800
Received: from orsmsx409.amr.corp.intel.com ([192.168.65.58])
 by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.5329); Thu,
 06 Nov 2003 14:42:40 -0800
Date: Thu, 06 Nov 2003 14:42:40 -0800
From: "Putzolu, David" <david.putzolu@intel.com>
Subject: RE: Proposals for closing open issues
To: Margaret.Wasserman@nokia.com, mstjohns@mindspring.com, avri@acm.org,
 ietf-nomcom@lists.elistx.com
Message-id: <52D13A805349A249960B9943E5590BD881F697@orsmsx409.jf.intel.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: QUOTED-PRINTABLE
Thread-Topic: Proposals for closing open issues
Thread-Index: AcOkhVlOStv8rI9+T7uDePoSAfpXMAAF2uRwAAPG4GA=
content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
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>
X-OriginalArrivalTime: 06 Nov 2003 22:42:40.0719 (UTC)
 FILETIME=[48FFA5F0:01C3A4B7]

> > Rationale:  While the information is important for the IETF=20
> > participants to understand the choices, publishing it prior to th=
e=20
> > nomcom making a choice may result less than useful public discuss=
ion

> > of that criteria and thrashing (as in "page thrashing") of the
process.
>=20
> Rationale: I believe that it would valuable for the community to=
=20
> provide feedback on the qualifications required for leadership=20
> positions _before_ the leaders are chosen to fill them.  I also=
=20
> think that posting the qualifications might help the community
> to identify and represent qualified nominees.

I agree with the point above.  Also,  the feedback/"thrashing"=20
given might contain useful input to the decision making process.

Cheers,
David

From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 18:15: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 <0HNY00D04DRHI0@eListX.com> (original mail from harald@alvestrand.no); Thu,
 06 Nov 2003 18:11:41 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00D01DRGHW@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 18:11:41 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00D01DRGHU@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 18:11:40 -0500 (EST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNY00B8IDRF6A@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 18:11:40 -0500 (EST)
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP	id 5E06661B8F; Fri,
 07 Nov 2003 00:10:49 +0100 (CET)
Date: Thu, 06 Nov 2003 15:10:47 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
Subject: Re: IESG Issue 2 (publication of requirements)
In-reply-to: <6.0.0.22.2.20031106112812.035fff48@pop.mindspring.com>
To: Michael StJohns <mstjohns@mindspring.com>, Avri Doria <avri@acm.org>,
 ietf-nomcom@lists.elistx.com
Message-id: <99683226.1068131447@halvestr-w2k1>
MIME-version: 1.0
X-Mailer: Mulberry/3.1.0b9 (Win32)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
References: <1676720E-1036-11D8-817E-000393CC2112@acm.org>
 <6.0.0.22.2.20031106112812.035fff48@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>

I disagree with Mike.

I think publication of the requirements at call for nomination time is 
useful. The IESG and IAB is responsible for wording them; once they're 
published, Nomcom has no responsibility for them, and the IESG & IAB can't 
call them back - I think that's good.

I support the suggested resolution.

--On 6. november 2003 11:44 -0500 Michael StJohns <mstjohns@mindspring.com> 
wrote:

>> DISCUSSION SO FAR:   5 comments
>>
>> The information should not be confidential.  It should be published.
>
> Specifically, it should be published as part of the announcement
> information, rather than as part of the solicitation for nominations.
>
> Rationale:  While the information is important for the IETF participants
> to understand the choices, publishing it prior to the nomcom making a
> choice may result less than useful public discussion of that criteria and
> thrashing (as in "page thrashing") of the process.
>
>
>> Recommended wording change submitted on the list:
>>
>> OLD NEW:
>>
>>    14.  The Chair obtains the list of IESG and IAB positions to be
>>           reviewed and a description of the desirable qualifications for
>>
>>         those positions. This information is announced, along with a
>>         solicitation for names of volunteers from the IETF community
>>         willing to serve on the nominating committee.
>>
>> NEW:
>>
>>    14.  The Chair obtains the list of IESG and IAB positions to be
>>           reviewed and a description of the desirable qualifications for
>>            those positions. This information is announced on
>>            ietf-announce@ietf.org, along with a solicitation for names
>>            of volunteers from the IETF community willing to serve on
>>           the nominating committee.
>>
>>
>> Is this wording acceptable?
>
> No - see above.
>





From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 18:35: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 <0HNY00E04EH4UK@eListX.com> (original mail from gih@telstra.net); Thu,
 06 Nov 2003 18:27:04 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00E01EH3UG@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 18:27:03 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00E01EH3UD@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 18:27:03 -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 <0HNY00BEZEH16A@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 18:27:02 -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 hA6NPwRe092813; Fri,
 07 Nov 2003 10:26:00 +1100 (EST envelope-from gih@telstra.net)
Date: Fri, 07 Nov 2003 10:24:29 +1100
From: Geoff Huston <gih@telstra.net>
Subject: Re: IESG Issue 2 (publication of requirements)
In-reply-to: <99683226.1068131447@halvestr-w2k1>
X-Sender: gih@kahuna.telstra.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>,
 Michael StJohns <mstjohns@mindspring.com>, Avri Doria <avri@acm.org>,
 ietf-nomcom@lists.elistx.com
Message-id: <5.1.0.14.2.20031107101843.00bd2da8@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: <6.0.0.22.2.20031106112812.035fff48@pop.mindspring.com>
 <1676720E-1036-11D8-817E-000393CC2112@acm.org>
 <6.0.0.22.2.20031106112812.035fff48@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>

A countervailing view is that the generation of the current
requirements in the IETF leadership and the associated
desireable qualifications for the vacant positions
rests with the Nomcom as an outcome of its interactions with
the community during its consultative process.

At the very least the Nomcom should not interpret any such
statement of 'desireable qualifications" as being a fixed constraint
placed upon the process, and the Nomcom should be able to
refine such an input to match what it is hearing from the broader
IETF community as to current requirements and associated
desireable qualifications for vacant positions.

Geoff


At 03:10 PM 6/11/2003 -0800, Harald Tveit Alvestrand wrote:
>I disagree with Mike.
>
>I think publication of the requirements at call for nomination time is 
>useful. The IESG and IAB is responsible for wording them; once they're 
>published, Nomcom has no responsibility for them, and the IESG & IAB can't 
>call them back - I think that's good.
>
>I support the suggested resolution.
>
>--On 6. november 2003 11:44 -0500 Michael StJohns 
><mstjohns@mindspring.com> wrote:
>
>>>DISCUSSION SO FAR:   5 comments
>>>
>>>The information should not be confidential.  It should be published.
>>
>>Specifically, it should be published as part of the announcement
>>information, rather than as part of the solicitation for nominations.
>>
>>Rationale:  While the information is important for the IETF participants
>>to understand the choices, publishing it prior to the nomcom making a
>>choice may result less than useful public discussion of that criteria and
>>thrashing (as in "page thrashing") of the process.
>>
>>
>>>Recommended wording change submitted on the list:
>>>
>>>OLD NEW:
>>>
>>>    14.  The Chair obtains the list of IESG and IAB positions to be
>>>           reviewed and a description of the desirable qualifications for
>>>
>>>         those positions. This information is announced, along with a
>>>         solicitation for names of volunteers from the IETF community
>>>         willing to serve on the nominating committee.
>>>
>>>NEW:
>>>
>>>    14.  The Chair obtains the list of IESG and IAB positions to be
>>>           reviewed and a description of the desirable qualifications for
>>>            those positions. This information is announced on
>>>            ietf-announce@ietf.org, along with a solicitation for names
>>>            of volunteers from the IETF community willing to serve on
>>>           the nominating committee.
>>>
>>>
>>>Is this wording acceptable?
>>
>>No - see above.
>
>
>
>
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.elistx.com/subscribe>




From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 19:05: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 <0HNY00G04FWPOJ@eListX.com> (original mail from harald@alvestrand.no); Thu,
 06 Nov 2003 18:58:01 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00G01FWPOH@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 18:58:01 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00G01FWOOG@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 18:58:00 -0500 (EST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNY00DDPFWOD0@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 18:58:00 -0500 (EST)
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP	id E9AF661B8F; Fri,
 07 Nov 2003 00:57:08 +0100 (CET)
Date: Thu, 06 Nov 2003 15:57:06 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
Subject: Re: IESG Issue 2 (publication of requirements)
In-reply-to: <5.1.0.14.2.20031107101843.00bd2da8@kahuna.telstra.net>
To: Geoff Huston <gih@telstra.net>, Michael StJohns <mstjohns@mindspring.com>,
 Avri Doria <avri@acm.org>, ietf-nomcom@lists.elistx.com
Message-id: <102462713.1068134226@halvestr-w2k1>
MIME-version: 1.0
X-Mailer: Mulberry/3.1.0b9 (Win32)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
References: <6.0.0.22.2.20031106112812.035fff48@pop.mindspring.com>
 <1676720E-1036-11D8-817E-000393CC2112@acm.org>
 <6.0.0.22.2.20031106112812.035fff48@pop.mindspring.com>
 <5.1.0.14.2.20031107101843.00bd2da8@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>



--On 7. november 2003 10:24 +1100 Geoff Huston <gih@telstra.net> wrote:

> A countervailing view is that the generation of the current
> requirements in the IETF leadership and the associated
> desireable qualifications for the vacant positions
> rests with the Nomcom as an outcome of its interactions with
> the community during its consultative process.

I agree, and disagree that it is countervailing :-)
The nomcom is responsible for using *its* judgment.
But I think that what the IESG and IAB tells them should be public, and 
made public at the time it's written, not 6 months later.

> At the very least the Nomcom should not interpret any such
> statement of 'desireable qualifications" as being a fixed constraint
> placed upon the process, and the Nomcom should be able to
> refine such an input to match what it is hearing from the broader
> IETF community as to current requirements and associated
> desireable qualifications for vacant positions.

Yes.
And the results of that refinement need to be reflected in the "testament" 
at the end of the process.




From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 19: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 <0HNY00H04GWDRZ@eListX.com> (original mail from gih@telstra.net); Thu,
 06 Nov 2003 19:19:25 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00H01GWDRX@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 19:19:25 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00H01GWCRW@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 19:19:24 -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 <0HNY00DGNGWBD0@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 19:19:24 -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 hA70IQRe094940; Fri,
 07 Nov 2003 11:18:28 +1100 (EST envelope-from gih@telstra.net)
Date: Fri, 07 Nov 2003 11:14:41 +1100
From: Geoff Huston <gih@telstra.net>
Subject: Re: IESG Issue 2 (publication of requirements)
In-reply-to: <102462713.1068134226@halvestr-w2k1>
X-Sender: gih@kahuna.telstra.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>,
 Michael StJohns <mstjohns@mindspring.com>, Avri Doria <avri@acm.org>,
 ietf-nomcom@lists.elistx.com
Message-id: <5.1.0.14.2.20031107111312.00bbff90@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.20031107101843.00bd2da8@kahuna.telstra.net>
 <6.0.0.22.2.20031106112812.035fff48@pop.mindspring.com>
 <1676720E-1036-11D8-817E-000393CC2112@acm.org>
 <6.0.0.22.2.20031106112812.035fff48@pop.mindspring.com>
 <5.1.0.14.2.20031107101843.00bd2da8@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 03:57 PM 6/11/2003 -0800, Harald Tveit Alvestrand wrote:


>--On 7. november 2003 10:24 +1100 Geoff Huston <gih@telstra.net> wrote:
>
>>A countervailing view is that the generation of the current
>>requirements in the IETF leadership and the associated
>>desireable qualifications for the vacant positions
>>rests with the Nomcom as an outcome of its interactions with
>>the community during its consultative process.
>
>I agree, and disagree that it is countervailing :-)
>The nomcom is responsible for using *its* judgment.
>But I think that what the IESG and IAB tells them should be public, and 
>made public at the time it's written, not 6 months later.

fair enough - I can (and do) agree with this.

>>At the very least the Nomcom should not interpret any such
>>statement of 'desireable qualifications" as being a fixed constraint
>>placed upon the process, and the Nomcom should be able to
>>refine such an input to match what it is hearing from the broader
>>IETF community as to current requirements and associated
>>desireable qualifications for vacant positions.
>
>Yes.
>And the results of that refinement need to be reflected in the "testament" 
>at the end of the process.


precisely!

   Geoff




From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 19:55: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 <0HNY00J04I6ZKI@eListX.com> (original mail from mstjohns@mindspring.com)
 ; Thu, 06 Nov 2003 19:47:23 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00J01I6ZKG@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 19:47:23 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00J01I6YKF@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 19:47:22 -0500 (EST)
Received: from razorbill.mail.pas.earthlink.net
 (razorbill.mail.pas.earthlink.net [207.217.121.248])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNY00H8HI6YOI@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 19:47:22 -0500 (EST)
Received: from pcp06939638pcs.nrockv01.md.comcast.net
 ([69.138.17.182] helo=STJOHNS-LAPTOP2.mindspring.com)
	by razorbill.mail.pas.earthlink.net with asmtp (TLSv1:RC4-SHA:128)
	(Exim 3.33 #1)	id 1AHuld-0002gf-00; Thu, 06 Nov 2003 16:46:26 -0800
Date: Thu, 06 Nov 2003 19:46:26 -0500
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: IESG Issue 2 (publication of requirements)
In-reply-to: <5.1.0.14.2.20031107111312.00bbff90@kahuna.telstra.net>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
To: Geoff Huston <gih@telstra.net>,
 Harald Tveit Alvestrand <harald@alvestrand.no>, Avri Doria <avri@acm.org>,
 ietf-nomcom@lists.elistx.com
Message-id: <6.0.0.22.2.20031106193307.02236058@pop.mindspring.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Content-type: text/plain; format=flowed; charset=us-ascii
X-ELNK-Trace:
 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4dd4d56ea421c5f28e312a0fdcb6e95184350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
References: <5.1.0.14.2.20031107101843.00bd2da8@kahuna.telstra.net>
 <6.0.0.22.2.20031106112812.035fff48@pop.mindspring.com>
 <1676720E-1036-11D8-817E-000393CC2112@acm.org>
 <6.0.0.22.2.20031106112812.035fff48@pop.mindspring.com>
 <5.1.0.14.2.20031107101843.00bd2da8@kahuna.telstra.net>
 <5.1.0.14.2.20031107111312.00bbff90@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 07:14 PM 11/6/2003, Geoff Huston wrote:
>At 03:57 PM 6/11/2003 -0800, Harald Tveit Alvestrand wrote:
>
>
>>--On 7. november 2003 10:24 +1100 Geoff Huston <gih@telstra.net> wrote:
>>
>>>A countervailing view is that the generation of the current
>>>requirements in the IETF leadership and the associated
>>>desireable qualifications for the vacant positions
>>>rests with the Nomcom as an outcome of its interactions with
>>>the community during its consultative process.
>>
>>I agree, and disagree that it is countervailing :-)
>>The nomcom is responsible for using *its* judgment.
>>But I think that what the IESG and IAB tells them should be public, and 
>>made public at the time it's written, not 6 months later.
>
>fair enough - I can (and do) agree with this.


*sigh* If they're made public at the beginning, then one or more of the 
IETF will feel that they need to provide input into that set of 
requirements, then there will be a very large discussion and if even one of 
the comments was ignored or excluded (or appeared to be ignored or 
excluded), then the selection process will be appealed and we really don't 
want that.

The general input from the membership should come in through the Nomcom WG 
and the Nomcom and the Nomcom's interaction with the membership.  The 
IAB/IESG guidance should not be subject to public debate or modification 
(specifically because it is the IAB's and IESG's guidance and not the 
membership's) and I see no way short of keeping it confidential until the 
termination of the process to enforce this.

This in no way is meant to prevent the Nomcom from publishing criteria 
without attribution, but frankly I'm not sure they would want to risk the 
same interaction as above.


>>>At the very least the Nomcom should not interpret any such
>>>statement of 'desireable qualifications" as being a fixed constraint
>>>placed upon the process, and the Nomcom should be able to
>>>refine such an input to match what it is hearing from the broader
>>>IETF community as to current requirements and associated
>>>desireable qualifications for vacant positions.
>>
>>Yes.
>>And the results of that refinement need to be reflected in the 
>>"testament" at the end of the process.
>
>
>precisely!
>
>   Geoff

Yup....


From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 21: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 <0HNY00004LF0UN@eListX.com> (original mail from jwkckid1@ix.netcom.com)
 ; Thu, 06 Nov 2003 20:57:00 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00001LEZUK@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 20:56:59 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00001LEZUJ@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 20:56:59 -0500 (EST)
Received: from tisch.mail.mindspring.net
 (tisch.mail.mindspring.net [207.69.200.157])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNY00HM1LEZOI@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 20:56:59 -0500 (EST)
Received: from 1cust89.tnt36.dfw9.da.uu.net ([67.234.81.89] helo=ix.netcom.com)
	by tisch.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 1AHvr6-0005sj-00; Thu, 06 Nov 2003 20:56:09 -0500
Date: Thu, 06 Nov 2003 19:53:36 -0800
From: Jeff Williams <jwkckid1@ix.netcom.com>
Subject: Re: Proposals for closing open issues
To: Margaret.Wasserman@nokia.com
Cc: mstjohns@mindspring.com, avri@acm.org, ietf-nomcom@lists.elistx.com
Message-id: <3FAB173F.4401DD5D@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:
 <E320A8529CF07E4C967ECC2F380B0CF902443F85@bsebe001.americas.nokia.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>

Margaret and all,

  I agree with Margaret  here.  I would add that what the minimum
qualifications should be delineated as well as verification by a neutral
third party as to the validity of the potential candidates claimed
qualifications listed....

Margaret.Wasserman@nokia.com wrote:

> Posting as an interested individual:
>
> > >The information should not be confidential.  It should be published.
> >
> > Specifically, it should be published as part of the announcement
> > information, rather than as part of the solicitation for nominations.
>
> I disagree.  I think that the qualifications should be posted as part
> of the call for nominations.
>
> > Rationale:  While the information is important for the IETF
> > participants to understand the choices, publishing it prior to the
> > nomcom making a choice may result less than useful public discussion
> > of that criteria and thrashing (as in "page thrashing") of the process.
>
> Rationale: I believe that it would valuable for the community to
> provide feedback on the qualifications required for leadership
> positions _before_ the leaders are chosen to fill them.  I also
> think that posting the qualifications might help the community
> to identify and represent qualified nominees.
>
> Margaret
>
> ----------------------------------------------------------------
> 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 134k members/stakeholders strong!)
"Be precise in the use of words and expect precision from others" -
    Pierre Abelard
"If the probability be called P; the injury, L; and the burden, B; liability
depends upon whether B is less than L multiplied by P: i.e., whether B is
less than PL." United States v. Carroll Towing (159 F.2d 169 [2d Cir. 1947]
===============================================================
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 Thu Nov  6 21: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 <0HNY00004LKAZU@eListX.com> (original mail from sob@harvard.edu); Thu,
 06 Nov 2003 21:00:10 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00001LKAZS@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 21:00:10 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00001LK9ZR@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 21:00:09 -0500 (EST)
Received: from newdev (newdev.eecs.harvard.edu [140.247.60.212])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNY00KFKLK90K@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 21:00:09 -0500 (EST)
Received: by newdev (Postfix, from userid 501)	id 1CF636D9D7; Thu,
 06 Nov 2003 20:59:22 -0500 (EST)
Date: Thu, 06 Nov 2003 20:59:22 -0500 (EST)
From: sob@harvard.edu (Scott Bradner)
Subject: Re: IESG Issue 2 (publication of requirements)
To: ietf-nomcom@lists.elistx.com
Message-id: <20031107015922.1CF636D9D7@newdev>
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>

agree also - this is just the right idea and the text should
be tweaked to say:
	1/ the IESG/IAB generated criteria  should be made public
	   when they are sent to the nomcom
	2/ the nomcom uses this as input but can come up with its
	   own as it hears from the community
	3/ the nomcom should publish at the end what the
	   criteria  it used were 
Scott

------------------------------------------------------------
> >>A countervailing view is that the generation of the current
> >>requirements in the IETF leadership and the associated
> >>desireable qualifications for the vacant positions
> >>rests with the Nomcom as an outcome of its interactions with
> >>the community during its consultative process.
> >
> >I agree, and disagree that it is countervailing :-)
> >The nomcom is responsible for using *its* judgment.
> >But I think that what the IESG and IAB tells them should be public, and 
> >made public at the time it's written, not 6 months later.
> 
> fair enough - I can (and do) agree with this.
> 
> >>At the very least the Nomcom should not interpret any such
> >>statement of 'desireable qualifications" as being a fixed constraint
> >>placed upon the process, and the Nomcom should be able to
> >>refine such an input to match what it is hearing from the broader
> >>IETF community as to current requirements and associated
> >>desireable qualifications for vacant positions.
> >
> >Yes.
> >And the results of that refinement need to be reflected in the "testament" 
> >at the end of the process.
> 
> 
> precisely!
> 

From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 21:05: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 <0HNY00104LOV9H@eListX.com> (original mail from sob@harvard.edu); Thu,
 06 Nov 2003 21:02:55 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00101LOU9E@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 21:02:54 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00101LOU9D@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 21:02:54 -0500 (EST)
Received: from newdev (newdev.eecs.harvard.edu [140.247.60.212])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNY00HOULOTOI@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 21:02:54 -0500 (EST)
Received: by newdev (Postfix, from userid 501)	id EB98B6D9F6; Thu,
 06 Nov 2003 21:02:06 -0500 (EST)
Date: Thu, 06 Nov 2003 21:02:06 -0500 (EST)
From: sob@harvard.edu (Scott Bradner)
Subject: Re: IESG Issue 2 (publication of requirements)
To: ietf-nomcom@lists.elistx.com
Message-id: <20031107020206.EB98B6D9F6@newdev>
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>


mike sez:
> *sigh* If they're made public at the beginning, then one or more of the 
> IETF will feel that they need to provide input into that set of 
> requirements

and they should communicate that input to the nomcom

Scott

From ietf-nomcom-errors@lists.elistx.com Thu Nov  6 21:45: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 <0HNY00304NIC7J@eListX.com> (original mail from jwkckid1@ix.netcom.com)
 ; Thu, 06 Nov 2003 21:42:13 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00301NIB7H@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 06 Nov 2003 21:42:12 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00301NIB7G@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 06 Nov 2003 21:42:11 -0500 (EST)
Received: from smtp10.atl.mindspring.net
 (smtp10.atl.mindspring.net [207.69.200.246])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNY00213NIBNN@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 06 Nov 2003 21:42:11 -0500 (EST)
Received: from 1cust89.tnt36.dfw9.da.uu.net ([67.234.81.89] helo=ix.netcom.com)
	by smtp10.atl.mindspring.net with esmtp (Exim 3.33 #1)
	id 1AHwYt-00074E-00; Thu, 06 Nov 2003 21:41:23 -0500
Date: Thu, 06 Nov 2003 20:38:50 -0800
From: Jeff Williams <jwkckid1@ix.netcom.com>
Subject: Re: IESG Issue 2 (publication of requirements)
To: Scott Bradner <sob@harvard.edu>
Cc: ietf-nomcom@lists.elistx.com
Message-id: <3FAB21DA.3A332AEF@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: <20031107015922.1CF636D9D7@newdev>
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>

Scott and all,

  I don't like your #2 because there is no minimum standard established,
and therefore making your #3 invalid or at least questionable...

  However as I recall, and I might be mistaken, we have had
this debate/discussion before.

Scott Bradner wrote:

> agree also - this is just the right idea and the text should
> be tweaked to say:
>         1/ the IESG/IAB generated criteria  should be made public
>            when they are sent to the nomcom
>         2/ the nomcom uses this as input but can come up with its
>            own as it hears from the community
>         3/ the nomcom should publish at the end what the
>            criteria  it used were
> Scott
>
> ------------------------------------------------------------
> > >>A countervailing view is that the generation of the current
> > >>requirements in the IETF leadership and the associated
> > >>desireable qualifications for the vacant positions
> > >>rests with the Nomcom as an outcome of its interactions with
> > >>the community during its consultative process.
> > >
> > >I agree, and disagree that it is countervailing :-)
> > >The nomcom is responsible for using *its* judgment.
> > >But I think that what the IESG and IAB tells them should be public, and
> > >made public at the time it's written, not 6 months later.
> >
> > fair enough - I can (and do) agree with this.
> >
> > >>At the very least the Nomcom should not interpret any such
> > >>statement of 'desireable qualifications" as being a fixed constraint
> > >>placed upon the process, and the Nomcom should be able to
> > >>refine such an input to match what it is hearing from the broader
> > >>IETF community as to current requirements and associated
> > >>desireable qualifications for vacant positions.
> > >
> > >Yes.
> > >And the results of that refinement need to be reflected in the "testament"
> > >at the end of the process.
> >
> >
> > precisely!
> >
>
> ----------------------------------------------------------------
> 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 134k members/stakeholders strong!)
"Be precise in the use of words and expect precision from others" -
    Pierre Abelard
"If the probability be called P; the injury, L; and the burden, B; liability
depends upon whether B is less than L multiplied by P: i.e., whether B is
less than PL." United States v. Carroll Towing (159 F.2d 169 [2d Cir. 1947]
===============================================================
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 Fri Nov  7 00:29: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 <0HNY00E04UY43O@eListX.com> (original mail from kre@munnari.OZ.AU); Fri,
 07 Nov 2003 00:22:52 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HNY00E01UY43M@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Fri,
 07 Nov 2003 00:22:52 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HNY00E01UY33F@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Fri, 07 Nov 2003 00:22:51 -0500 (EST)
Received: from ratree.psu.ac.th (ratree.psu.ac.th [202.12.73.3])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HNY008G2UY0T8@eListX.com>
 for ietf-nomcom@lists.elistx.com; Fri, 07 Nov 2003 00:22:50 -0500 (EST)
Received: from delta.cs.mu.OZ.AU ([172.30.0.189])
	by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id hA75LoB01341; Fri,
 07 Nov 2003 12:21:53 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id hA74sdw01331; Fri,
 07 Nov 2003 11:54:39 +0700 (ICT)
Date: Fri, 07 Nov 2003 11:54:39 +0700
From: Robert Elz <kre@munnari.OZ.AU>
Subject: Re: IESG Issue 2 (publication of requirements)
In-reply-to: <6.0.0.22.2.20031106193307.02236058@pop.mindspring.com>
To: Michael StJohns <mstjohns@mindspring.com>
Cc: Geoff Huston <gih@telstra.net>,
 Harald Tveit Alvestrand <harald@alvestrand.no>, Avri Doria <avri@acm.org>,
 ietf-nomcom@lists.elistx.com
Message-id: <17710.1068180879@munnari.OZ.AU>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
References: <6.0.0.22.2.20031106193307.02236058@pop.mindspring.com>
 <5.1.0.14.2.20031107101843.00bd2da8@kahuna.telstra.net>
 <6.0.0.22.2.20031106112812.035fff48@pop.mindspring.com>
 <1676720E-1036-11D8-817E-000393CC2112@acm.org>
 <6.0.0.22.2.20031106112812.035fff48@pop.mindspring.com>
 <5.1.0.14.2.20031107101843.00bd2da8@kahuna.telstra.net>
 <5.1.0.14.2.20031107111312.00bbff90@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>

    Date:        Thu, 06 Nov 2003 19:46:26 -0500
    From:        Michael StJohns <mstjohns@mindspring.com>
    Message-ID:  <6.0.0.22.2.20031106193307.02236058@pop.mindspring.com>

  | requirements, then there will be a very large discussion and if even one of 
  | the comments was ignored or excluded (or appeared to be ignored or 
  | excluded), then the selection process will be appealed and we really don't 
  | want that.

To quote the draft ...

   The following rules apply to the process.

   1.  The results of this process are final and binding.  There is no
       appeal.

This is why we have the confirmation process (any "issues" are
dealt with there).

  | The general input from the membership should come in through the Nomcom WG 
  | and the Nomcom and the Nomcom's interaction with the membership.

Of course.

  | The IAB/IESG guidance

We're not discussing guidance here, but qualification requirements.

The IAB and IESG, and their members individually if they desire, just
like everyone else, are free to provide additional "guidance" to the
nomcom.

The approach that has been agreed by everyone else on this point seems
correct to me.

kre


From ietf-nomcom-errors@lists.elistx.com Thu Nov 27 03:05:18 2003
Return-Path: <ietf-nomcom-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HP000M043S7BB@eListX.com> (original mail from avri@acm.org); Thu,
 27 Nov 2003 03:04:55 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HP000M013S6B9@eListX.com> for
 ietf-nomcom@elist.lists.elistx.com (ORCPT ietf-nomcom@lists.elistx.com); Thu,
 27 Nov 2003 03:04:54 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HP000M013S6B8@eListX.com> for ietf-nomcom@elist.lists.elistx.com
 (ORCPT ietf-nomcom@lists.elistx.com); Thu, 27 Nov 2003 03:04:54 -0500 (EST)
Received: from psg.com (psg.com [147.28.0.62])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HP000II63S4D1@eListX.com>
 for ietf-nomcom@lists.elistx.com; Thu, 27 Nov 2003 03:04:53 -0500 (EST)
Received: from [147.28.0.62] (helo=acm.org)
	by psg.com with esmtp (Exim 4.24; FreeBSD 4.9)
	id 1APH7t-000Dsd-FU	for ietf-nomcom@lists.elistx.com; Thu,
 27 Nov 2003 08:03:50 +0000
Date: Thu, 27 Nov 2003 17:03:17 +0900
From: Avri Doria <avri@acm.org>
Subject: Draft minutes from Nomcom Meeting
To: ietf-nomcom@lists.elistx.com
Message-id: <28AB1932-20B0-11D8-A38A-000393CC2112@acm.org>
MIME-version: 1.0 (Apple Message framework v553)
X-Mailer: Apple Mail (2.553)
Content-type: text/plain; format=flowed; 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>

Nomcom, Wednesday 9-11:30
Minutes taken by Melinda Shore

Agenda:
Agenda review
Review of changes to 2727bis
Review of proposals for closing open issues
Discussion of when 2727bis becomes normative

[Trying to close down wg]

no changes to agenda
-----------
Jim Galvin reviewed changes in 2727bis-08.

Issue 11 (and 23): should clarifying text indicate that the
Confirmed candidates, chosen by the standard process (as
opposed to midterm appointments) be expected to serve at
least two years.  mid-term appointments may serve less than
two years

Issue 8: when a new area is created one AD may serve for a
longer term (to offset terms).  Change specifies maximum
period of 3 years.  In the past nomcom can't choose term
length - they're told by the requesting body (IESG or IAB)
[Scott Bradner and Mike St Johns].  Disputed by Avri and
Jim.  2727bis has said for a long time that nomcom can set
duration.  Marshall asked about how firm this is - how do
the checks and balances work?  Scott B. said that the IESG
has decided in the past - the issue here is lack of clarity
in the document.  Mike said that when two slots are open of
different length, the nomcom chooses which candidate fills
which slot, but the requesting body is responsible for
requesting the durations in the first place.  Jim asked if
the authority to adjust the term length rests only with the
requesting body, and Scott said "yes."  Harald said it's a
distinction without a difference and that reasonable people
will do the right thing without specific guidance - that the
document does not need clarification.  Scott said that he's
not asking for a change.

Issue 25: explicitly declare that the ISOC board of trustees
may provide a liaison

Issue 9: clarify what is meant by "approved by all members."

Issue 7: allows for the possibility that the NOMCOM may
replace a member no longer participating

Issue 5: adds that the nomcom talk to wg chairs

Issue 4: adds that the recall signers should be verified for
eligibility

Bunch of editorial changes

------------

Proposals for closing open issues

1. Release of qualification statements

objection was description of desirable qualifications was to
be disseminated.  Issue was "when."  should be during
announcement or during solicitation?  Mike St John wants to
withhold communication until done (as validation) - doesn't
want public discussion during process, thinks it will create
appealable problems.  Jim Galvin asked if it would be okay
to make editorial changes.  Also, what is meaning of
information?  Is it normative, and how is it used by nomcom?
Scott said that the information should be put out early, and
that it's important for the community to know what the IESG
and IAB suggested as criteria.  Harald also disagrees with
Mike, asked if it would be correct to say that the
description is from the IESG and IAB, identifying the
source?  Lucy Lynch said it's chicken/egg problem, that if
the information is mandatory it should be exposed early and
that if it's advisory there's more wiggle room.  Mike:
"expertise" may be a better term than "qualifications."
Avri asked if "expertise" would obviate Mike's objections.
Mike said he doesn't feel that strongly and would be willing
to be overridden.  If there's no benefit from exposing the
information, why do it?  Scott argued again for early
release of the information, said community may not agree
with the IESG about qualification and that dialog should be
possible.  Joel pointed out that the text already says that
the qualifications are "desirable", not mandatory.  Jim said
that the context is allowing people to choose whether they'd
like to serve on nomcom or be considered for open I*
positions.  Mike said the community should be asked for
input for qualifications.

Agreed to suggested change

2. nomcom causes midterm vacancies

nomcom may propose moving a serving I* from one position to
another.  issue is whether mid-term procedures should be
used to replace mover.  Mike asked to be aware of dependency
on rule saying that no-one may serve on both IESG and IAB
simultaneously.  IESG and IAB chairs do the requesting of
the Executive Director, who's responsible for asking the
nomcom to select the replacement.  Harald and Scott think
it's more specific than necessary, ask that the stuff about
chair requests be dropped.  Jim asked if the issue is that
the text in -08 is about making sure that mid-term vacancy
rules are applied to the letter, Mike pointed to Ted Hardie
experience - he may have been able to serve on both, but
voluntarily stepped down.  Nomcom cannot by itself choose to
fill a slot that it's creating.  Also distinguishes between
IAB, where open position need not be announced, and IESG,
where open position must be announced.  Text in -08 applies
only to openings created by the nomcom on the IAB.

Agreed tosuggested change

3. liaison initiation of problem resolution process

When the liaison goes to their respective bodies, do they
reveal information that's confidential to nomcom.  Proposal
is to have liaisons discuss among themselves and the chair
rather than going back to their bodies.

Agreed to suggested change

10. nomcom member recall

replaces "quorum" with "2/3".  Doesn't explicitly exclude
the chair, should.  Mikes says should exclude person under
consideration for recall.  Quorum is defined elsewhere in
the text as 75%.

Agreed to suggested change

17, must or should for completion of nomcom process

Old text says the confirmatin process must be completed at
least one month prior to first IETF.  Suggested to change
the must to should proposal is to leave as is.  Scott says
that must implies existence of recourse and there is none.
Joel said job is "do it."  Mike said problem with text is
that it's binding on process, not people, and suggested
changing to musts on people.  Scott suggested changing to
"due dates" rather than musts.

Will be taken back to the list ("is due by").

24.  Term changeover timing for IAB

What does overlap mean for IAB, where there are no specific
slots?  When does IAB seat start, when does it end?  The
delta is the addition of IESG for existing text, addition of
IAB sentence at end.  How does this apply to midterm
vacancies?  Jim said handled elsewhere - that's why it says
"sitting members."  Mike suggests specifying that the
proposed text is for sitting candidates, adding clause for
midterm replacements.  Scott suggested that midterm
appointments become effective as soon as possible after
confirmation.

Change is agreed to, with editorial clarifications.

---------------

When does 27272bis become normative?

Proposal: once published.  Current nomcom is free to use
current BCP or new one for current process, but use new
process for new midterm vacancies.  Scott said that it
should wait for publication, suggested that it become
effective when IESG approves it or when ISOC board accepts
it.  Joel says the question of when it becomes effective is
out of the hands of the working group.  Mike said the
problem is that the nomcom may not conflict the old stuff,
must document any changes to procedure.  Jim said it might
be useful for IESG to make general statement about process
documents.  Mike thinks the document should include a
statement about when it becomes normative.  Scott said that
it would be harmful, but that it would be better for the
IEsG to make a statement.

Is the second bullet acceptable (current nomcom is free to
use current or bis for any current process where there is no
conflict)?  Yes

Should it only be sent as a recommendation to IETF chair, or
should it go in the document?  Goes as a recommendation to
chair.

Mike asked if the recommendation is binding.  Joel said he
hopes the IESG will make a statement about this when then
document is announced.

Does the room agree that the IESG should make a statement?
yes

Scott clarified that we're not sending it to the IETF chair,
but the area director for the general area.

-----------

The intention is to close down the group but keep the list
active once the document is approved by the IESG and
accepted by the ISOC board.  Scott said that according to
recent history, the wg would not go poof until the document
popped out of the RFC editor's queue.


