The IETF Last Call resulted in a healthy discussion with many people
speaking. Some people think that the open list is the right thing to
do, but other people want to redesign the entire NomCom process from
a base set of principles. This message summarizes my view of the
consensus following
Ooops. I sent this on the wrong thread. The
draft-dawkins-nomcom-dont-wait document is approved, and it is in the
RFC Editor queue. This message was about the
draft-dawkins-nomcom-openlist document. I'll resend this message on
the proper thread so that people will be able to locate it with
On Fri, 5 Jun 2009, Russ Housley wrote:
...
The IETF Executive Director, who is part of the Secretariat, already has a
role in NomCom. The IETF Executive Director provides the requirements for
the open positions.
Would you be more comfortable if the Executive Director were named as the
Pekka:
- 'Nominating Committee Process: Earlier Announcement of Open Positions
and Solicitation of Volunteers'
draft-dawkins-nomcom-dont-wait-03.txt as a BCP
I have two issues with this.
1) This places a new responsibility at the feet of IETF secretariat.
That's a new actor (not
On Wed, 27 May 2009, The IESG wrote:
- 'Nominating Committee Process: Earlier Announcement of Open Positions
and Solicitation of Volunteers'
draft-dawkins-nomcom-dont-wait-03.txt as a BCP
I have two issues with this.
1) This places a new responsibility at the feet of IETF secretariat.
The IESG has received a request from an individual submitter to consider
the following document:
- 'Nominating Committee Process: Earlier Announcement of Open Positions
and Solicitation of Volunteers'
draft-dawkins-nomcom-dont-wait-03.txt as a BCP
The IESG plans to make a decision in the
