<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Rich,<br>
<br>
<div class="moz-cite-prefix">On 03/10/2015 10:15 PM, Rich Smith
wrote:<br>
</div>
<blockquote
cite="mid:0aa701d05b6e$fbde1470$f39a3d50$@smith@comodo.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Eddy, not sure
about all jurisdictions, but for the US DBA/trade names are
generally registered, either at the state, county or city
level, depending upon jurisdiction, so tracing them back to
the legal entity is generally possible, it's just not in
your face obvious, which these customers would call a
feature, not a bug, and generally the reason why they
register such a DBA/trade name in the first place.<o:p></o:p></span></p>
</div>
</blockquote>
<br>
OK, first of all lets work on the assumption that we are writing the
guidelines for any part of the world, not just the US. This will
probably help us to look at the issue better.<br>
<br>
Now, can you (or anybody else) explain to me what were the reasons
for the proposed naming convention for EV certificates? Assuming
there are a couple of good reasons, why should this be a bad thing
for non-EV certificates? <br>
<br>
As somebody who was and is involved trying to confirm registered
trade names (DBAs) I can tell you that this isn't always an easy
thing, not even in the US. Now proposing to have a relying party
doing the same thing, even if possible somehow defeats the purpose
of a verification in my opinion.<br>
<br>
For the record, we adopted the naming convention required for EV
certificates also for non-EV verified SSL certificates. Of course
not everybody likes it, but then there are many things potential
subscribers (or existing subscribers) don't like very much, but
nevertheless have to agree with it or use a different verification
or certificate type.<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>