<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
Dear Members,<br>
<br>
Following up on recent discussions,<br>
<ul>
<li>At the <a moz-do-not-send="true"
href="https://cabforum.org/2019/08/16/minutes-for-ca-browser-forum-f2f-meeting-47-thessaloniki-12-13-june-2019/#Instructions-for-creating-ballots-and-challenges-for-moving-canonical-versions-of-all-Guidelines-to-GitHub">last
F2F in Thessaloniki</a></li>
<li>On the <a moz-do-not-send="true"
href="https://cabforum.org/pipermail/servercert-wg/2019-August/000896.html">server
certificate WG list</a></li>
</ul>
<p>and since the current Bylaws (version 2.2) do not address how the
Chair or Vice-Chair could make any changes whatsoever to the Final
Guidelines or Final Maintenance Guidelines, I would like to
prepare a ballot with some administrative language that would
allow the Forum or WG Chair (or Vice-Chair) to make some changes
to Final Guidelines and Final Maintenance Guidelines. Please note
that these practices are already in place and have been followed
for years without any "official" approval from the Forum or a WG
and without having received any objections by the Membership.</p>
<p>Since this is language that would normally be in the Bylaws, and
while we have <a moz-do-not-send="true"
href="https://docs.google.com/document/d/1EtrIy3F5cPge0_M-C8J6fe72KcVI8H5Q_2S6S31ynU0">other
issues pending to discuss</a>, I would like to propose to ballot
these issues separately and once we collect a few, we could update
the Bylaws including language for all these separate issues. I
understand that we don't want to make too frequent changes to our
Bylaws because it involves legal reviews that take additional
time, etc. <br>
</p>
<p>I would like to start with what seems to be an uncontroversial
issue. There seems to be consensus to allow the Chair or
Vice-Chair to update informative (non-normative) sections of the
Guidelines. Here is a list of changes that the Chair or Vice-Chair
should be allowed to do on a Final Guideline or Final Maintenance
Guideline before it is published on our public web site and
without requiring a ballot procedure: <br>
</p>
<ol>
<li>The cover page, <br>
</li>
<li>The Table of Contents</li>
<li>Headers/Footers with version numbers and page numbers<br>
</li>
<li>The table with document revisions or Document History<br>
</li>
<li>The table with Relevant Dates, unless the ballot explicitly
updates this table</li>
</ol>
<p>I would also recommend removing the first paragraph of the EV
Guidelines which reads:</p>
<p>"This version 1.7.0 represents the Extended Validation
Guidelines, as adopted by the CA/Browser Forum as of Ballot SC17,
passed by the Forum on 21 May 2019 and effective as of 21 June
2019." I believe it's redundant because this information is
included in the revision history table and the public web site.</p>
<p>Are there any comments or additional changes that members would
like to see before I start drafting some language? I plan on
having something ready by the end of next week.</p>
<p><br>
</p>
<p>Thank you,</p>
<p>Dimitris.<br>
</p>
<p><br>
</p>
</body>
</html>