<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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:0cm;
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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.line867, li.line867, div.line867
{mso-style-name:line867;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.line874, li.line874, div.line874
{mso-style-name:line874;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.line862, li.line862, div.line862
{mso-style-name:line862;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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="NO-BOK" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Buypass votes NO.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">We support the main intent with the ballot, but the changes in the definitions and the use of them may be problematic.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">We need a term covering the “applied-for” Domain Name to be included in the certificate and I think the FQDN term partly served this purpose (with the exception for wildcard domain names). Such a
term, used together with Authorization Domain Name and Base Domain Name would make it possible to express the validation requirements in a clear and consistent way.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">In this ballot the term FQDN is (almost) replaced with the generic term “Domain Name” and since all terms mentioned above are domain names this is confusing. And the term FQDN is still used in section
7.1.4.2.1 but completely replaced in section 3.2.2.4.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I do agree we need to clarify the terms regarding domain names, but I am not comfortable with how this is done in this ballot. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Mads<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Public [mailto:public-bounces@cabforum.org]
<b>On Behalf Of </b>Ben Wilson via Public<br>
<b>Sent:</b> 20. juli 2017 00:34<br>
<b>To:</b> Peter Bowen; CA/Browser Forum Public Discussion List; Ryan Sleevi<br>
<b>Subject:</b> Re: [cabfpub] Ballot 202 - Underscore and Wildcard Characters<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Also, I have capitalized “Domain Name” in the definition of “Domain Label”<span style="background:white">, as shown below and in the attached PDF document.</span><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">On Jul 19, 2017, at 3:52 PM, Peter Bowen <<a href="mailto:pzb@amzn.com">pzb@amzn.com</a>> wrote:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">One more update before voting starts, based on a request from Adriano. The definition of the term Wildcard Domain Name has been updated.<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US">On Jul 18, 2017, at 8:28 PM, Peter Bowen <<a href="mailto:pzb@amzn.com">pzb@amzn.com</a>> wrote:<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt">Thanks to all who provided comments. I’ve integrated the feedback from Kirk, Geoff, and Wayne, including using the definitions that Geoff proposed. <span style="color:#FF2600">BR text that has
changed is in red. Additionally we dropping the proposed change for fully qualified domain name.</span></span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt">Ryan and Ben have agreed to these changes. Voting is scheduled to start in about 18 hours.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt">Thanks for the all the feedback!</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US">On Jul 12, 2017, at 10:24 AM, Ben Wilson via Public <<a href="mailto:public@cabforum.org">public@cabforum.org</a>> wrote:<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="line867" style="font-variant-caps: normal;-webkit-text-stroke-width: 0px;word-spacing:0px">
<strong><span lang="EN-US" style="font-family:"Calibri","sans-serif"">Ballot 202 - Underscore and Wildcard Characters</span></strong><span lang="EN-US"><o:p></o:p></span></p>
<p class="line874" style="font-variant-caps: normal;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span lang="EN-US">The current Baseline Requirements do not expressly allow underscore characters in Subject Alternative Names. This ballot seeks to clarify that one or more underscore characters (“_”) are allowed in FQDNs. In many places it also replaces the
term "FQDN" with "Domain Name" because "Domain Name" now means either "FQDN" or "Wildcard Domain Name". The ballot clarifies validation of wildcard domain names. It also cleans up some of the language in Sections 3.2.2.4 and 7.1.4.2.1 of the Baseline Requirements.<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line862" style="font-variant-caps: normal;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span lang="EN-US">The following motion has been proposed by Ben Wilson of DigiCert and endorsed by Peter Bowen of Amazon and Ryan Sleevi of Google to introduce new Final Maintenance Guidelines for the "Baseline Requirements Certificate Policy for the Issuance
and Management of Publicly-Trusted Certificates" (Baseline Requirements).<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874" style="font-variant-caps: normal;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span lang="EN-US">--Motion Begins--<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874" style="font-variant-caps: normal;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span lang="EN-US">A. In Sections 1.3.2, 1.6 (Base Domain Name), 2.2, 3.2.2.4, 3.2.2.4.5, 3.2.2.4.6, 3.2.2.4.10, 3.2.2.4.11, 4.2.1, 4.9.1.1.6, and 4.9.11 of the Baseline Requirements, REPLACE the words "Fully Qualified Domain Name" and "FQDN" with "Domain Name".<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874" style="font-variant-caps: normal;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span lang="EN-US">B. In Section 1.6.1 of the Baseline Requirements, in the definition for "Authorization Domain Name”, replace “FQDN” with “Domain Name” and change the third sentence to utilize the term “Wildcard Domain Name” such that the definition reads
as follows: The Domain Name used to obtain authorization for certificate issuance for a given Domain Name. The CA may use the
<span style="color:#FF2600">Domain Name</span> returned from a DNS CNAME lookup as the Domain Name for the purposes of domain validation. If the Domain Name is a Wildcard Domain Name, then the CA MUST remove “*.” from the left most portion of
<span style="color:#FF2600">the </span>requested Domain Name. The CA may prune zero or more labels from left to right until encountering a Base Domain Name and may use any one of the intermediate values for the purpose of domain validation.<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">C. In Section 1.6.1 of the Baseline Requirements, INSERT the following definition: "Domain Label: <span style="color:#FF2600;background:white">A label of a
</span><span style="background:white">D<span style="color:#FF2600">omain </span>N<span style="color:#FF2600">ame, as defined in RFC 5890 section 2.2; for example, the
</span>D<span style="color:#FF2600">omain </span>N<span style="color:#FF2600">ame "</span></span><span style="color:#FF2600"><a href="http://www.example.com/">www.example.com</a><span style="background:white">" is composed of three labels: "www", "example",
and "com”. </span></span>" <o:p></o:p></span></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="line874"><span lang="EN-US">D. In Section 1.6.1 of the Baseline Requirements, REPLACE the definition for "Domain Name" with the following: <span style="color:#FF2600;background:white">A string which is a ‘domain name’, as defined in RFC 5890 section
2.2, with </span><span style="background:white">Domain L<span style="color:#FF2600">abels separated by dots, or a Wildcard Domain Name. For example “</span></span><span style="color:#FF2600"><a href="http://www.example.com/">www.example.com</a><span style="background:white">”
and “*.</span><a href="http://example.net/">example.net</a><span style="background:white">” are Domain Names.</span></span> <o:p></o:p></span></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="line874"><span lang="EN-US">E. In Section 1.6.1 of the Baseline Requirements,
<span style="color:#FF2600">DO NOT CHANGE</span> the definition for "Fully-Qualified Domain Name”<o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">F. In Section 1.6.1 of the Baseline Requirements, REPLACE the definition for "Reserved IP Address" with the following: An IPv4 or IPv6 address that the IANA has "False" for Globally Reachable in either of the IANA Special-Purpose
IP Address Registries:<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line867"><span lang="EN-US"><a href="https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml"><span style="color:#954F72">https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml</span></a><span class="apple-converted-space"> </span>or<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line867"><span lang="EN-US"><a href="https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml"><span style="color:#954F72">https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml</span></a><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">G. In Section 1.6.1 of the Baseline Requirements, REPLACE the definition for "Wildcard Certificate" with the following: A Certificate containing a Wildcard Domain Name in any of the Subject Alternative Names in the Certificate.<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">H. In Section 1.6.1 of the Baseline Requirements, INSERT the following definition: "Wildcard Domain Name: <span style="color:#FF2600;background:white">A string starting with "*." (U+002A ASTERISK, U+002E FULL STOP) immediately
followed by a Fully-Qualified Domain Name.</span>" <o:p></o:p></span></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="line874"><span lang="EN-US">I. In Section 2.2 of the Baseline Requirements, INSERT the word "requested" in the fourth sentence between the words "processing CAA records for" and "Domain Names" so that it reads, "processing CAA records for requested
Domain Names".<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">J. In the second paragraph of Section 3.2.2.4 of the Baseline Requirements, replace the first instance of “Full Qualified Domain Name (FQDN)” with “Domain Name” such that it reads, "The CA SHALL confirm that, as of the
date the Certificate issues, the CA has validated each Domain Name listed in the Certificate using at least one of the methods listed below, or is within the Domain Namespace of a Fully Qualified Domain Name (FQDN) that has been validated using at least one
of the methods listed below (not including the method defined in section 3.2.2.4.8)."<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">K. REPLACE Section 3.2.2.6 of the Baseline Requirements in its entirety with:<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">3.2.2.6. Additional Validation for Wildcard Certificates<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">Before issuing a Wildcard Certificate, the CA MUST establish and follow a documented procedure[^pubsuffix] that determines if the FQDN portion of any Wildcard Domain Name in the certificate is “registry-controlled” or is
a “public suffix” (e.g. “*.com”, “*.<a href="http://co.uk/"><span style="color:#954F72">co.uk</span></a>”, see RFC 6454 Section 8.2 for further explanation).<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">If the FQDN portion of any Wildcard Domain Name in the certificate is "registry-controlled" or is a "public suffix", CAs MUST refuse issuance unless the applicant proves its rightful control of the entire Domain Namespace.
(e.g. CAs MUST NOT issue "*.<a href="http://co.uk/"><span style="color:#954F72">co.uk</span></a>" or "*.local", but MAY issue "*.<a href="http://example.com/"><span style="color:#954F72">example.com</span></a>" to Example Co.).<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line862"><span lang="EN-US">[^pubsuffix] Determination of what is “registry-controlled” versus the registerable portion of a Country Code Top-Level Domain Namespace is not standardized at the time of writing and is not a property of the DNS itself.
Current best practice is to consult a “public suffix list” such as<span class="apple-converted-space"> </span><a href="http://publicsuffix.org/"><span style="color:#954F72">http://publicsuffix.org/</span></a><span class="apple-converted-space"> </span>(PSL),
and to retrieve a fresh copy regularly. If using the PSL, a CA SHOULD consult the "ICANN DOMAINS" section only, not the "PRIVATE DOMAINS" section. The PSL is updated regularly to contain new gTLDs delegated by ICANN, which are listed in the "ICANN DOMAINS"
section. A CA is not prohibited from issuing a Wildcard Certificate to the Registrant of an entire gTLD, provided that control of the entire namespace is demonstrated in an appropriate way.<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">L. REPLACE Section 7.1.4.2.1 of the Baseline Requirements in its entirety with:<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">7.1.4.2.1 Subject Alternative Name Extension<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">Certificate Field: extensions:subjectAltName<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">Required/Optional: Required<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">Contents: This extension MUST contain at least one entry. Each entry MUST be one of the following types:<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">1. dNSName: the entry MUST contain either a Fully-Qualified Domain Name or Wildcard Domain Name that the CA has validated in accordance with section 3.2.2.4. FQDNs and the FQDN portion of Wildcard DNs must comply with RFC
5280 section 4.2.1.6 with the following exception: underscore characters ("_") are allowed in Domain Labels such that replacing all underscore characters with hyphen characters ("-") would result in a valid Domain Label. CAs MUST NOT include Domain Labels
which have hyphens as the third and fourth characters unless the first character is "x" or "X", the second character is "n" or "N", and the fifth and later characters are a valid Punycode string. CAs MUST additionally validate that Wildcard DNs are consistent
with section 3.2.2.6. The entry MUST NOT contain an Internal Name.<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">2. iPAddress: the entry MUST contain an IP address that the CA has validated in accordance with Section 3.2.2.5. The entry MUST NOT contain a Reserved IP Address.<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">M. REPLACE subsection a. of Section 7.1.4.2.2 of the Baseline Requirements with:<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">a. Certificate Field: subject:commonName (OID 2.5.4.3)<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">Required/Optional: Deprecated (Discouraged, but not prohibited)<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">Contents: If present, this field MUST contain a single IP address or Domain Name that is one of the values contained in the Certificate’s subjectAltName extension (see Section 7.1.4.2.1). When including a Domain Name in
a common name, CAs MUST only use LDH labels as defined in RFC 5890 and MUST NOT use U-labels. When including an IPv6 address in a common name, CAs MUST use a format conforming to Section 4 or Section 5 of RFC 5952. When including an IPv4 address in a common
name, CAs MUST encode the name as an IPv4Address as defined in RFC 3986.<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">--Motion Ends--<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">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 class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">BALLOT 202 Status: Final Maintenance Guideline Start time (22:00 UTC) End time (22:00 UTC)<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">Discussion (7 to 14 days) July 12, 2017 to July 19, 2017<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">Vote for approval (7 days) July 19, 2017 to July 26, 2017<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">If a vote of the Forum approves this ballot, the Chair will initiate a 30-day IPR Review Period by sending out an IPR Review Notice.<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">After 30 days of announcing the IPR Review period by the Chair:<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">(a) If Exclusion Notice(s) are filed, this ballot approval is rescinded and a PAG will be created; or (b) If no Exclusion Notices are filed, this ballot becomes effective at end of the IPR Review Period.<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">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 class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="line862"><span lang="EN-US">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 class="apple-converted-space"> </span><a href="https://cabforum.org/members/"><span style="color:#954F72">https://cabforum.org/members/</span></a><o:p></o:p></span></p>
<p class="line874"><span lang="EN-US">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 half of the
number of currently active Members, which is the average number of Member organizations that have participated in the previous three Forum-wide meetings (both teleconferences and face-to-face meetings). 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 class="apple-converted-space"> </span><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><Ballot 202.pdf></span><span lang="EN-US" style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">_______________________________________________<br>
Public mailing list<br>
</span><span lang="EN-US"><a href="mailto:Public@cabforum.org"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";color:#954F72">Public@cabforum.org</span></a></span><span lang="EN-US" style="font-size:9.0pt;font-family:"Helvetica","sans-serif""><br>
</span><span lang="EN-US"><a href="https://cabforum.org/mailman/listinfo/public"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";color:#954F72">https://cabforum.org/mailman/listinfo/public</span></a><o:p></o:p></span></p>
</blockquote>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>