iasa-bcp-04: unanimity in section 3.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi.

After a bit more reflection and looking at the new text in
context, I think I'm actually pretty upset about

	"The IAOC attempts to reach all decisions unanimously.
	If the IAOC cannot achieve a unanimous decision, the
	IAOC decides by voting."

In the process of simplifying this text, something seems
to have gotten lost. It is usually a strong principle
around the IETF and in our style of decision-making that
we want people to to try really hard to see if a point
of agreement can be found.   The simplified text has
lost the notion of consensus short of unanimity.  So,
"if you aren't unanimous, go take votes" is, IMO, the
wrong formulation.  A better one would be "if you can't
reach consensus without voting, then by all means vote".

Unfortunately, this isn't quite trivial editorial nit-picking.
Let's assume that several choices are possible, and assume that
one of them, selected by whomever frames a motion first, is
proposed for adoption.  As that current text is written, if
that choice doesn't get unanimous approval, the IAOC goes off
and takes a vote on it because that is what the BCP says to do.

That isn't how we work around here, and I don't think it is the
way we want the IAOC to work.   Instead, I would hope that the
IAOC would examine all of the other plausible options looking
for consensus and resorting to voting only when it is clear
that no consensus, around any option, is possible

Proposed change: Get rid of "unanimous" (both times), replacing
it with "consensus" and appropriate editorial smoothing.

     john


_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]