Re: Proposed OVC Listed Policies

From: Arthur Keller <voting_at_kellers_dot_org>
Date: Fri Dec 15 2006 - 12:53:46 CST

Joe, congratulations on passing your qualifying exam. I look forward
to your comments on the proposal below, along with anyone else who
may have comments. Your "comments later" note is the only comment
I've received so far.

Best regards,

At 9:45 AM -0800 11/29/06, Joseph Lorenzo Hall wrote:
>I won't be able to look at this in detail until after my qualifying
>exam in one week. 'til then, Joe
>On 11/27/06, Arthur Keller <> wrote:
>> At its October 20, 2006 meeting, the OVC Board voted unanimously to
>> create "an OVC listed mark that is to be given solely on the nature
>> of the disclosure, type of license, and vendor attestations." The
>> OVC is to publish the disclosure, license, and vendor attestations on
>> its websites. Details about the requirements of what is to be
>> disclosed and under what licenses and what vendor attestations were
>> to be posted to the OVC discuss list subsequently. Further
>> discussions took place at the November 17, 2006 OVC Board meeting.
>> The following proposal is based on these discussions.
>> "OVC Listed" would say that the source, documentation, license, etc.,
>> are publicly disclosed. The public disclosure of the source,
>> documentation, license, etc., would be on our website. We need to
>> come up with a checklist of the items that need to be disclosed. We
>> would then provide a listing ID that one could look up on our website
>> to have access to the publicly disclosed information.
>> Submission components:
>> 1. Listing of components of system (e.g., electronic ballot printer,
>> ballot reconciliation system, ballot verification system) and their
>> version identifiers.
>> 2. Full source code for each voting-specific component of system,
>> including make files, header files, and configuration files, and any
>> other file needed to build a complete version of the system (given
>> COTS object code).
>> 3. Object code image for each component of system (including COTS
>> 4. Checksums of object code image for each component of system (e.g.,
>> MD5, etc.; list of required checksums to be updated by OVC from time
>> to time).
>> 5. Specifications.
>> 6. Documentation.
>> 7. Internal and external document formats and sample documents (e.g.,
>> ballot definition files, cast ballot records, vote total records).
>> 8. Hardware dependencies, specifications, and requirements.
>> 9. For each Commercial-off-the-shelf (COTS) component (e.g.,
>> operating system or device or printer drivers), specifications,
>> version numbers, dates of manufacture. requirements and uses.
>> 10. Feature checklist (e.g., paper ballot vs. electronic ballot with
>> paper audit trail; basic architectural type).
>> 11. License(s) for the system, as per the requirement below.
>> 12. Reports of non-internal tests, such as by Independent Testing
>> Authorities or acceptance tests by customers, as they are prepared.
>> 13. An attestation that all components and descriptions submitted are
>> accurate and represent the versions identified.
>> The Vendor license must allow others also to publish the software,
>> anyone to test and experiment and analyze, including publication of
>> analyses including excerpts of source code. The vendor may retain
>> copyrights, trademark rights, and patent rights, but not trade secret
>> rights.
>> OVC will assign an "OVC Listed" identifier, and publish all of the
>> information submitted (on websites or through other means) with the
>> identifier. Each configuration/version is a separate submission with
>> its own "OVC Listed" identifier. Updated versions or configurations
>> must be resubmitted to be OVC Listed.
>> OVC will document the process for submitting a voting system to be
>>OVC Listed.
>> -------
>> Note: Vendors are not required to grant the rights to make derivative
>> works or derivative systems (other than as part of analyses, tests,
>> or experiments), and the rights to use the system for elections would
> > not be required to be granted as part of obtaining an OVC listing.
>> Note: OVC may charge for listing or make iisting a benefit of certain
>> classes of membership.
>> Note: OVC Listed does not imply any testing of the voting system.
>> The OVC will subsequently develop concepts of open testing,
>> Note: The OVC may host a website or email list or other mechanism for
>> reporting problems with voting systems (whether listed or not), or
>> link to websites maintained by others.
>> -------
>> Note: Feedback on this proposal are requested. In particular,
>> suggestions are requested on what should be in the feature checklist.
>> Respectfully submitted,
>> Arthur Keller
>> OVC Board Secretary
>> --
>> Arthur M. Keller, Ph.D., 3881 Corina Way, Palo Alto, CA 94303-4507
>> tel +1(650)424-0202, fax +1(650)424-0424
>> _______________________________________________
>> OVC-discuss mailing list
>Joseph Lorenzo Hall
>PhD Student, UC Berkeley, School of Information
>OVC-discuss mailing list

Arthur M. Keller, Ph.D., 3881 Corina Way, Palo Alto, CA  94303-4507
tel +1(650)424-0202, fax +1(650)424-0424
OVC-discuss mailing list
= The content of this message, with the exception of any external 
= quotations under fair use, are released to the Public Domain    
Received on Sun Dec 31 23:17:14 2006

This archive was generated by hypermail 2.1.8 : Sun Dec 31 2006 - 23:17:16 CST