-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hallam-Baker, Phillip wrote: >>>Why can't we elect the WG chairs? Why can't we elect the ADs? >> >>... >> >>When the IETF pays for the 60% (80%, 100%, take your pick) of >>an AD's salary, they can elect ADs. Unfortunately, the >>current system is heavily biased towards keeping existing ADs >>- who, like career politicians, can secure financial support >>from their employers for continued participation based on >>their current position. Perhaps it's time for term limits ;-) > > > I have two problems with the current situation, the first is that the > ADs have very much less authority than their role requires. It is simply > not possible to have authority without accountability and the whole > point of NOMCON is to ensure that no AD or IAB member is ever > accountable to anyone. The committee that appoints them will not be the > committee that reappoints them. > > The second is that there is no way for the membership to tell the IESG > and IAB that they should stop dealling in the minutiae and instead focus > on the real problems facing the Internet which have nothing to do with > whether a draft that will soon be forgotten is well written or not. > > I want the IAB to be giving architectural leadership. ... If we beleive that the IESG or IAB _should_ act as a "program committee" (which I do not, but is a large part of their current behavior, IMO), then elections are not a useful solution. If we believe they should represent _us_, and help the participants of the IETF coordinate and promote issues that the participants of the IETF think are important (which I do), then elections and accountability might be very useful to consider. To me, the IAB's (or IESG's, or IRTF's, for that matter) "architectural leadership" would be based on coordinating the interests of various participants - i.e., representing _us_. If they want to show us a new direction, they can do it as citizens. Real leaders _lead_ by _doing_; pulpits are for preachers, and preachers aren't what we need here. Joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCXWMWE5f5cImnZrsRAs3UAJwKHjVYwfII3cfCNJk2v/grq2qfCACgy/J4 KDX7IM6Txan0khZam5bsgWg= =0DIM -----END PGP SIGNATURE----- _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf