<html><div>Chunghwa Telecom Co., Ltd. Votes Yes</div><div><br>
</div><div> Li-Chun</div><div><br>
-----Original message-----<br>
<b>From:</b>Curt Spann via Public<public@cabforum.org><br>
<b>To:</b>CA/Browser Forum Public Discussion List<public@cabforum.org><br>
<b>Cc:</b>Curt Spann<cspann@apple.com><br>
<b>Date: </b> Sat, 15 Apr 2017 09:01:14<br>
<b>Subject:</b> [外部郵件] Re: [cabfpub] Ballot 194 - Effective Date of Ballot 193 Provisions is in the VOTING period (ends April 16)<br>
<x-body>Apple votes ABSTAIN.</x-body></div><x-body><div><br>
</div><div>Curt</div><div><br>
<div><blockquote type="cite"><div>On Apr 9, 2017, at 4:29 PM, Kirk Hall via Public <<a href="mailto:public@cabforum.org">public@cabforum.org</a>> wrote:</div><br class="Apple-interchange-newline"><div>
<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;}
/* 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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
p.line874, li.line874, div.line874
{mso-style-name:line874;
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;}
p.line862, li.line862, div.line862
{mso-style-name:line862;
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;
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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" vlink="#954F72" link="#0563C1">
<div class="WordSection1"><p class="MsoNormal">Reminder: Ballot 194 - Effective Date of Ballot 193 Provisions is in the voting period (ends April 16)<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><b><span style='font-family: "Arial",sans-serif;'>Ballot 194 – Effective Date of Ballot 193 Provisions</span></b><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal"><b><span style='font-family: "Arial",sans-serif;'>Purpose of Ballot:</span></b><span style='font-family: "Arial",sans-serif;'> Recent Ballot 193 reduced the maximum period for certificates and for reuse of vetting data for DV and OV certificates
from 39 months to 825 days. The effective date for reducing the maximum validity period of certificates was specified as March 1, 2018, but no effective date was specified for when the reduction of the maximum period for reuse of vetting data becomes effective.</span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'>It was the intention of the authors of Ballot 193 that the effective date for reducing the maximum period for reuse of vetting data under BR 4.2.1 would also be March 1, 2018. This ballot is
intended to clarify that intention. The ballot also makes these changes retroactive to the effective date of Ballot 193 so there is no gap period.</span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'>Ballot 193 is in the Review Period (which will end on April 22, 2017), and has not yet taken effect. Bylaw 2.3 states that Ballots should include a “redline or comparison
showing the set of changes from the Final Guideline section(s) intended to become a Final Maintenance Guideline” and that “[s]uch redline or comparison shall be made against the Final Guideline section(s) as they exist at the time a ballot is proposed”.</span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'>To avoid confusion, this Ballot will show the proposed changes to BR 4.2.1 will be presented two ways: (1) a comparison of the changes to BR 4.2.1 as it existed before Ballot 193 (which is as
BR 4.2.1 exists at this time this ballot is proposed), and also (2) a comparison of the changes to BR 4.2.1 as it will exist after the Review Period for Ballot 193 is completed (assuming no Exclusion Notices are filed).</span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'>The following motion has been proposed by Chris Bailey of Entrust Datacard and endorsed by Ben Wilson of DigiCert, and Wayne Thayer of GoDaddy to introduce new Final Maintenance Guidelines for
the "Baseline Requirements Certificate Policy for the Issuance and Management of Publicly-Trusted Certificates" (Baseline Requirements) and the "Guidelines for the Issuance and Management of Extended Validation Certificates" (EV Guidelines).</span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'>-- MOTION BEGINS --
</span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal"><b><u><span style='font-family: "Arial",sans-serif;'>Ballot Section 1</span></u></b><o:p></o:p></p><p class="MsoNormal"><b><span style='font-family: "Arial",sans-serif;'> </span></b><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'>BR 4.2.1 is amended to read as follows:</span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal"><i><span style='font-family: "Arial",sans-serif;'>[Ballot amendments shown against BR 4.2.1
<u>as it currently exists without the changes adopted in Ballot 193</u>]</span></i><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><b><span style='font-family: "Arial",sans-serif;'>BR 4.2.1. Performing Identification and Authentication Functions</span></b><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'>The certificate request MAY include all factual information about the Applicant to be included in the Certificate, and such additional information as is necessary
for the CA to obtain from the Applicant in order to comply with these Requirements and the CA’s Certificate Policy and/or Certification Practice Statement. In cases where the certificate request does not contain all the necessary information about the Applicant,
the CA SHALL obtain the remaining information from the Applicant or, having obtained it from a reliable, independent, third</span><span style='font-family: "Cambria Math",serif;'>‐</span><span style='font-family: "Arial",sans-serif;'>party data source, confirm
it with the Applicant. The CA SHALL establish and follow a documented procedure for verifying all data requested for inclusion in the Certificate by the Applicant.</span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'>Applicant information MUST include, but not be limited to, at least one Fully</span><span style='font-family: "Cambria Math",serif;'>‐</span><span style='font-family: "Arial",sans-serif;'>Qualified
Domain Name or IP address to be included in the Certificate’s SubjectAltName extension.</span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'>Section 6.3.2 limits the validity period of Subscriber Certificates. The CA MAY use the documents and data provided in Section 3.2 to verify certificate information,
provided that<b><u>:</u></b> <i><s>the CA obtained the data or document from a source specified under Section 3.2 no more than thirty</s></i></span><i><s><span style='font-family: "Cambria Math",serif;'>‐</span></s></i><i><s><span style='font-family: "Arial",sans-serif;'>nine
(39) months prior to issuing the Certificate.</span></s></i><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="margin-left: 0.5in; -ms-text-autospace:;"><b><u><span style='font-family: "Arial",sans-serif;'>(1) Prior to March 1, 2018, the CA obtained the data or document from a source specified under Section 3.2 no more than 39 months prior to issuing
the Certificate; and</span></u></b><o:p></o:p></p><p class="MsoNormal" style="margin-left: 0.5in; -ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="margin-left: 0.5in; -ms-text-autospace:;"><b><u><span style='font-family: "Arial",sans-serif;'>(2) On or after March 1, 2018, the CA obtained the data or document from a source specified under Section 3.2 no more than 825 days prior to
issuing the Certificate. </span></u></b><o:p></o:p></p><p class="MsoNormal" style="margin-left: 0.5in; -ms-text-autospace:;"><b><span style='font-family: "Arial",sans-serif;'> </span></b><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'>The CA SHALL develop, maintain, and implement documented procedures that identify and require additional verification activity for High Risk Certificate Requests prior
to the Certificate’s approval, as reasonably necessary to ensure that such requests are properly verified under these Requirements.</span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'>If a Delegated Third Party fulfills any of the CA’s obligations under this section, the CA SHALL verify that the process used by the Delegated Third Party to identify and further verify High
Risk Certificate Requests provides at least the same level of assurance as the CA’s own processes.</span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal"><i><span style='font-family: "Arial",sans-serif;'>[Ballot amendments shown against BR 4.2.1
<u>as it existed after Ballot 193 was approved</u>]</span></i><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><b><span style='font-family: "Arial",sans-serif;'>BR 4.2.1. Performing Identification and Authentication Functions</span></b><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'>The certificate request MAY include all factual information about the Applicant to be included in the Certificate, and such additional information as is necessary
for the CA to obtain from the Applicant in order to comply with these Requirements and the CA’s Certificate Policy and/or Certification Practice Statement. In cases where the certificate request does not contain all the necessary information about the Applicant,
the CA SHALL obtain the remaining information from the Applicant or, having obtained it from a reliable, independent, third</span><span style='font-family: "Cambria Math",serif;'>‐</span><span style='font-family: "Arial",sans-serif;'>party data source, confirm
it with the Applicant. The CA SHALL establish and follow a documented procedure for verifying all data requested for inclusion in the Certificate by the Applicant.</span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'>Applicant information MUST include, but not be limited to, at least one Fully</span><span style='font-family: "Cambria Math",serif;'>‐</span><span style='font-family: "Arial",sans-serif;'>Qualified
Domain Name or IP address to be included in the Certificate’s SubjectAltName extension.</span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'>Section 6.3.2 limits the validity period of Subscriber Certificates. The CA MAY use the documents and data provided in Section 3.2 to verify certificate information,
provided that<b><u>:</u></b> <i><s>the CA obtained the data or document from a source specified under Section 3.2 no more than 825 days<b>
</b>prior to issuing the Certificate.</s></i></span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="margin-left: 0.5in; -ms-text-autospace:;"><b><u><span style='font-family: "Arial",sans-serif;'>(1) Prior to March 1, 2018, the CA obtained the data or document from a source specified under Section 3.2 no more than 39 months prior to issuing
the Certificate; and</span></u></b><o:p></o:p></p><p class="MsoNormal" style="margin-left: 0.5in; -ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="margin-left: 0.5in; -ms-text-autospace:;"><b><u><span style='font-family: "Arial",sans-serif;'>(2) On or after March 1, 2018, the CA obtained the data or document from a source specified under Section 3.2 no more than 825 days prior to
issuing the Certificate. </span></u></b><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'>The CA SHALL develop, maintain, and implement documented procedures that identify and require additional verification activity for High Risk Certificate Requests prior
to the Certificate’s approval, as reasonably necessary to ensure that such requests are properly verified under these Requirements.</span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'>If a Delegated Third Party fulfills any of the CA’s obligations under this section, the CA SHALL verify that the process used by the Delegated Third Party to identify and further verify High
Risk Certificate Requests provides at least the same level of assurance as the CA’s own processes.</span><o:p></o:p></p><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><b><u><span style='font-family: "Arial",sans-serif;'>Ballot Section 2</span></u></b><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'>The provisions of Ballot Section 1 will be effective retroactive to the effective date of Ballot 193.</span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><span style='font-family: "Arial",sans-serif;'> </span><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><b><span lang="EN" style="font-family: Arial, sans-serif;"> </span></b><o:p></o:p></p><p class="MsoNormal" style="-ms-text-autospace:;"><b><span lang="EN" style="font-family: Arial, sans-serif;">--Motion Ends--</span></b><o:p></o:p></p><div style="margin: 0in 0in 0pt;"><span style='font-family: "Arial",sans-serif; font-size: 11pt;'> </span><o:p></o:p></div><div style="margin: 0in 0in 0pt;"><span style='font-family: "Arial",sans-serif; font-size: 11pt;'>The procedure for approval of this Final Maintenance Guideline ballot is as follows (exact start and end times may be adjusted to comply
with applicable Bylaws and IPR Agreement):</span><o:p></o:p></div><div style="margin: 0in 0in 0pt;"><span style='font-family: "Arial",sans-serif; font-size: 11pt;'> </span><o:p></o:p></div>
<table class="MsoNormalTable" style="border-collapse: collapse;" border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td width="459" valign="top" style="padding: 0in 5.4pt; border: 1pt solid windowtext; border-image: none; width: 229.25pt;"><div style="margin: 0in 0in 0pt; line-height: 105%;"><span style='line-height: 105%; font-family: "Arial",sans-serif; font-size: 11pt;'>BALLOT 194</span><o:p></o:p></div><div style="margin: 0in 0in 0pt; line-height: 105%;"><span style='line-height: 105%; font-family: "Arial",sans-serif; font-size: 11pt;'>Status: Final Maintenance Guideline</span><o:p></o:p></div>
</td>
<td width="165" valign="top" style="border-width: 1pt 1pt 1pt medium; border-style: solid solid solid none; border-color: windowtext windowtext windowtext currentColor; padding: 0in 5.4pt; border-image: none; width: 82.4pt;"><div style="margin: 0in 0in 0pt; text-align: center; line-height: 105%;">
<span style='line-height: 105%; font-family: "Arial",sans-serif; font-size: 11pt;'>Start time (22:00 UTC)</span><o:p></o:p></div>
</td>
<td width="159" valign="top" style="border-width: 1pt 1pt 1pt medium; border-style: solid solid solid none; border-color: windowtext windowtext windowtext currentColor; padding: 0in 5.4pt; border-image: none; width: 79.35pt;"><div style="margin: 0in 0in 0pt; text-align: center; line-height: 105%;">
<span style='line-height: 105%; font-family: "Arial",sans-serif; font-size: 11pt;'>End time (22:00 UTC)</span><o:p></o:p></div>
</td>
</tr>
<tr>
<td width="459" valign="top" style="border-width: medium 1pt 1pt; border-style: none solid solid; border-color: currentColor windowtext windowtext; padding: 0in 5.4pt; border-image: none; width: 229.25pt;"><div style="margin: 0in 0in 0pt; line-height: 105%;"><span style='line-height: 105%; font-family: "Arial",sans-serif; font-size: 11pt;'>Discussion (7 to 14 days)</span><o:p></o:p></div>
</td>
<td width="165" valign="top" style="border-width: medium 1pt 1pt medium; border-style: none solid solid none; border-color: currentColor windowtext windowtext currentColor; padding: 0in 5.4pt; width: 82.4pt;"><div style="margin: 0in 0in 0pt; text-align: center; line-height: 105%;">
<span style='line-height: 105%; font-family: "Arial",sans-serif; font-size: 11pt;'>April 2, 2017</span><o:p></o:p></div>
</td>
<td width="159" valign="top" style="border-width: medium 1pt 1pt medium; border-style: none solid solid none; border-color: currentColor windowtext windowtext currentColor; padding: 0in 5.4pt; width: 79.35pt;"><p align="center" class="MsoNormal" style="text-align: center;"><span style='font-family: "Arial",sans-serif;'>April 9, 2017</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="459" valign="top" style="border-width: medium 1pt 1pt; border-style: none solid solid; border-color: currentColor windowtext windowtext; padding: 0in 5.4pt; border-image: none; width: 229.25pt;"><div style="margin: 0in 0in 0pt; line-height: 105%;"><span style='line-height: 105%; font-family: "Arial",sans-serif; font-size: 11pt;'>Vote for approval (7 days)</span><o:p></o:p></div>
</td>
<td width="165" valign="top" style="border-width: medium 1pt 1pt medium; border-style: none solid solid none; border-color: currentColor windowtext windowtext currentColor; padding: 0in 5.4pt; width: 82.4pt;"><p align="center" class="MsoNormal" style="text-align: center;"><span style='font-family: "Arial",sans-serif;'>April 9, 2017</span><o:p></o:p></p>
</td>
<td width="159" valign="top" style="border-width: medium 1pt 1pt medium; border-style: none solid solid none; border-color: currentColor windowtext windowtext currentColor; padding: 0in 5.4pt; width: 79.35pt;"><p align="center" class="MsoNormal" style="text-align: center;"><span style='font-family: "Arial",sans-serif;'>April 16, 2017</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="459" valign="top" style="border-width: medium 1pt 1pt; border-style: none solid solid; border-color: currentColor windowtext windowtext; padding: 0in 5.4pt; border-image: none; width: 229.25pt;"><div style="margin: 0in 0in 0pt; line-height: 105%;"><span style='line-height: 105%; font-family: "Arial",sans-serif; font-size: 11pt;'>If vote approves ballot: Review Period (Chair to send Review Notice) (30 days).
</span><o:p></o:p></div><div style="margin: 0in 0in 0pt; line-height: 105%;"><span style='line-height: 105%; font-family: "Arial",sans-serif; font-size: 11pt;'>If Exclusion Notice(s) filed, ballot approval is rescinded and PAG to be created.</span><o:p></o:p></div><div style="margin: 0in 0in 0pt; line-height: 105%;"><span style='line-height: 105%; font-family: "Arial",sans-serif; font-size: 11pt;'>If no Exclusion Notices filed, ballot becomes effective at end of Review Period.</span><o:p></o:p></div>
</td>
<td width="165" valign="top" style="border-width: medium 1pt 1pt medium; border-style: none solid solid none; border-color: currentColor windowtext windowtext currentColor; padding: 0in 5.4pt; width: 82.4pt;"><p align="center" class="MsoNormal" style="text-align: center;"><span style='font-family: "Arial",sans-serif;'>Upon filing of Review Notice by Chair</span><o:p></o:p></p>
</td>
<td width="159" valign="top" style="border-width: medium 1pt 1pt medium; border-style: none solid solid none; border-color: currentColor windowtext windowtext currentColor; padding: 0in 5.4pt; width: 79.35pt;"><p align="center" class="MsoNormal" style="text-align: center;"><span style='font-family: "Arial",sans-serif;'>30 days after filing of Review Notice by Chair</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table><div style="margin: 0in 0in 0pt;"><span style='font-family: "Arial",sans-serif; font-size: 11pt;'> </span><o:p></o:p></div><div style="margin: 0in 0in 0pt;"><span style='font-family: "Arial",sans-serif; font-size: 11pt;'>From Bylaw 2.3: If the Draft Guideline Ballot is proposing a Final Maintenance Guideline, such ballot will include a redline or comparison
showing the set of changes from the Final Guideline section(s) intended to become a Final Maintenance Guideline, and need not include a copy of the full set of guidelines. Such redline or comparison shall be made against the Final Guideline section(s) as
they exist at the time a ballot is proposed, and need not take into consideration other ballots that may be proposed subsequently, except as provided in Bylaw Section 2.3(j).</span><o:p></o:p></div><div style="margin: 0in 0in 0pt;"><span style='font-family: "Arial",sans-serif; font-size: 11pt;'> </span><o:p></o:p></div><div style="margin: 0in 0in 0pt;"><span style='font-family: "Arial",sans-serif; font-size: 11pt;'>Votes must be cast by posting an on-list reply to this thread on the Public list. 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:
</span><a href="https://cabforum.org/members/"><span style='color: windowtext; font-family: "Arial",sans-serif; font-size: 11pt;'>https://cabforum.org/members/</span></a><span style='font-family: "Arial",sans-serif; font-size: 11pt;'>
</span><o:p></o:p></div><div style="margin: 0in 0in 0pt;"><span style='font-family: "Arial",sans-serif; font-size: 11pt;'> </span><o:p></o:p></div><p class="MsoNormal"><span style='font-family: "Arial",sans-serif;'>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. <span style="background: white;">Quorum is shown on CA/Browser Forum wiki. Under Bylaw 2.2(g), at least the required quorum number must participate in the ballot for the ballot to be valid, either by voting in favor, voting against, or abstaining.</span></span><o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
_______________________________________________<br>
Public mailing list<br>
<a href="mailto:Public@cabforum.org">Public@cabforum.org</a><br>
https://cabforum.org/mailman/listinfo/public<br>
</div></blockquote></div><br>
</div></x-body><div><x-body></x-body>_______________________________________________<br>
Public mailing list<br>
Public@cabforum.org<br>
<a href="https://cabforum.org/mailman/listinfo/public" target="new_win">https://cabforum.org/mailman/listinfo/public</a><br>
<br>
</div></html><br><html><div><div>本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件. 如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任. </div><div>Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information.</div></div><div><br></div><div><br></div></html>