<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>The question is not if it's "acceptable to continue", but if there is evidence to show that banning a wide swath of DV issuance is an effective improvement that merits the increased cost and effort that it requires of customers.</div><div><br></div><div>The "evidence" shown so far has been a hypothetical threat that a relying party would trust a DV certificate in a situation where an OV certificate would be distrusted due to the additional information contained in the O field. In addition, it has been stated that the validation process for an OV cert provides better traceability and presents an overall "higher bar" to deter a malicious applicant.</div><div><br></div><div>The first assertion assumes that the relying party is going to drill into the certificate details to examine the O field before trusting the cert. The second assertion implies that the standard for getting an "individual" OV cert is a significantly higher bar. That requires the applicant to submit a copy of a photo ID and a copy of a utility bill. That's our idea of raising the bar?<br></div><div><br></div><div>I think we'd all be better off if we focus on educating our customers about the benefits of different types of certs and then letting them choose, rather than continuing to try to mandate their behavior.</div><div><br></div><div>Meanwhile, if this ballot is approved, a lot of people relying on publicly trusted certs for completely private systems will have been misled by the CAB Forum's original 2015 deadline and be immediately forced to buy OV.<br></div><div><br></div><div>Thanks,<br></div><div><br></div><div>Wayne</div><div><br><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [cabfpub] [cabfman] Ballot 92 - Subject Alternative Names<br>
From: Steve Roylance <<a href="mailto:steve.roylance@globalsign.com">steve.roylance@globalsign.com</a>><br>
Date: Fri, November 16, 2012 10:33 am<br>
To: "<a href="mailto:kirk_hall@trendmicro.com">kirk_hall@trendmicro.com</a>" <<a href="mailto:kirk_hall@trendmicro.com">kirk_hall@trendmicro.com</a>><br>
Cc: 'CABForum Management' <<a href="mailto:management@cabforum.org">management@cabforum.org</a>>,<br>
"<a href="mailto:public@cabforum.org">public@cabforum.org</a>" <<a href="mailto:public@cabforum.org">public@cabforum.org</a>><br>
<br>
<div><div><div>Kirk,</div><div><br></div><div>It is NOT meant to prohibit all types of DV SANs</div><div><br></div><div>It is meant to prohibit DV SANs under certain conditions i.e. where non unique information is contained, or Public IPs are used, or there is a mixture of owners as detailed by the domain registration.</div><div><br></div><div>If you own <b><a href="http://kirk.com">kirk.com</a></b> and <b><a href="http://finewineexpert.com">finewineexpert.com</a></b> then you can have both inside if they are registered to you.</div><div><br></div><div>Please read the text again carefully and highlight which situation you specifically don't agree with and why you feel it's acceptable to continue.</div><div><br></div><div>Steve</div><div><div><div><div></div><font class="Apple-style-span" style="color: rgb(0, 0, 0); "><font class="Apple-style-span"><div style="font-family: Arial, sans-serif; color: rgb(0, 0, 0); font-size: 14px; "></div></font></font></div></div></div></div></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> "<a target="_blank" href="mailto:kirk_hall@trendmicro.com">kirk_hall@trendmicro.com</a>" <<a target="_blank" href="mailto:kirk_hall@trendmicro.com">kirk_hall@trendmicro.com</a>><br><span style="font-weight:bold">Date: </span> Friday, 16 November 2012 17:24<br><span style="font-weight:bold">To: </span> CABForum Management <<a target="_blank" href="mailto:management@cabforum.org">management@cabforum.org</a>>, "<a target="_blank" href="mailto:public@cabforum.org">public@cabforum.org</a>" <<a target="_blank" href="mailto:public@cabforum.org">public@cabforum.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [cabfman] [cabfpub] Ballot 92 - Subject Alternative Names<br></div><div><br></div><div 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"><style>
#wmQuoteWrapper /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}
#wmQuoteWrapper @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;}
#wmQuoteWrapper /* Style Definitions */ p.MsoNormal, #wmQuoteWrapper li.MsoNormal, #wmQuoteWrapper div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif";}
#wmQuoteWrapper a:link, #wmQuoteWrapper span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;}
#wmQuoteWrapper a:visited, #wmQuoteWrapper span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;}
#wmQuoteWrapper p.MsoPlainText, #wmQuoteWrapper li.MsoPlainText, #wmQuoteWrapper div.MsoPlainText {mso-style-priority:99; mso-style-link:"Plain Text Char"; margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif";}
#wmQuoteWrapper p.MsoAcetate, #wmQuoteWrapper li.MsoAcetate, #wmQuoteWrapper div.MsoAcetate {mso-style-priority:99; mso-style-link:"Balloon Text Char"; margin:0in; margin-bottom:.0001pt; font-size:8.0pt; font-family:"Tahoma","sans-serif";}
#wmQuoteWrapper span.PlainTextChar {mso-style-name:"Plain Text Char"; mso-style-priority:99; mso-style-link:"Plain Text"; font-family:"Calibri","sans-serif";}
#wmQuoteWrapper span.BalloonTextChar {mso-style-name:"Balloon Text Char"; mso-style-priority:99; mso-style-link:"Balloon Text"; font-family:"Tahoma","sans-serif";}
#wmQuoteWrapper .MsoChpDefault {mso-style-type:export-only; font-family:"Calibri","sans-serif";}
#wmQuoteWrapper @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;}
#wmQuoteWrapper div.WordSection1 {page:WordSection1;}
</style><div link="blue" vlink="purple" lang="EN-US"><div class="WordSection1"><div class="MsoPlainText">To help members evaluate Ballot 92 we are attaching a side-by-side comparison of current Baseline Requirements language with the proposed new language. As before, the intent of this ballot is to prohibit DV SANs certificates, which we will oppose.<o:p></o:p></div><div class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></div><div class="MsoPlainText"><span style="color:black">Trend Micro does not issue DV certificates, but we think they serve a valuable security function in increasing the use of SSL. Forcing customers to buy OV certs instead is anti-competitive and will likely lead to less use of SSL to secure sites.<o:p></o:p></span></div></div></div></div><table><tbody><tr><td bgcolor="#ffffff"><font color="#000000"><pre><table class="TM_EMAIL_NOTICE"><tbody><tr><td><pre>TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidentialand may be subject to copyright or other intellectual property protection.
If you are not the intended recipient, you are not authorized to use or
disclose this information, and we request that you notify us by reply mail or
telephone and delete the original message from your mail system.
</pre></td></tr></tbody></table></pre></font></td></tr></tbody></table> _______________________________________________ Management mailing list <a target="_blank" href="mailto:Management@cabforum.org">Management@cabforum.org</a> <a target="_blank" href="https://cabforum.org/mailman/listinfo/management">https://cabforum.org/mailman/listinfo/management</a> </span> <hr>_______________________________________________<br>
Public mailing list<br>
<a href="mailto:Public@cabforum.org">Public@cabforum.org</a><br>
<a href="https://cabforum.org/mailman/listinfo/public">https://cabforum.org/mailman/listinfo/public</a><br>
</div>
</blockquote></span></body></html>