cacert/cacert-policies
9
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Fixed up comments on Name.

Browse source 
Moved the "policy" out of the terms definition.
Dropped the (Name) in point 3 because the point is that the Member can be traced with the *certificate* which also includes nameless certs.  This means that any certificate can be relied upon (although what reliance on anonymous certs means is a question for a future arbitrator).
Fixed spelling mistake with 'secondary'.


git-svn-id: http://svn.cacert.org/CAcert/Policies@862 14b1bab8-4ef6-0310-b690-991c95c89dfd
This commit is contained in:
Ian Grigg 2008-06-19 21:40:23 +00:00
parent 79333d0420
commit 8bfd83f99f
1 changed files with 16 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
AssurancePolicy.html
View file

@ -13,9 +13,9 @@
</h1>
<p>
<a href="PolicyOnPolicy.html"><img src="Images/cacert-wip.png" alt="CAcert Policy Status" height="31" width="88" style="border-style: none;" /></a><br />
Author: Ian Grigg<br />
Editor: iang ? <br />
Creation date: 2008-05-30<br />
Status: WIP 2008-05-30<br />
Status: WIP 2008-06-19<br />
Next status: DRAFT June 2008<br />
<!-- $Id: AssurancePolicy.html 772 2008-06-02 13:46:20Z teus $ -->
</p>
@ -35,9 +35,9 @@ The strength of these activities is based on the strength of the assurance.
<dt><em>Member</em></dt>
<dd>An individual who has agreed to the CAcert Community agreement and has created successfully a CAcert (web)account on http://www.cacert.org.
<dt><em>Name</em></dt>
<dd>A Name is the full name (first name(s), family name(s), name extensions,abreviation of name(s), etc.) of an individual. The Name is technically spoken a string exactly taken from a governemental issued photo ID. Transliteration of characters to a character table defined by CAcert is permitted.
<dd>A Name is the full name (first name(s), family name(s), name extensions,abreviation of name(s), etc.) of an individual.
</dd>
<dt><em>Secundary Distinguished Feature</em> (DoB)</dt>
<dt><em>Secondary Distinguishing Feature</em> (DoB)</dt>
<dd>A Name for an individual is discrimated from similar full names by a secondary distinguished feature, as recorded on the on-line CAcert (web) account.
Currently this is the date of birth (DoB) of the individual.
</dd>
@ -85,11 +85,11 @@ In other words, the person is a member of the CAcert community, as defined by th
</li>
<li> The Member has a (login) (web)Account with CAcert's on-line registration and service system.
</li>
<li> The Member (Name) can be determined from any certificate issued by the Account.
<li> The Member can be determined from any certificate issued by the Account.
</li>
<li> The Member is bound into CAcert's Arbitration (as defined by the CCA).
</li>
<li> Some personal details of the Member (Name(s), primary and other listed email address(es), secundary distinguished feature (eg DoB)) are known to CAcert.
<li> Some personal details of the Member (Name(s), primary and other listed email address(es), Secondary Distinguishing Feature (e.g., DoB)) are known to CAcert.
</li></ol>
<p >
The confidence level of the Assurance Statement is expressed by the Assurance Points.
@ -121,6 +121,11 @@ The general standard is that the individual name of the Member is as written on
<em>For more details see the <a href="/wiki/PolicyDrafts/PolicyOnNames">PolicyDrafts/PolicyOnNames</a>, where the discussion is carried on.
This page will be copied into here when the discussion is complete.</em>
<p >
<p>
The technical form of a Name is a string of characters. It should be exactly copied from a governemental-issued photo ID. Transliteration of characters to a character table defined by Assurance Officer is permitted.
</p>
<strong>Multiple Names</strong>
<br>
A Member may have multiple individual Names.
@ -214,7 +219,7 @@ The process consists of:
</li>
<li>Recording of essential details on CAP form (below);
</li>
<li>Examination of Identity documents by Assurer and verification of recorded details (Name(s) and secundary distinguishing feature, eg DoB);
<li>Examination of Identity documents by Assurer and verification of recorded details (Name(s) and Secondary Distinguishing Feature, e.g., DoB);
</li>
<li>Allocation of Assurance Points by Assurer;
</li>
@ -261,11 +266,11 @@ The allocation of the maximum means that the Assurer is 100% confident in the in
<li>The Assurance Statement is confirmed.
</li></ul>
<p >
Any lesser confidence should give less Assurance Points for a Name. If the Assurer has no confidence in the information presented, then <em>zero </em> Assurance Points may be allocated by the Assurer.
Any lesser confidence should result in less Assurance Points for a Name. If the Assurer has no confidence in the information presented, then <em>zero </em> Assurance Points may be allocated by the Assurer.
For example, this may happen if the identity documents are totally unfamiliar to the Assurer.
The number of Assurance Points from <em>zero</em> to <em>maximum </em> is guided by the Assurance Handbook and the judgement of the Assurer.
<p >
Multiple Names (fields for reliance in certificates) should be allocated separately in a single Assurance.
Multiple Names should be allocated separately in a single Assurance.
That is, the Assurer may allocate the maximum to one Name, half that amount to another Name, and zero to a third Name.
<p >
A (new) Member who is not an Assurer may award an Assurer in a reciprocal process a maximum of 2 Assurance Points, according to his judgement.
@ -326,7 +331,7 @@ The CAcert Assurance Programme (CAP) form requests the following details of each
</li>
<li>Primary email address, as recorded in the on-line account;
</li>
<li>Secondary distinguishing feature, as recorded in the on-line account (normally, date of birth);
<li>Secondary Distinguishing Feature, as recorded in the on-line account (normally, date of birth);
</li>
<li>Statement of agreement with the CAcert Community Agreement (CCA);
</li>
@ -343,7 +348,7 @@ The CAP form requests the following details of the Assurer:
<li>Statement of Assurance;
</li>
<li>
Optional: If the Assurance is reciprocal, then the Assurer's email address and secondary distinguishing feature are required as well.
Optional: If the Assurance is reciprocal, then the Assurer's email address and Secondary Distinguishing Feature are required as well.
</li>
<li>Date, location of Assurance and signature of Assurer.
</li></ul>