<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 11/05/2014 04:48 PM, Jeremy Rowley
wrote:<br>
</div>
<blockquote
cite="mid:14fedd1705ee4b8c81cee523e9b8b0a7@EX2.corp.digicert.com"
type="cite">
<pre wrap="">That wasn't the point of creating EV. From the beginning, EV was intended to reach only the largest companies on the internet. It was designed at the request of Microsoft and banks to be a premiere indicator of identity. EV was never intended to impact OV issuance.
</pre>
</blockquote>
<br>
Maybe we should acknowledge here that CAs working in the field of
verification according to different criterion/policies/capabilities
have a completely different view of the things than say browser
vendors (not speaking about users thereof). It's natural that CAs
see it differently since this is their main product, for browsers
SSL is just a small (though important) aspect of their product.<br>
<br>
I believe it wouldn't hurt to provide a more advanced UI for the
more knowledgeable users without confusing the casual user who
doesn't care/know what it's for anyway. This could be probably done
with the UI that is one click away, whereas the regular UI (address
bar) wouldn't change.<br>
<br>
But that's just food for thought...<br>
<br>
<div class="moz-signature">-- <br>
<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="xmpp:startcom@startcom.org">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>
</body>
</html>