proposed motion to initiate ballot to promote our KMIP V1.1 docs to Committee Specifications / Notes

[<robert.griffin@rsa.com>]

Hi –

 

Following Chet’s guidance in the note below, here’s a draft of the motion that I’d like to consider tomorrow, regarding promoting our V1.1 docs to Committee Specs / Notes:

 

“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."

 

Regards,

Bob

 

 

-----Original Message-----
From: kmip@lists.oasis-open.org [mailto:kmip@lists.oasis-open.org] On Behalf Of Chet Ensign
Sent: Monday, June 25, 2012 4:26 PM
To: Griffin, Robert
Cc: kmip@lists.oasis-open.org
Subject: Re: [kmip] preparing to vote for submission of KMIP V1.1 Committee Specifications to OASIS membership

 

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