Hi Bruce –
Thanks for catching the errors in the references. As editorial corrections, I believe it is reasonable for me to fix them and re-post the zip files by the end of day today, under the wording of the motion we passed on Thursday. However, I will need to amend the ballot to point to the new zip file that will contain the corrected Profiles doc.
Regarding the raw format for P-1, I don’t know that we can make a change without re-starting the ballot, even if the change is desired. So I think we will have to leave this question until we resume after the holidays and decide at that point whether we make a change once the public review is complete and then request a second (hopefully shorter) second public review.
From: Bruce Rich [mailto:firstname.lastname@example.org]
Sent: Tuesday, December 20, 2011 10:06 AM
To: Griffin, Robert; Subhash.Sankuratripati@netapp.com
Subject: Re: [kmip] KMIP V1.1 docs uploaded and ballot created
It looks like we have a problem with the Profiles document. It seems that when the Digital Signature Algorithm Enumeration got inserted alphabetically into the KMIP spec as section 184.108.40.206.7 (thus shifting subsequent 220.127.116.11.x sections higher), the affected references in the Profiles document did not get adjusted.
This has numerous impacts, as anything that refers to 18.104.22.168.7 or higher has to be checked by hand. For example, references to ObjectType should have been changed from 22.214.171.124.11 to 126.96.36.199.12, references to CryptographicAlgorithm should have been changed from 188.8.131.52.12 to 184.108.40.206.13, etc.
Less seriously, I can't figure out why the Asymmetric suites have to support RAW format for keys. PKCS1 format is so raw that you need the context or an attribute to tell you whether it's a public key or private, so I'm really puzzled about what a RAW-formatted RSA private key would look like...and the UseCases don't show it in use for Asymmetric cases...if it's never been interop'd, perhaps it doesn't exist?
Bruce A Rich
brich at-sign us dot ibm dot com
Date: 12/17/2011 03:15 PM
Subject: [kmip] KMIP V1.1 docs uploaded and ballot created
Sent by: <email@example.com>
I have uploaded the zip file containing the V1.1 documents that we are considering for Committee Drafts. The documents incorporate all outstanding editorial corrections to both the KMIP Spec and to the KMIP Profiles.
This zip contains only the pdf versions – as soon as I have the docx version of the Use Cases doc, I’ll create a zip of the doc versions and HTML versions.
Following the guidance of OASIS admin, Subhash and I have created a single ballot containing both motions voted in our 15-Dec KMIP TC meeting:
- Promote the working drafts to Committee (Specification / Note) Drafts
- Request OASIS admin to initiate the Public Review
All voting members should see this ballot within the next few minutes. If you believe you are a voting member and do not receive this ballot, please contact the KMIP TC co-chairs.
Thanks again to everyone for all the work in producing KMIP V1.1!
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Robert Griffin
Sent: Saturday, December 17, 2011 3:44 PM
Subject: [kmip] Groups - kmip_v1.1_pdf_17dec11.zip uploaded
this Zip file contains the 4 KMIP V1.1 working draft documents that are being proposed as committee drafts. A comparable Zip with the docx files will also be posted as soon as possible.
-- Mr. Robert Griffin
Document Name: kmip_v1.1_pdf_17dec11.zip
Contains the KMIP V1.1 working draft documents in pdf format that are being
voted on for committee drafts.
Download Latest Revision
Public Download Link
Submitter: Mr. Robert Griffin
Group: OASIS Key Management Interoperability Protocol (KMIP) TC
Date submitted: 2011-12-17 12:44:16