<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-family: Arial, sans-serif; "><div><div><div>Hi Kirk,</div><div><br></div><div>No it would not. It would depend on the certificate they requested. I assume that shop keepers in the US don't card 9 year olds buying chocolates but if they asked for alcohol the situation changes.</div><div><br></div><div>It would only be applicable in the 3 instances shown (Which are not the majority of cases) and in one of those would not be necessary if the domain registration information all aligned. They could then choose to include it or not.</div><div><br></div><div>If Trend does not offer DV certificates then it might be best to abstain from this one rather than confusing the rest of the members who also may/may not have experience here.</div><div><br></div><div>Steve</div><div><div><div><p></p><font class="Apple-style-span" style="color: rgb(0, 0, 0); "><font class="Apple-style-span"><p style="font-family: Arial, sans-serif; color: rgb(0, 0, 0); font-size: 14px; "></p></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 href="mailto:kirk_hall@trendmicro.com">kirk_hall@trendmicro.com</a>" <<a href="mailto:kirk_hall@trendmicro.com">kirk_hall@trendmicro.com</a>><br><span style="font-weight:bold">Date: </span> Friday, 16 November 2012 18:06<br><span style="font-weight:bold">To: </span> Steve Roylance <<a href="mailto:steve.roylance@globalsign.com">steve.roylance@globalsign.com</a>><br><span style="font-weight:bold">Cc: </span> CABForum Management <<a href="mailto:management@cabforum.org">management@cabforum.org</a>>, "<a href="mailto:public@cabforum.org">public@cabforum.org</a>" <<a 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"><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 14 (filtered medium)"><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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
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;}
p.MsoPlainText, li.MsoPlainText, 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";}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, 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";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle24
{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 lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="color:#1F497D">The only way a CA could comply with your rules would be to do an OV authentication for every customer before deciding whether or not to issue a DV SANs cert. That’s pretty much the same as outlawing DV SANs
certs<o:p></o:p></span></p><p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "> Steve Roylance [<a href="mailto:steve.roylance@globalsign.com">mailto:steve.roylance@globalsign.com</a>]
<br><b>Sent:</b> Friday, November 16, 2012 9:33 AM<br><b>To:</b> Kirk Hall (RD-US)<br><b>Cc:</b> 'CABForum Management'; <a href="mailto:public@cabforum.org">public@cabforum.org</a><br><b>Subject:</b> Re: [cabfman] [cabfpub] Ballot 92 - Subject Alternative Names<o:p></o:p></span></p></div></div><p class="MsoNormal"><o:p> </o:p></p><div><div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; ">Kirk,<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; "><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; ">It is NOT meant to prohibit all types of DV SANs<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; "><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; ">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.<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; "><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; ">If you own
<b>kirk.com</b> and <b>finewineexpert.com</b> then you can have both inside if they are registered to you.<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; "><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; ">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.<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; "><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; ">Steve<o:p></o:p></span></p></div></div></div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; "><o:p> </o:p></span></p></div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">"<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><b>Date: </b>Friday, 16 November 2012 17:24<br><b>To: </b>CABForum Management <<a href="mailto:management@cabforum.org">management@cabforum.org</a>>, "<a href="mailto:public@cabforum.org">public@cabforum.org</a>" <<a href="mailto:public@cabforum.org">public@cabforum.org</a>><br><b>Subject: </b>Re: [cabfman] [cabfpub] Ballot 92 - Subject Alternative Names<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; "><o:p> </o:p></span></p></div><div><div><p class="MsoPlainText"><span style="color:black">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></span></p><p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p><p 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></p></div></div><table class="MsoNormalTable" border="0" cellpadding="0"><tbody><tr><td style="background:white;padding:.75pt .75pt .75pt .75pt"><table class="MsoNormalTable" border="0" cellpadding="0"><tbody><tr><td style="padding:.75pt .75pt .75pt .75pt"><pre>TREND MICRO EMAIL NOTICE<o:p></o:p></pre><pre>The information contained in this email and any attachments is confidentialand 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 or<o:p></o:p></pre><pre>telephone and delete the original message from your mail system.<o:p></o:p></pre></td></tr></tbody></table></td></tr></tbody></table><p class="MsoNormal"><span style="font-size: 9pt; color: black; font-family: Arial, sans-serif; ">_______________________________________________ Management mailing list
<a href="mailto:Management@cabforum.org">Management@cabforum.org</a> <a href="https://cabforum.org/mailman/listinfo/management">
https://cabforum.org/mailman/listinfo/management</a> <o:p></o:p></span></p></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></span></body></html>