[cabfpub] Audit Period ballot draft

[Ryan Sleevi]

I think "Audit periods are required to be continuous in coverage from audit
to audit, and of maximum length 1 year." ends up getting into normatively
specifying, rather than simply defining, and thus may be appropriate to
remove from the definition, and let Section 8.1 define what an _acceptable_
audit period is

Does that work for you?

On Tue, Mar 28, 2017 at 9:18 AM, Gervase Markham via Public <
public at cabforum.org> wrote:

> Hi everyone,
>
> Here's a draft of the ballot to define Audit Period, using the definition
> agreed with Jeff. Does it look OK? Can I get two endorsers?
>
> Gerv
>
>
> *Ballot XXX - Define "Audit Period" *
>
> *Purpose of Ballot: *It appears that CAs are sometimes confused by the
> phrase Audit Period. This ballot adds a definition of that phrase to the
> BRs, in the hope of heading off any further misunderstandings.
>
> -- MOTION BEGINS --
>
> Add the following definition to section 1.6.1 of the Baseline Requirements:
>
> *Audit Period:* In a period-of-time audit, the period between the first day (start) and the last day of operations (end) covered by the auditors in their engagement. (This is not the same as the period of time when the auditors are on-site at the CA.) Audit periods are required to be continuous in coverage from audit to audit, and of maximum length 1 year.
>
> -- MOTION ENDS --
>
>
> 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):
>
>
>
> BALLOT XXX
>
> Status: Final Maintenance Guideline
>
> Start time (23:00 UTC)
>
> End time (23:00 UTC)
>
> Discussion (7 to 14 days)
>
> XXX
>
> XXX
>
> Vote for approval (7 days)
>
> XXX
>
> XXX
>
> If vote approves ballot: Review Period (Chair to send Review Notice) (30
> days).
>
> If Exclusion Notice(s) filed, ballot approval is rescinded and PAG to be
> created.
>
> If no Exclusion Notices filed, ballot becomes effective at end of Review
> Period.
>
> Upon filing of Review Notice by Chair
>
> 30 days after filing of Review Notice by Chair
>
>
>
> 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).
>
>
>
> 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 listPublic at cabforum.orghttps://cabforum.org/mailman/listinfo/public
>
>
> _______________________________________________
> 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/20170328/fd3440ab/attachment-0003.html>