Ballot 181 – Readopting BR 3.2.2.4 (Part 1)

Ballot overview

• Ballot 181, Readopting BR 3.2.2.4 (Part 1), was presented as a Final Guideline.
• The ballot states that it passed.
• Voting results shown on the page were 18 yes, 0 no, 3 abstain for CAs, and 5 yes, 0 no, 0 abstain for browsers.
• The page states that the ballot requires a 2/3 affirmative vote by CAs and a majority affirmative vote by browsers, and that quorum was achieved.

What the ballot changed

• The Forum Baseline Requirements and Extended Validation Guidelines, as previously approved up to and including Ballot 176, were readopted with amendments.
• BR 3.2.2.4 was rewritten to define validation of domain authorization or control.
• The CA must confirm, as of certificate issuance, that either the CA or a Delegated Third Party validated each FQDN in the certificate using at least one permitted method.
• The motion says completed confirmations of Applicant authority may be valid for issuance of multiple certificates over time, but the confirmation must have been initiated within the relevant required time period before issuance.
• The motion includes specific validation methods, including:
  • Domain Authorization Document
  • Agreed-Upon Change to Website
• Several subsections were marked Reserved.

Timing and process shown on the ballot page

• Discussion period: Oct. 25, 2016 to Nov. 1, 2016.
• Review period: Nov. 1, 2016 to Dec. 31, 2016.
• Vote for approval: Dec. 31, 2016 to Jan. 7, 2017.
• The page says that if Exclusion Notice(s) were filed, a PAG would be created and no further action would occur until PAG recommendations were received.
• The page also says that if no Exclusion Notice(s) were filed, the process would proceed to the vote for approval.

Compliance date

• The evidence does not state a separate normative effective date for implementation beyond the ballot process dates shown on the page.