[cabfpub] [EXTERNAL] Ballot 212: Canonicalise formal name of the Baseline Requirements

Ryan Sleevi sleevi at google.com
Mon Aug 21 18:03:14 UTC 2017


Hi Kirk,

It may be subtle, but the ballot purpose captured it "to make the formal
name of the Baseline Requirements document clear, as use is not currently
consistent"

As noted, the use of terminology is not consistent, throughout the document
or our other documents. This offers the editorial flexibility when
integrating changes to harmonize that, without having to have a giant
ballot to do so once, and then ensure the need to police every ballot
afterwards to ensure they maintain the same internal and external
consistency.

It also provides a stable reference name for external documents (whether
ETSI, WebTrust, or the EVGs) to reference these and ensure there's no
confusion about 'which' baseline requirements these are.

As you're fond of suggesting editorial leeway, this formalizes it in a
Ballot for the specific case of the document name - across all of our
documents (c.f. "Editors and maintainers of CAB Forum documents and
websites are empowered to update text under their control at any time to
make this so.")



On Mon, Aug 21, 2017 at 1:59 PM, Kirk Hall via Public <public at cabforum.org>
wrote:

> Gerv, I was asked by my team “what problem is this ballot solving”?  Not
> in opposition, but just wondering why we need it?
>
>
>
> *From:* Public [mailto:public-bounces at cabforum.org] *On Behalf Of *Gervase
> Markham via Public
> *Sent:* Friday, August 18, 2017 8:06 AM
> *To:* CABFPub <public at cabforum.org>
> *Subject:* [EXTERNAL][cabfpub] Ballot 212: Canonicalise formal name of
> the Baseline Requirements
>
>
>
> *Ballot 212: Canonicalise formal name of the Baseline Requirements*
>
> Purpose of Ballot: to make the formal name of the Baseline Requirements
> document clear, as use is not currently consistent.
>
> The following motion has been proposed by Gervase Markham of Mozilla and
> endorsed by Jeremy Rowley of DigiCert and Ryan Sleevi of Google:
>
> *-- MOTION BEGINS --*
>
> The official name of the Baseline Requirements document shall be 'The
> Baseline Requirements for the Issuance and Management of Publicly-Trusted
> Certificates'. Approved abbreviations for official use are "the Baseline
> Requirements", and "the BRs".
>
> Editors and maintainers of CAB Forum documents and websites are empowered
> to update text under their control at any time to make this so.
>
> *-- MOTION ENDS --*
>
> The procedure for approval of this ballot is as follows:
>
> Start time (22:00 UTC)
>
> End time (22:00 UTC)
>
> Discussion (7 to 14 days)
>
> 18 Aug
>
> 25 Aug
>
> Vote for approval (7 days)
>
> 25 Aug
>
> 1 Sep
>
> 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:
> https://cabforum.org/members/
>
> 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 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.
>
> _______________________________________________
> Public mailing list
> Public at cabforum.org
> https://cabforum.org/mailman/listinfo/public
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20170821/670c67bb/attachment-0003.html>


More information about the Public mailing list