+ Editor: Iang+ Creation Date : 20091215
+ Status: WIP 20100202
+
+
+ Editor: Iang
+ Creation Date : 20091215
+ Status: WIP 20100202
+
+ This sub-policy extends the + + Assurance Policy ("AP" => COD13) + by specifying how Assurers can be assisted by + outsourcing the identity documents verification + component of assurance to trusted third parties (TTPs). +
+ ++ This sub-policy is restricted to members located + in areas not well-served with Assurers. +
+ ++ A Trusted Third Party ("TTP") is a person who is traditionally respected + for making reliable statements to others, especially over identification + documents. Typically, notaries public (anglo), + Notaries (European), bank managers, accountants + and lawyers. +
++ 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. +
+ +uli: (Synonyms: TTP-Assurer, TTP-Admin)
++ 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 be familiar with the local + language and customs. +
+uli: Needs the TTP-Admin be appointed ? Who appoints TTP-Admins ? AO ? Board ?
+ In the past, the TTP-admin was appointed by the board or was the Secretarys duty.
+ A Member ("assuree") who is located in a place not well-served + by Assurers may use the TTP-assisted Assurance. +
+ ++ These steps are taken. +
+ ++ The Member creates her account + and attempts to be assured by the routine face-to-face process. +
++ Once determining that none are conveniently located, + the Member contacts an Assurer who is enabled to + conduct TTP-assisted assurances in the region. +
++ The Assurer confirms that the Member + agrees to the CAcert Community Agreement (CCA), + including the Dispute Resolution Policy (DRP). +
++ The Member and Assurer must negotiate the selection of TTPs + and the provision of adequate identification documents to the TTP. + Each TTP can only be used once (within one assurance for this Member). +
+ +iang: this may suggest a Patch required to the system that permits the Assurer to check other TTP Assurances of the member.
++ The TTP and the Member meet face-to-face. +
++ The TTP shall confirm that: +
++ The TTP shall use either the local form of document + (on CAcert's approved list), or a CAcert-provided form. +
+ ++ The TTP shall log the event by their customary means, + including the Assurer's Name and Verification Token. +
+Old: leaving a Remote Assurance Form and copies of identity documents with the TTP for at least 60 days
++ The paperwork is sent to the Assurer by the TTP. +
+ +Old: sending a Remote Assurance Form and copies of identity documents to the Assurer by mutually agreed medium (eg post, web form or encrypted email).
+iang: this clause is similar to the requirement DRC C.9.b:
+"RAs provide the CA with complete documentation on each verified applicant for a certificate."+
What is different is that the criteria requires the TTP to send the form, not the Member.
+ ++ The Assurer must confirm the assurance using the paperwork, +
+ The Assurer must + be satisfied as to the identity and competency of the TTP + in identification procedures, + as though they were to be conducting the assurance themselves +
+ +iang: this clause would probably meet DRC C.9.a: +
"When the CA uses an external registration authority (RA), each RA is positively identified by CA personnel before being authorized to verify identities of subscribers and authorizations of individuals to represent organizational subscribers (see §A.2.v)."+ For that reason, the above clause should be considered strongly, + and either discussed further in the Handbook, or include these + other Older suggestions: +
RA MUST authenticate the TTP to their satisfaction by: +
+iang: this clause might be better off in the Handbook. Dominik+1
++ The Board routinely delegates its responsibilities to the + Assurance Officer (and this section assumes that, but does + not require it). +
+ ++ A report is requested annually from the Assurance Officer + on performance of this policy for the association's + annual report. +
++ Assurance Officer should prepare documentation + to support the TTP-assisted Assurance, including: +
++ The Assurance Officer maintains + a list of classes of TTPs, divided into regions. + Changes to the regional lists are prepared by + either an Organisation Assurer for that region + (as described by OAP) + or by two Assurers familiar with the traditions + in that region. + Changes are then submitted to the Board for approval. +
++ Use of a TTP not on the list must be approved by Board. + + It is an explicit goal to reduce the usage of + TTP-assisted Assurances in favour of face-to-face Assurance. + +
+ +
+ In coordination with internal and external auditors, + the Assurance Officer shall design and implement a + suitable programme to meet the needs of audit. + Where approved by auditors or Board, the Assurance + Officer may document and implement minor variations to this policy. +
+ +uli: did we discuss the points gained thru a TTP assurance?
+ 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 ?
+ Alternate plan: issue 50 pts (temporarly) with 2 TTP assurances. As enough people
+ 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.