<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>So, is it a fair summary to say:</div>
<div><br>
</div>
<div>A) with the baselines we have blessed methods to validate domains. </div>
<div><br>
</div>
<div>B) we can have multiple domains (San) in those certs. </div>
<div><br>
</div>
<div>C) when we try an issue an OV cert, now there is a perceived confusion of the relying party in instances where there are multiple organizations for the included domains?</div>
<div><br>
</div>
<div>Maybe this is over simplifying, but with baseline Multi org DV is just fine because the cert presents no org, but we are trying to nail down who the org "should" be in the OV equivalent? </div>
<div><br>
</div>
<div>(I know there are other potential items in this ballot, but this is of the most interest to me)</div>
<div><br>
</div>
<div>Brian-<br>
<br>
Sent from my iPhone</div>
<div><br>
On Nov 16, 2012, at 3:57 PM, "Eddy Nigg (StartCom Ltd.)" <<a href="mailto:eddy_nigg@startcom.org">eddy_nigg@startcom.org</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><br>
On 11/16/2012 11:36 PM, From Eddy Nigg (StartCom Ltd.):
<blockquote type="cite"><br>
As long as there are CAs that will sign just anything and everything (for pay), what does it matter if there are revocation capabilities?<br>
<br>
Don't make EV weaker than it is already, we have enough trouble earning some credibility in the other settings, we don't need more of that.<br>
</blockquote>
<br>
Having said that, even though I'm in disagreement with Gerv about his perception regarding OV certificates, it's still troubling to hear that there is still no confidence in the work and diligence most of us probably do.
<br>
<br>
If we can change this perception by raising the bar with serious and reasonable improvements, we probably should do it. We certainly should eliminate well known risk first.<br>
<br>
<br>
<div class="moz-signature">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td colspan="2">Regards </td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td>Signer: </td>
<td>Eddy Nigg, COO/CTO</td>
</tr>
<tr>
<td> </td>
<td><a href="http://www.startcom.org">StartCom Ltd.</a></td>
</tr>
<tr>
<td>XMPP: </td>
<td><a href="">startcom@startcom.org</a></td>
</tr>
<tr>
<td>Blog: </td>
<td><a href="http://blog.startcom.org">Join the Revolution!</a></td>
</tr>
<tr>
<td>Twitter: </td>
<td><a href="http://twitter.com/eddy_nigg">Follow Me</a></td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
</tbody>
</table>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Management mailing list</span><br>
<span><a href="mailto:Management@cabforum.org">Management@cabforum.org</a></span><br>
<span><a href="https://cabforum.org/mailman/listinfo/management">https://cabforum.org/mailman/listinfo/management</a></span><br>
</div>
</blockquote>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information
contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format.<br>
</font>
</body>
</HTML>