Re: [kmip] preparing to vote for submission of KMIP V1.1 Committee Specifications to OASIS membership

[Chet Ensign <chet.ensign@oasis-open.org>]

Hi Bob, hi Subhash (and all),

Actually, unless I have missed something, your next step is to request
a Special Majority Ballot to approve the Committee Drafts that just
completed public review as Committee Specifications / Notes. Then you
can move on to the COS state.

I have your last public review ending on June 19 for...

Key Management Interoperability Protocol Specification Version 1.1,
Committee Specification Draft 02 / Public Review Draft 02

Key Management Interoperability Protocol Profiles Version 1.1,
Committee Specification Draft 02 / Public Review Draft 02

Key Management Interoperability Protocol Usage Guide Version 1.1,
Committee Note Draft 02 / Public Review Draft 02

Key Management Interoperability Protocol Test Cases Version 1.1,
Committee Note Draft 02 / Public Review Draft 02

I didn't see that any of these had comments so you should submit an
email to the mailing list (if you didn't already) indicating that the
public review ended with no comments received. That then is your link
to the change log for the ticket.

So the motion at the next meeting should be to request TC Admin to
hold a special majority ballot to approve each of these as Committee
Specifications / Notes. Please include the links, e.g.

“The KMIP Technical Committee requests the KMIP co-chairs to request
that TC Administration hold a Special Majority Ballot to approve Key
Management Interoperability Protocol Specification Version 1.1
(http://www.oasis-open.org/committees/download.php/46154/kmip-spec-v1.1-csprd02.zip)
and Key Management Interoperability Protocol Profiles Version 1.1
(http://www.oasis-open.org/committees/download.php/46155/kmip-profiles-v1.1-csprd02.zip)
as Committee Specifications and Key Management Interoperability
Protocol Usage Guide Version 1.1
(http://www.oasis-open.org/committees/download.php/46157/kmip-ug-v1.1-cnprd02.zip)
and Key Management Interoperability Protocol Test Cases Version 1.1
(http://www.oasis-open.org/committees/download.php/46156/kmip-testcases-v1.1-cnprd02.zip)
as Committee Notes."

Once that is approved, please enter 2 Committee Specification ballot
tickets (https://www.oasis-open.org/resources/tc-admin-requests/committee-specification-ballot-request)
and 2 Committee Note ballot tickets
(https://www.oasis-open.org/resources/tc-admin-requests/committee-note-ballot-request)
and I will start the Special Majority Ballots right away.

You should wait until these are completed because the TC Process
requires that the Statements of Use explicitly require the CS and the
approval date. "After the approval of a Committee Specification, and
after three Statements of Use >>explicitly referencing the Committee
Specification, including approval date<<, have been presented to the
TC..."

Let me know if you have any questions on this.

Best,

/chet
On Mon, Jun 25, 2012 at 1:58 AM,  <robert.griffin@rsa.com> wrote:
> Hi –
>
>
>
> Now that we’ve passed the second public review, we’re ready to consider
> submitting the V1.1 Specification and Profiles to OASIS membership for
> promotion to OASIS standards, as we did with the V1.0 docs. For our meeting
> on Thursday 28-Jun, we’d like to consider a motion such as the following:
>
>
>
> “The KMIP Technical Committee requests the KMIP co-chairs to create a ballot
> to submit the KMIP Specification Version 1.1 Committee Specification and
> KMIP Profiles Version 1.1 Committee Specification as a Candidate OASIS
> Standards and to request OASIS to initiate the process for review of these
> candidate standards by the OASIS membership, as defined in the OASIS
> Technical Committee Process, section 3.4.1.”
>
>
>
> There are a number of supporting materials specified in that part of the TC
> Process that have to be included when the chairs submit these documents;
> we’ll prepare and distribute those materials prior to our next meeting on
> 28-June so that TC members can review them before voting on this motion.
>
>
>
> As we’ve discussed in earlier TC calls, we will also need to have at least 3
> Statements of Use – preferably at least in draft form at the time we
> initiate this ballot.  We suggest the following, by way of process for these
> SoUs:
>
>
>
> -          Any organization that is an OASIS member who is interested in
> having a Statement of Use included in the submission to OASIS should
> distribute a draft to the KMIP TC by end-of-day (EDT) Wednesday 27-June. The
> SoU must specify one or more profiles for which the SoU claims conformance.
> Note that for any profile included in the SoU, all of the conformance
> clauses not explicitly marked as optional within the profile must have been
> implemented and tested in order to make such a conformance claim.
>
>
>
> -          Any comments/concerns from TC members should be sent to the KMIP
> co-chairs within a week (that is, by end-of-day Wednesday 4-July. At that
> point the TC co-chairs will work with the SoU submitters on behalf of the TC
> to resolve issues (if there are any) with the SoUs.
>
>
>
> -          The submitter should send the final version of the SoU signed by
> organizational representative to the KMIP TC co-chairs by the start of our
> KMIP TC meeting on 12-July at 11 a.m EDT, when we will review the results of
> the ballot and (hopefully) confirm that we are ready to request the vote by
> OASIS membership.
>
>
>
> Thanks for all the work on KMIP V1.1!  We’re looking forward to our next
> meeting on the 28th.
>
>
>
> Regards,
>
>
> Subhash / Bob
>
>



-- 

/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

TC Administration information and support is available at
http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open