This page reports on the details of the first All Member Ballot of 2010. We'll refer to it as All Member Ballot 2010-01.
Motion
This is an All Member Ballot to approve the release of the following Draft Recommendation as a Kantara Initiative Recommendation.
Title of Draft Recommendation: Identity Assurance Framework Version 2.0
Copy of Draft Recommendation: http://bit.ly/iaf_member_ballot
This All-Member Ballot is open to all Members of Kantara Initiative.
- Each Member organization may cast only one vote.
- The Primary Representative from each Member organization should cast the organizational Member's vote.
- If you are unsure who your Primary Representative is please contact staff@kantarainitiative.org for assistance.
Approval of this All Member Ballot requires a "Supermajority of those Voting, with at least 15% of all Members voting" (i.e. at least 75% of those casting a vote must vote to Approve).
Duration
This ballot was open from April 9, 2010 until April 24, 23:59 UTC.
Ballot Results Summary
22 Member Representatives participated in the ballot. 21 voted Yes and 1 voted Abstain (comment provided for Abstain vote).
Ballot Results Details
- Results listed in the order they were received.
Representative
Organization
Vote cast in favour
Comment
1
Bill Smith
Sun
Yes
2
Darrell Shull
BiPac
Yes
3
Ken Salzberg
Intel
Yes
4
Alan Nagelberg
CSC
Yes
5
Philippe Clement
OrangeFT
Yes
6
Roger Martin
AOL
Yes
7
Matthew Gardiner
CA
Yes
8
Roger Sullivan
Oracle
Yes
9
Barry Hieb
Global Patient Identifiers
Yes
10
Susan Landau
Sun
Yes
11
Paul Trevithick
Paul Trevithick
Yes
12
Iain Henderson
MyDex
Yes
13
Colin Wallis
New Zealand State and Government Services
Yes
14
Paul Madsen
NTT
Yes
15
Conor P. Cahill
Intel
Yes
16
John Tolbert
Boeing
Yes
17
Nat Sakimura
NRI
Yes
18
John Fraser
MedNet
Yes
19
Kyle Meadors
Drummond Group (DGI)
Yes
20
Peter Davis
NeuStar
Yes
21
Lucy Lynch
ISOC
Yes
22
Hasan Akram
Fraunhofer SIT
Yes
23
Jim Zok
CSC
Yes
24
Ryota Hashimoto
NTT
Yes
25
Hiroshi Kumeta
NTT
Yes
26
Colin Soutar
CSC
No
References
This ballot was issued in compliance with section 6.2 and section 9 of the Operating Procedures.