<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML con formato previo Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texto de globo Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.HTMLconformatoprevioCar
{mso-style-name:"HTML con formato previo Car";
mso-style-priority:99;
mso-style-link:"HTML con formato previo";
font-family:"Consolas","serif";
color:black;}
span.TextodegloboCar
{mso-style-name:"Texto de globo Car";
mso-style-priority:99;
mso-style-link:"Texto de globo";
font-family:"Tahoma","sans-serif";
color:black;}
span.EstiloCorreo21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=ES link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The TS 102 042 is the one for EV and BR certs and also indicates in 7.5 what Mou has stated. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>This “control” was included to let the CA to set the requirements appropriate to its needs and according to national legislation.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='line-height:9.75pt'><b><span lang=ES-TRAD style='font-size:8.5pt;font-family:"Tahoma","sans-serif"'>Iñigo Barreira</span></b><span lang=ES-TRAD style='font-size:8.5pt;font-family:"Tahoma","sans-serif"'><br>Responsable del Área técnica<br><a href="mailto:i-barreira@izenpe.net">i-barreira@izenpe.net</a><o:p></o:p></span></p><p class=MsoNormal><span lang=ES-TRAD style='font-size:8.5pt;font-family:"Tahoma","sans-serif"'>945067705</span><span lang=ES-TRAD style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=ES-TRAD style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><img border=0 width=585 height=111 id="Imagen_x0020_1" src="cid:image001.png@01CF7E46.BE6479A0" alt="Descripción: cid:image001.png@01CE3152.B4804EB0"></span><span lang=ES-TRAD style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='line-height:9.75pt'><span style='font-size:7.5pt;font-family:"Tahoma","sans-serif";color:#888888;mso-fareast-language:ES-TRAD'>ERNE! Baliteke mezu honen zatiren bat edo mezu osoa legez babestuta egotea. Mezua badu bere hartzailea. Okerreko helbidera heldu bada (helbidea gaizki idatzi, transmisioak huts egin) eman abisu igorleari, korreo honi erantzuna. KONTUZ!</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#888888;mso-fareast-language:ES-TRAD'><br></span><span style='font-size:7.5pt;font-family:"Tahoma","sans-serif";color:#888888;mso-fareast-language:ES-TRAD'>ATENCION! Este mensaje contiene informacion privilegiada o confidencial a la que solo tiene derecho a acceder el destinatario. Si usted lo recibe por error le agradeceriamos que no hiciera uso de la informacion y que se pusiese en contacto con el remitente.</span><span style='font-family:"Calibri","sans-serif";color:navy;mso-fareast-language:ES-TRAD'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>De:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> public-bounces@cabforum.org [mailto:public-bounces@cabforum.org] <b>En nombre de </b>Moudrick M. Dadashov<br><b>Enviado el:</b> sábado, 31 de mayo de 2014 2:30<br><b>Para:</b> ben@digicert.com; kirk_hall@trendmicro.com; 'Gervase Markham'; 'public >> CABFPub'<br><b>Asunto:</b> Re: [cabfpub] Ballot 121 (insurance)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 5/31/2014 2:46 AM, Ben Wilson wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Do you have a proposal that addresses the concerns about financial<o:p></o:p></pre><pre>stability?<o:p></o:p></pre></blockquote><p class=MsoNormal>Please see ETSI TS 101 456 V1.4.3 section 7.5 specifically points d), e) and f) - IMO they are close to what you are looking for.<br><br>As a standardization body ETSI doesn't set its requirements in terms of absolute amounts, this is left to implementers - in this case to MS Governments.<br><br>FYI:<br><a href="http://www.etsi.org/deliver/etsi_ts/101400_101499/101456/01.04.03_60/ts_101456v010403p.pdf">http://www.etsi.org/deliver/etsi_ts/101400_101499/101456/01.04.03_60/ts_101456v010403p.pdf</a><br><br>Given the fact that EVG is incorporated into ETSI "as is", I see potential conflict between the two approaches. <br><br>Thanks.<br>M.D.<br><br><br><o:p></o:p></p><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>-----Original Message-----<o:p></o:p></pre><pre>From: <a href="mailto:kirk_hall@trendmicro.com">kirk_hall@trendmicro.com</a> [<a href="mailto:kirk_hall@trendmicro.com">mailto:kirk_hall@trendmicro.com</a>] <o:p></o:p></pre><pre>Sent: Friday, May 30, 2014 5:20 PM<o:p></o:p></pre><pre>To: <a href="mailto:ben@digicert.com">ben@digicert.com</a>; 'Gervase Markham'; 'public >> CABFPub'<o:p></o:p></pre><pre>Subject: RE: [cabfpub] Ballot 121 (insurance)<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Ben -- as I indicated to the EV Working Group in an email recently, I have<o:p></o:p></pre><pre>definitely changed my mind about the EVGL insurance requirement based on my<o:p></o:p></pre><pre>own experience in starting AffirmTrust in 2010. (As a reminder to all,<o:p></o:p></pre><pre>AffirmTrust was acquired by Trend Micro in 2011, and Trend is big enough and<o:p></o:p></pre><pre>has a strong enough balance sheet and treasury that under the EVGL we are<o:p></o:p></pre><pre>entirely exempt from the insurance requirements -- so we have no personal<o:p></o:p></pre><pre>stake in this.) <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>While starting my own company, the insurance brokers kept asking me why I<o:p></o:p></pre><pre>wanted the insurance coverages -- they clearly didn't think I needed them --<o:p></o:p></pre><pre>and they warned me that the E&O coverage in particular probably wasn't going<o:p></o:p></pre><pre>to provide me with any meaningful protection for anything (given that it<o:p></o:p></pre><pre>generally doesn't cover contractual liability for a bad cert, return of<o:p></o:p></pre><pre>fees, etc.) So it felt like a very big waste of money.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Plus we now know from eight years of experience (plus the anecdotal evidence<o:p></o:p></pre><pre>of Trend Micro's legal counsel from his decade at VeriSign) that there<o:p></o:p></pre><pre>simply aren't claims from customers or relying parties for mis-issued certs<o:p></o:p></pre><pre>and that the need for insurance (even if it did cover the mis-issuance of EV<o:p></o:p></pre><pre>certs) is minimal at best. The one case of catastrophic failure and breach,<o:p></o:p></pre><pre>DigiNotar, apparently resulted in a court ruling that the insurer would be<o:p></o:p></pre><pre>allowed to deny all coverage.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>When we collectively were brainstorming in 2005-6 to create the first EV<o:p></o:p></pre><pre>Guidelines, we were trying to come up with lots and lots of requirements to<o:p></o:p></pre><pre>try to set EV certs apart from other certs. As I recall, we considered even<o:p></o:p></pre><pre>more complex verification steps for EV to make it similar to the closing of<o:p></o:p></pre><pre>a major corporate transaction (e.g., getting Board of Directors<o:p></o:p></pre><pre>authorizations, Secretary's Certificates, etc.) -- fortunately, common sense<o:p></o:p></pre><pre>prevailed and we slimmed down the requirements so they are very thorough,<o:p></o:p></pre><pre>but achievable.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Finally, the Forum has learned through eight years of experience that these<o:p></o:p></pre><pre>insurance requirements are even harder and more expensive for<o:p></o:p></pre><pre>non-US/Canadian CAs to satisfy, and that their brokers also tell them the<o:p></o:p></pre><pre>coverages won't provide them with any meaningful protection. We don't want<o:p></o:p></pre><pre>the EV Guidelines to be weighted in favor of US/Canadian CAs.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The Forum hasn't hesitated from changing other EVGL requirements when we<o:p></o:p></pre><pre>think justified -- such as recently allowing the use of the automatic email<o:p></o:p></pre><pre>verification method to upgrade domains to the EV level (using the same<o:p></o:p></pre><pre>verification methods as for DV and OV certs). For the first seven years of<o:p></o:p></pre><pre>the EVGL, we were all required to do manual vetting of domains with a WhoIs<o:p></o:p></pre><pre>lookup and deal with any mis-match of the registration.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>So for all these reasons, I think Gerv is right and it's time to drop the<o:p></o:p></pre><pre>insurance requirements. Let CAs follow any insurance requirements that<o:p></o:p></pre><pre>their applicable local jurisdiction(s) may impose, but otherwise don't<o:p></o:p></pre><pre>create an additional insurance requirement through the EV Guidelines.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Gerv, thanks for sharing your thoughtful and well informed opinion. It<o:p></o:p></pre><pre>really helps.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Kirk<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>-----Original Message-----<o:p></o:p></pre><pre>From: <a href="mailto:public-bounces@cabforum.org">public-bounces@cabforum.org</a> [<a href="mailto:public-bounces@cabforum.org">mailto:public-bounces@cabforum.org</a>] On<o:p></o:p></pre><pre>Behalf Of Ben Wilson<o:p></o:p></pre><pre>Sent: Friday, May 30, 2014 3:15 PM<o:p></o:p></pre><pre>To: 'Gervase Markham'; 'public >> CABFPub'<o:p></o:p></pre><pre>Subject: Re: [cabfpub] Ballot 121 (insurance)<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Gerv and all,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>If people want to save money, they can stick to issuing DV or OV<o:p></o:p></pre><pre>certificates. EV certificates need to remain different, and this proposed<o:p></o:p></pre><pre>move is contrary to the first goal we all agreed upon when we began working<o:p></o:p></pre><pre>on the guidelines for issuing Extended Validation Certificates, which my<o:p></o:p></pre><pre>notes indicates was to "increase online trust." <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>If the ballot is re-introduced and passes, then CAs will not be required to<o:p></o:p></pre><pre>have insurance for any negligence in issuing or maintaining EV Certificates.<o:p></o:p></pre><pre>It increases the likelihood that another Diginotar won't be held<o:p></o:p></pre><pre>accountable, and I believe the insurance is currently available at<o:p></o:p></pre><pre>affordable cost, approximately $10,000 per $1 million coverage. I have<o:p></o:p></pre><pre>attached a sample cyber-insurance policy, which is available in similar form<o:p></o:p></pre><pre>from any of top insurers internationally-- Zurich, ING, AIG, AXA, Allianz,<o:p></o:p></pre><pre>etc.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The reintroduction of Ballot 121 also reopens negotiations of 8 years ago,<o:p></o:p></pre><pre>which took place during 2006. For example, attached is Kirk Hall's memo to<o:p></o:p></pre><pre>the group from June 2006 in which he recommends "indemnity insurance<o:p></o:p></pre><pre>coverage (e.g. "errors and omissions," "cyber coverage," "network computer<o:p></o:p></pre><pre>liability," "professional liability," or other similar coverage) for<o:p></o:p></pre><pre>Extended Validation Certificates [in the amount of $10 million]." <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Opponents of insurance requirements cannot simply erase these historical<o:p></o:p></pre><pre>choices without proposing viable alternatives. (It's always easier to<o:p></o:p></pre><pre>complain and to poke holes at things than to work on real solutions.) And<o:p></o:p></pre><pre>finally, if the EV Guidelines do not contain some form of financial<o:p></o:p></pre><pre>responsibility, then we might as well delete the Section 7 warranties, and<o:p></o:p></pre><pre>the other EV provisions to which they refer, because they will just become<o:p></o:p></pre><pre>empty promises. <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Ben<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>-----Original Message-----<o:p></o:p></pre><pre>From: <a href="mailto:public-bounces@cabforum.org">public-bounces@cabforum.org</a> [<a href="mailto:public-bounces@cabforum.org">mailto:public-bounces@cabforum.org</a>] On<o:p></o:p></pre><pre>Behalf Of Gervase Markham<o:p></o:p></pre><pre>Sent: Friday, May 30, 2014 12:41 PM<o:p></o:p></pre><pre>To: public >> CABFPub<o:p></o:p></pre><pre>Subject: [cabfpub] Ballot 121 (insurance)<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I talked to our lawyer this morning. Mozilla is now willing to support the<o:p></o:p></pre><pre>proposal in Ballot 121 (removal of the insurance requirement from the EV<o:p></o:p></pre><pre>Guidelines).<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>We feel that this requirement provides no significant protection in practice<o:p></o:p></pre><pre>for either users, for whom CAs can limit liability to $2000 anyway, or for<o:p></o:p></pre><pre>browsers, for whom clause 18.2 which indemnifies them is much more relevant.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>We encourage other CAs and browsers to support this ballot also, and let the<o:p></o:p></pre><pre>CAs put the $N,000 saved towards making their products better and/or cheaper<o:p></o:p></pre><pre>for users.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Gerv<o:p></o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>Public mailing list<o:p></o:p></pre><pre><a href="mailto:Public@cabforum.org">Public@cabforum.org</a><o:p></o:p></pre><pre><a href="https://cabforum.org/mailman/listinfo/public">https://cabforum.org/mailman/listinfo/public</a><o:p></o:p></pre><pre><table class="TM_EMAIL_NOTICE"><tr><td><pre><o:p></o:p></pre><pre>TREND MICRO EMAIL NOTICE<o:p></o:p></pre><pre>The information contained in this email and any attachments is confidential<o:p></o:p></pre><pre>and may be subject to copyright or other intellectual property protection. <o:p></o:p></pre><pre>If you are not the intended recipient, you are not authorized to use or<o:p></o:p></pre><pre>disclose this information, and we request that you notify us by reply mail<o:p></o:p></pre><pre>or telephone and delete the original message from your mail system.<o:p></o:p></pre><pre></pre></td></tr></table><o:p></o:p></pre><p class=MsoNormal><br><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>Public mailing list<o:p></o:p></pre><pre><a href="mailto:Public@cabforum.org">Public@cabforum.org</a><o:p></o:p></pre><pre><a href="https://cabforum.org/mailman/listinfo/public">https://cabforum.org/mailman/listinfo/public</a><o:p></o:p></pre><p class=MsoNormal><o:p> </o:p></p></div></body></html>