<html 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">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (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:12.0pt;
font-family:"Times New Roman",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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">It was to both limit and expand the scope. We wanted to cover BR validation and inclusion of cert extensions but limit the scope to only validation and cert
contents. Previously, we were covering everything related to EV, including insurance, audits, etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Dean Coclin [mailto:Dean_Coclin@symantec.com]
<br>
<b>Sent:</b> Thursday, January 29, 2015 11:14 AM<br>
<b>To:</b> Ryan Sleevi; Jeremy Rowley<br>
<b>Cc:</b> CABFPub<br>
<b>Subject:</b> RE: [cabfpub] Ballot 145 - Formalization of Validation Working Group<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I’ll let Jeremy weigh in, but it was my understanding that the purpose of the name change was to include the requirements for BR SSL certs as part of the scope
and not limit it to just EV. It was not intended to go beyond that.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><br>
Dean<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">
<a href="mailto:public-bounces@cabforum.org">public-bounces@cabforum.org</a> [<a href="mailto:public-bounces@cabforum.org">mailto:public-bounces@cabforum.org</a>]
<b>On Behalf Of </b>Ryan Sleevi<br>
<b>Sent:</b> Thursday, January 29, 2015 1:08 PM<br>
<b>To:</b> Jeremy Rowley<br>
<b>Cc:</b> CABFPub<br>
<b>Subject:</b> Re: [cabfpub] Ballot 145 - Formalization of Validation Working Group<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Jan 29, 2015 at 8:56 AM, Jeremy Rowley <<a href="mailto:jeremy.rowley@digicert.com" target="_blank">jeremy.rowley@digicert.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p><strong><span style="font-weight:normal">This is the ballot to formalize the validation working group and modify its scope to include validation and the inclusion of information in certificates. I’m looking for two endorsers</span></strong><o:p></o:p></p>
<p><strong>Ballot 145 – Formalization of Validation Working Group</strong> <o:p></o:p></p>
<p><strong>Reason</strong> <o:p></o:p></p>
<p>In order to address validation issues and inconsistencies in both the SSL Baseline Requirements and the EV Guidelines, the CAB Forum has held an informal working group previously referred to as the Extended Validation Working Group now known as the Validation
Working Group, would like to modify its scope to include validation in the Baseline Requirements as well as the EV Guidelines.
<o:p></o:p></p>
<p><b>— Motion begins — </b><o:p></o:p></p>
<p>The CA-Browser Forum formally establishes the Validation Working Group as an official working group of the CAB Forum, replacing the previous informal EV working group. The scope of this working group is to address issues arising under adopted CAB Forum
standards related to <span style="color:#1F497D">the </span>validation of certificate information and the inclusion of
<span style="color:#1F497D">information in certificates. </span> <o:p></o:p></p>
<p><b>Scope:</b> The Validation Working Group will consider all matters relating to the validation and inclusion of information in certificates under adopted CAB Forum guidelines.
<o:p></o:p></p>
<p><b>Deliverables:</b> The Working Group shall produce one or more documents offering options to the Forum for validation within the scope defined above.
<o:p></o:p></p>
<p><b>-- Motion Ends -- </b><o:p></o:p></p>
<p>The review period for this ballot shall commence at 2200 UTC on , and will close at 2200 UTC on . Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will
close at 2200 UTC on . Votes must be cast by posting an on-list reply to this thread.
<o:p></o:p></p>
<p>A vote in favor of the motion must indicate a clear 'yes' in the response. A vote against must indicate a clear 'no' in the response. A vote to abstain must indicate a clear 'abstain' in the response. Unclear responses will not be counted. The latest vote
received from any representative of a voting member before the close of the voting period will be counted. Voting members are listed here:
<a href="https://cabforum.org/members/" target="_blank">https://cabforum.org/members/</a>
<o:p></o:p></p>
<p>In order for the motion to be adopted, two thirds or more of the votes cast by members in the CA category and greater than 50% of the votes cast by members in the browser category must be in favor. Quorum is currently nine (9) members– at least nine members
must participate in the ballot, either by voting in favor, voting against, or abstaining.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Jeremy,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I'm a bit unclear on what you see the deliverables of. Is it just a menu-style document for the Forum to mix and match?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Also, could you provide a bit of clarification about the scope of the activity of the WG? For example, would it be within your charter to look at Code Signing? It would seem not, based on the description of documents adopted under the Guidelines.
Or do you see the WG attempting to define new documents that extend/enhance the activities of the Forum?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>