[rtcweb] The Voting Process

John Leslie <john@jlc.net> Wed, 27 November 2013 17:54 UTC

Return-Path: <john@jlc.net>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECCC81ADF10 for <rtcweb@ietfa.amsl.com>; Wed, 27 Nov 2013 09:54:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AoMZKEVHdWUy for <rtcweb@ietfa.amsl.com>; Wed, 27 Nov 2013 09:54:17 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id F1A431ADF5E for <rtcweb@ietf.org>; Wed, 27 Nov 2013 09:54:16 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 729AEC94BF; Wed, 27 Nov 2013 12:54:14 -0500 (EST)
Date: Wed, 27 Nov 2013 12:54:14 -0500
From: John Leslie <john@jlc.net>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <20131127175414.GA87911@verdi>
References: <52935C89.5040408@ericsson.com> <CAGgHUiQnkQKkc-ptMu6DtfUYJY6N9i7PUaeAqKxp96nB2MQBGA@mail.gmail.com> <52936207.5040704@ericsson.com> <E44893DD4E290745BB608EB23FDDB7620A13302B@008-AM1MPN1-041.mgdnok.nokia.com> <5295B273.1060305@ericsson.com> <C5B67CF6-44C2-44ED-A087-67D9737870AD@gmail.com> <5295F718.9010603@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5295F718.9010603@ericsson.com>
User-Agent: Mutt/1.4.1i
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: [rtcweb] The Voting Process
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Nov 2013 17:54:20 -0000

Magnus Westerlund <magnus.westerlund@ericsson.com>; wrote:
> 
> For the proposed voting process see our previous message
> http://www.ietf.org/mail-archive/web/rtcweb/current/msg09909.html
> 
> As I stated, we chairs will need to update this based on the discussion.

   I gather the WGCs intend to update that tomorrow.

   While I would _much_ prefer not to mix discussion of the process
with discussion of the alternatives, there are some really serious
problems with this proposal.

   First:
] 
] The method we propose is based on Instant-runoff voting,
] http://en.wikipedia.org/wiki/Instant-runoff_voting, with the
] understanding that the choice will be the winner according to the
] Instant-runoff voting process.

   Fail!

   A reference to wikipedia is completely unstable unless it refers
to the webpage retrieved at a particular time.

   It is the _intent_ of Wikipedia that the webpage may be modified
at any time by any person: thus people retrieving the page on
different days may receive different text. Those differences may be
obvious or they may be subtle.

   Second:
] 
] 2) Establish those eligible to vote.

   What follows doesn't do that. It instead establishes rules for
determining at some later time _whether_ an individual is eligible.

] Any participant in the working group process either electronically
] or in-person as of yesterday (20th of November).

   (That's where Magnus broke the sentence. Don't blame me...)

   I merely raise the question of whether the process Magnus outlined
is likely to match that goal.

] Who has participated in the Working group process will be anyone
] that can be identified from:
] - The Blue Sheets for any RTCWEB WG session during an IETF meeting or
]   an interim meeting since the WG's creation.
] - posting of at least one email to the RTCWEB mailing list

   Obviously missing from this list is persons subscribed to the
mailing-list during some period. Those would ordinarily be considered
participants.

] The voter must at time of voting prove their eligibility, by pointing
] to the mail archive or a particular blue sheet/meeting. Please verify
] your own eligibility.

   "Voter" is vague here. I take it to mean any person sending a ballot.

   Thus there is no way of challenging a right to vote before the
ballot itself is opened. I believe that is unheard-of.

   It is, IMHO, strange to have no list of eligible voters to enable
challenging eligibility (or absence from the list) before a vote is
cast.

] 3) Start the the voting period. Those eligible and willing to vote send
] their ballot to a vote collector (Matt Lepinski, former Nomcom chair)
] within two weeks using email. The vote collector will check when
] receiving a ballot the that the voter is eligible and send a
] confirmation email on receiving the ballot. During the balloting period
] the vote collector will keep all ballots secret.

   (Just to prove I'm not leaving anything out.)

] Balloting:
] - The voter MUST rank ALL alternatives in their ballot from the most
]   preferred, marked with rank 1, the second most with 2, all the way
]   to the least preferred marked with rank N.

   This is very unusual in Instant Runoff. There are always choices
that a voter would vote _against_ regardless of the alternatives.
This requires that a voter may be counted as in favor of something
s/he completely opposes.

   (Further, it leaves open the "or else" question: what happens if
a ballot doesn't exactly match that requirement?)

] 4) When the voting period is over the ballot collector will publish the
] results as well as all ballots, including the voters name to the RTCWEB
] WG mailing list. This enables all voting individuals to verify that
] their ballot is unmodified. And allows anyone to verify the result of
] the vote.

   Thus every detail of preference becomes public. Inevitably there will
be some persons who are nervous about publishing so much detail. (I
don't mean to imply that employers _would_ punish employees, merely
that employees could understandably be nervous.)

] 5) The selection is recorded in the drafts.

   Even when we get that wikipedia page "retrieved at a particular time,"
it will contain half a dozen different rules for how the counting
proceeds. I strongly recommend extracting the actual rules the WGCs
intend to follow on this list (which will be archival).

   Further, some person needs to be designated to interpret the rules
during counting.

====

   There are many other things I could mention from the email quoted;
but I think it would only detract from the discussion to do so.

--
John Leslie <john@jlc.net>;