![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
I'm certainly silly enough to stand up and say such a thing if I thought it were true and if I thought that I had no other recourse.
An argument made in this thread is that nomcom is ineffective. I was assuming, perhaps incorrectly,that you subscribed to that view.
Most years, I put my name into the nomcom list. I've been on nomcom twice.
I believe in the process, but I also believe it needs significant changing.
The current design of the nomcom process works well when there is a large percentage of the volunteer pool that has extensive experience with both the technology and the IETF process. This makes it likely that a useful portion of the resulting nomcom will be savvy about IETF issues.
Over the years, that percentage has gone down dramatically. This has resulted in recent nomcoms that have very little real IETF process experience among the voting members.
When there is a pattern of concern, there is a problem that needs fixing.
So, I chose to cite a common rationale used by the nomcom ("there were no
other choices") and suggest that the regular occurrence of that rationale
is sufficient indication of a deep, serious problem that needs
addressing.
That we now are assured of knowing who is doing the veto merely means that we can engage in infinite, unproductive exchanges about their concerns. There is no way to really counter the veto, when it is silly, other than an appeal.
-- Jeff
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.