@ -22,6 +22,10 @@
color : blue;
font-weight: bold;
}
.strike {
color : blue;
text-decoration:line-through;
}
-->
< / style >
@ -31,26 +35,35 @@
< h1 > TTP-Assisted Assurance Policy < / h1 >
< p >
< a href = "PolicyOnPolicy.html" > < img align = "right" src = " I mages/cacert-wip.png" alt = "CAcert Policy Status" height = "31" width = "88" style = "border-style: none;" / > < / a >
< a href = "PolicyOnPolicy.html" > < img align = "right" src = " i mages/cacert-wip.png" alt = "CAcert Policy Status" height = "31" width = "88" style = "border-style: none;" / > < / a >
Editor: Iang< br / >
Creation Date : < a href = "https://svn.cacert.org/CAcert/Assurance/Minutes/20091215HamburgMiniTOP.html" > 20091215< / a > < br / >
Status: WIP 20100202< br / >
Status: WIP 20100705< br / >
Licence: < a href = "wiki.cacert.org/Policy#Licence" title = "this document is Copyright CAcert, licensed openly under CC-by-sa with all disputes resolved under DRP. More at wiki.cacert.org/Policy" > CC-by-sa/DRP < / a > < br / >
< / p >
< h2 > < a name = "0" > 0. < / a > Preliminaries < / h2 >
< p >
This sub-policy extends the
< a href = " http: //www.cacert.org/policy/AssurancePolicy.php">
< a href = " //www.cacert.org/policy/AssurancePolicy.php">
Assurance Policy< / a > ("AP" => COD13)
by specifying how Assurers can be assisted by
outsourcing the identity documents verification
component of assurance to trusted third parties (TTPs).
< span class = "change" >
Definitions can be found in AP or in
< a href = "//wiki.cacert.org/AssuranceHandbook" > Assurance Handbook< / a >
("AH").
< / span >
< / p >
< h2 > < a name = "1" > 1. < / a > Scope < / h2 >
< p >
This sub-policy is restricted to members located
in areas not well-served with Assurers.
< span class = "change" >
It serves a goal of promoting both Assurers and Members is those areas.
< / span >
< / p >
< h2 > < a name = "1" > 2. < / a > Roles < / h2 >
@ -63,26 +76,34 @@
Notaries (European), bank managers, accountants
and lawyers.
< / p >
< p >
< p class = "strike" >
The Board maintains a list of approved classes of TTP
and forms of documents.
The list is expected to vary according to the
different juridical traditions of different regions.
< / p >
< h3 > < a name = "2.2" > 2.2 < / a > The Assurer < / h3 >
< h3 > < a name = "2.2" > 2.2 < / a > The Assurer < span class = "change" > (aka TTP-admin)< / a > < / h3 >
< p class = "q" > uli: (Synonyms: TTP-Assurer, TTP-Admin)< / p >
< p >
< p >
To employ a TTP in an assurance,
the Assurer must have 50 experience points,
and pass other checks as imposed by the Board
from time to time.
the Assurer must
< span class = "change" >
be a Senior Assurer.
< / span >
< span class = "strike" >
have 50 experience points, and pass other checks as imposed by the Board from time to time.
< / span >
The Assurer must be familiar with the local
language and customs.
< / p >
< p class = "q" > uli: Needs the TTP-Admin be appointed ? Who appoints TTP-Admins ? AO ? Board ?< br >
In the past, the TTP-admin was appointed by the board or was the Secretarys duty.< / p >
< ul class = "q" > < li > uli: Needs the TTP-Admin be appointed ? Who appoints TTP-Admins ? AO ? Board ?< / li >
< li > In the past, the TTP-admin was appointed by the board or was the Secretarys duty.< / li >
< li > Iang: suggested above in blue that as Senior Assurer, no appointment is necessary.< / li >
< / ul >
< h3 > < a name = "2.3" > 2.3 < / a > Member < / h3 >
< p >
@ -92,6 +113,31 @@
< h2 > < a name = "3" > 3. < / a > The Assurance < / h2 >
< p class = "q" > Iang: I suggest this be section 3:< / p >
< p class = "change" >
Assurance assisted by TTP must meet these requirements:
< / p >
< ol class = "change" type = "a" > < li >
The Assurer must positively confirm the identity and
suitability of the TTP.
< / li > < li >
The TTP and the Member must meet face-to-face.
< / li > < li >
The TTP confirms the details supporting the Assurance Statement.
< / li > < li >
The Assurer makes a reliable statement to confirm the
Assurance Statement.
< / li > < li >
< i >
Assurance must be marked as TTP-Assisted
(e.g., by use of TTPAdmin flag).
< / i >
< / li > < / ol >
< p class = "q" > And all the rest in pink box be pushed into the HANDBOOK. This way, the policy sets requirements and standards, and AO is responsible for meeting them as a PRACTICE. < / p >
< blockquote > < table border = "1" bgcolor = "lightpink" > < tr > < td >
< p >
These steps are taken.
< / p >
@ -235,6 +281,8 @@
< / li > < / ol >
< / td > < / tr > < / table > < / blockquote >
< h2 > < a name = "4" > 4. < / a > Assurance Officer ("AO") < / h2 >
< p >
The Board routinely delegates its responsibilities to the
@ -247,9 +295,18 @@
on performance of this policy for the association's
annual report.
< / p >
< h3 id = "s4.1" > 4.1 Practice < / h3 >
< p >
Assurance Officer should prepare documentation
Assurance Officer should prepare
< span class = "change" >
a detailed documentation under
< a href = "//wiki.cacert.org/AssuranceHandbook" > AH< / a >
that meets the needs of this policy, including:
< / span >
< span class = "strike" >
documentation
to support the TTP-assisted Assurance, including:
< / span >
< / p >
< ul > < li >
Form for TTPs
@ -258,14 +315,28 @@
< / li > < li >
Form for TTP-assisted assurance (used by Assurer)
< / li > < li >
Guide for Assurers.
Guide < span class = "change" > and protocol < / span >
< span class = "q" > (pink box above)< / span >
for Assurers.
< / li > < li >
Mechanisms for contacting Assurers available for
TTP-assisted Assurances.
< / li > < li class = "change" >
Definition of
< a href = "https://wiki.cacert.org/AssuranceHandbook2#What_is_a_Senior_Assurer.3F" >
Senior Assurer< / a > .
< / li > < / ul >
< h3 id = "s4.2" > 4.2 Deserts < / h3 >
< p >
The Assurance Officer maintains
a list of classes of TTPs, divided into regions.
< span class = "change" >
The Assurance Officer maintains a list of regions
that are designated as '< i > deserts,< / i > ' being areas that are so short
of Assurers as to render face-to-face Assurance impractical.
In each region, approved types of TTP are listed (e.g., Notary).
The list is expected to vary according to the
different juridical traditions of different regions.
< / span >
Changes to the regional lists are prepared by
either an Organisation Assurer for that region
(as described by OAP)
@ -274,7 +345,11 @@
Changes are then submitted to the Board for approval.
< / p >
< p >
Use of a TTP not on the list must be approved by Board.
Use of a type of TTP not on the list must be approved by
< span class = "change" >
AO and notified to
< / span >
Board.
< span class = "change" >
It is an explicit goal to reduce the usage of
TTP-assisted Assurances in favour of face-to-face Assurance.
@ -289,20 +364,52 @@
Officer may document and implement minor variations to this policy.
< / p >
< p class = "q" > uli: did we discuss the points gained thru a TTP assurance?< br >
From the calculation with the 35 pts, a TTP assuree never can reach the 100 pts level ...
< h2 class = "change" > < a name = "5" > 5. < / a > Topup Assurance Points < / h2 >
< ul class = "q" > < li > uli: did we discuss the points gained thru a TTP assurance?< / li >
< li > From the calculation with the 35 pts, a TTP assuree never can reach the 100 pts level ...
2x 35 = 70 pts max. So he probably can never become an Assurer. One goal with the
TTP program is, to bring people upto 100 pts, so they can start to be a
regular Assurer. This goal cannot be reached neither by the Nucleus program
in conjunction to the TTP program. Is this as expected ?< br >
Alternate plan: issue 50 pts (temporarly) with 2 TTP assurances. As enough people
in conjunction to the TTP program. Is this as expected ?< / li >
< li >
are in an area, they can start Assure each other. With enough points received,
the temporarly 50 pts can be decreased to the default 35 pts level
(see also the Nucleus program). But issuing temporarly 50 pts, needs probably
also a software update to the system.< / p >
also a software update to the system.< / li >
< li > Iang: see below for one idea we discussed.< / li >
< / ul >
< a href = "http://validator.w3.org/check?uri=referer" > < img align = "right" src = "Images/valid-xhtml11-blue" alt = "Valid XHTML 1.1" height = "31" width = "88" style = "border-style: none;" / > < / a >
< / p >
< p class = "change" >
AO is to operate a topup Assurance programme
to help seed desert areas with Assurers.
< / p >
< p class = "change" >
A topup Assurance is conducted by a third Senior Assurer
according to the following requirements:
< / p >
< ol class = "change" > < li >
Assurer must be a Senior Assurer.
< / li > < li >
Assurer Challenge must be completed as passed by Member.
< / li > < li >
The topup must be requested by Member for purpose of enabling the Member to reach Assurer level.
< / li > < li >
The two TTP-Assisted Assurances already conducted are to be reviewed.
< / li > < li >
Topup may award up to 35 points.
< / li > < li >
Assurance must be marked as Topup
(e.g., by use of new feature with TTPAdmin flag).
< / ol > < / li >
< p class = "change" >
Each topup is to be reported to AO.
Topup is only available in designated deserts.
< / p >
< / body >
< / html >
Ian Grigg
14 years ago