Comments on kmip-asym-key-profile-v1.0-wd01-review Test cases AKLC-M-3-10, AKLC-M-3-11, AKLC-M-3-12 at TIME 7 require that the public key state be pre-active after the private key was revoked with reason key compromise at TIME 5. As agreed at the face to face, as stated in the Usage Guide, and as allowed in the January 2013 interop testing, the state of the public key after the linked private key has been revoked with reason key compromise MAY be compromised. The specification does not require that it SHALL remain unchanged. Either this profile should define both allowed behaviours as optional - i.e. linked key state changes, or linked key state remains unchanged - or separate profiles should be defined for each behaviour. 3.4 Optional Test Cases KMIP 1.0 3.5 Optional Test Cases KMIP 1.1 3.6 Optional Test Cases KMIP 1.2 This section documents the optional test cases that a client or server conformant to the Asymmetric Key Lifecycle Profile SHALL support under KMIP Specification ... Using "SHALL" to specify optional behaviour is confusing. Replace "SHALL" with "MAY". John From:
kmip@lists.oasis-open.org [mailto:
kmip@lists.oasis-open.org] On Behalf Of Tim Hudson Sent: Wednesday, 26 June 2013 9:41 PM To:
kmip@lists.oasis-open.org Subject: [kmip] Groups - kmip-asym-key-profile-v1.0-wd01-review.doc uploaded Submitter's message Updated conformance wording style. Updated test case style. Included test cases for 1.0, 1.1 and 1.2. Applied new OASIS template. -- Tim Hudson Document Name : kmip-asym-key-profile-v1.0-wd01-review.doc Description Asymmetric Key Lifecycle Profile Download Latest Revision Public Download Link Submitter : Tim Hudson Group : OASIS Key Management Interoperability Protocol (KMIP) TC Folder : Drafts Date submitted : 2013-06-26 04:40:47