<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 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;}
@font-face
{font-family:"Bradley Hand ITC";
panose-1:3 7 4 2 5 3 2 3 2 3;}
/* 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;}
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.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.Default, li.Default, div.Default
{mso-style-name:Default;
margin:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:12.0pt;
font-family:"Calibri","sans-serif";
color:black;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><u>Ben and all</u> – Now that Carsten has indicated T-Systems has completed its legal review of the draft Bylaws, I’m going through all the suggested edits I have received. I’ll post a new Bylaws version for final review, then we can proceed
to a vote.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ben, you made many useful editing suggestions in the some Bylaws sections that fall into three categories: (1) suggested changes to the Forum’s existing rules, (2) suggested changes to Trend Micro’s proposed new rules as presented in the
Trend Micro governance proposal, and (3) some totally new provisions.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">When I first prepared the draft Bylaws derived from Trend Micro’s governance proposal, I also wanted to include some additional provisions that I favored, such as rules on how ballots are presented and voted on, quorum rules, general rules
for the admission of Observers, etc. – but it was pointed out to me that I shouldn’t add anything that was not previously included in the Trend Micro governance proposal and approved by the Forum members (otherwise members could say “No fair, I didn’t vote
for that.”) So I am holding my other ideas for later ballots if the Bylaws pass.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For this reason, Ben, I’m not going to include your suggestions is categories (1) and (3) above – changes to the Forum’s existing rules that were not in the Trend Micro governance proposal and totally new ideas. But you should save your
ideas and present them for discussion later if the Bylaws pass. I’ll consider and incorporate many of your suggested edits in category (2).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Here are Ben’s suggested edits that I am <u>deferring</u> to a later presentation by Ben and subsequent discussion and ballot if the Bylaws pass: Sec. 1.1, 2.1, 2.2, 3.2,
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Here are Ben’s suggested edits that relate to the Trend Micro governance proposal (and don’t conflict with what was in the proposal or add a totally new idea): Sec. 1.2, 1.3, 3.3, 4.1, 5.1, 6.2, 6.3, and Definitions. I will incorporate
some of these edits in the next draft, which I will post shortly<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks to everyone who has provided ideas.<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Kirk<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:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Ben Wilson [mailto:ben@digicert.com]
<br>
<b>Sent:</b> Tuesday, October 16, 2012 10:24 AM<br>
<b>To:</b> Kirk Hall (RD-US); 'CABFPub'<br>
<b>Subject:</b> RE: [cabfpub] Trend Micro Proposed Bylaws for Review<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Kirk and all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I took the liberty of making a few changes that I think will help move us forward.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Ben<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:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> public-bounces@cabforum.org [mailto:public-bounces@cabforum.org]
<b>On Behalf Of </b>kirk_hall@trendmicro.com<br>
<b>Sent:</b> Monday, October 15, 2012 7:28 PM<br>
<b>To:</b> CABFPub (public@cabforum.org)<br>
<b>Subject:</b> [cabfpub] Trend Micro Proposed Bylaws for Review<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">When the Forum started its governance reform discussion, it adopted a procedure for how any new governance structure would be adopted. Here is the relevant portion of Ballot 85:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN" style="color:black">“A final ballot will be offered to select between the two remaining proposals, by the following voting process:
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN" style="color:black">• A seven (7) day review period, followed by a seven (7) day voting period.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN" style="color:black">• Votes will be tallied and the proposal receiving a simple majority of votes in favor will be deemed the governance policy that the Forum will pursue.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN" style="color:black">• A period of undefined duration during which the author of the successful proposal shall refine the proposal in order to ensure its completeness, while keeping within the spirit
of the proposal that he or she posted to <a href="http://www.cabforum.org">http://www.cabforum.org</a>.”</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Trend Micro attaches for your review and comment the following three documents:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.0in;text-indent:-.5in">1. Proposed CA-Browser Forum Bylaws (v1) 15 Oct 2012<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in;text-indent:-.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.0in;text-indent:-.5in">2. Existing CABF Rules Incorporated in Draft Bylaws (15 Oct 2012)<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in;text-indent:-.5in"><o:p> </o:p></p>
<p class="Default" style="margin-left:1.0in;text-indent:-.5in"><span style="font-size:11.0pt">3. Trend Micro Governance Proposal for the CA/Browser Forum<b>
</b>(v3 – June 27, 2012) – this was the governance proposal adopted by Forum members in Ballot 90.<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="Default"><span style="font-size:11.0pt">You will see that various Bylaws provisions have references in their titles to existing Forum rules from which they were adopted. To compare the existing rules to the proposed new language, look at the text
in the second document, Existing CABF Rules Incorporated in Draft Bylaws. (We believe it will be useful for the Forum to have its basic governance rules all in one place.)<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="Default"><span style="font-size:11.0pt">Other provisions of the draft Bylaws are consistent with the third document, Trend Micro Governance Proposal, and the responses Trend Micro provided over many weeks in response to specific questions about the
Proposal.<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="Default"><span style="font-size:11.0pt">We invite comments on these draft Bylaws from Forum Members and from the public. Once it appears that discussion is complete, Trend Micro will make its final edits, and will then post a “final” version of the
Bylaws for a subsequent Ballot for adoption according to our current voting rules. If the Ballot for adoption succeeds, the Bylaws will be the Forum’s new governance structure; if the Ballot fails, the Forum will continue with its existing governance structure
and rules.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><i><span style="font-size:14.0pt;font-family:"Bradley Hand ITC";color:#0F243E">Kirk R. Hall<o:p></o:p></span></i></b></p>
<p class="MsoNormal">Operations Director, Trust Services<o:p></o:p></p>
<p class="MsoNormal">Trend Micro<o:p></o:p></p>
<p class="MsoNormal">+1.503.243.5405<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<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><o:p> </o:p></pre>
<pre>TREND MICRO EMAIL NOTICE<o:p></o:p></pre>
<pre>The information contained in this email and any attachments is confidential <o:p></o:p></pre>
<pre>and 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:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
</div>
</body>
</html>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre><table class="TM_EMAIL_NOTICE"><tr><td><pre>
TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidential
and 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></table></pre></font></td></tr></table>